Resources
Documentation for the people who will extend this
Nexus is a template, so the useful documentation is architectural: how the data model fits together, how themes are defined and what the demo does and does not do.
The Nexus data model
How users, teams, companies, contacts, leads, pipelines, stages, deals, line items, activities, tasks, events, proposals and automations relate — and why derived values are never stored.
See custom fields in the appBuilding a seventh theme
Themes are a token block plus a registry entry. Add a `[data-theme]` rule defining the surface, ink, accent, status and chart tokens, then register the theme's name, tagline and preview swatches.
Open the theme pickerAutomation: triggers, conditions, actions
The rules engine runs in the browser against the demo dataset. Learn which triggers exist, how conditions are evaluated and what each action does to local demo state.
Open the automation builderFive minutes in the demo
Move a deal to Won on the pipeline board, then check the forecast, the dashboard and the customer timeline. One change, four screens, no duplicated state.
Start on the pipelineWhat is not implemented
No backend, no authentication, no email delivery, no payment processing and no external integrations. Everything labelled as connected is local demo state.
Review integration stateSaved views and filters
How the built-in views — my open deals, high-value opportunities, slipped close dates, overdue follow-ups, new leads this week — are expressed as filter objects you can extend.
Try the saved views