Working with content
How to evolve the shell while product details and live integrations are still in progress.
The current VENV build separates content work into three layers:
- Website content in
content/ - Dashboard framing in Vue pages and components
- Mock fixtures in
server/api/
Keep the content strategy independent from whichever live API model is added later.
Content rules of thumb
- Frame intent before writing detail.
- Prefer neutral wording where the backend contract is not final yet.
- Keep release notes aligned around change, adoption and operational clarity.
- Use dashboard copy to explain what a surface is for, not to fake polished business data.
Practical workflow
- Define or update the page role in the content outline.
- Write the public-facing version in
content/if the page lives on the website. - Add supporting copy in the dashboard if the page is part of the app shell.
- Replace mock data only when the API source and naming are stable.
Next step
The dedicated content outline page maps every major surface and its job in the product story.