Nexxspan CMS workflow
Nexxspan CMS dashboard
A controlled workflow for inspecting legacy source data, normalizing it, compiling a preview, and handing off a static published snapshot.
- Client
- Nexxspan
- Source mode
- Local Legacy Export
- Future source
- NetSuite/File Cabinet
- Current stage
- Intake
- Runtime model
- Static Published Snapshot
Intake Audit
IntakeInspect the quarantined local legacy export and classify files before mapping.
Source Preview
NormalizedView the future-facing source contract that NetSuite/File Cabinet should emit later.
Compile Preview
PreviewCompile the minimal subset into a renderer snapshot without publishing production.
Website Handoff
Published SnapshotOpen the static JSON contract that nexxspan-site consumes as generated content.
Field Mapping
AgreementReview how legacy source fields map into Feasure canonical fields.
Design Manifest
RendererReview which generic components are used to compile the homepage subset.
Theme Tokens
BrandReview the controlled styling tokens used by the compiled snapshot.
Draft editing
Editing Mode Coming Next
Users will edit draft content here through controlled fields.
Changes will be saved as drafts first, not pushed directly live.
Publishing will validate the draft, generate a published snapshot, and hand it off to the client website.
In production, NetSuite/File Cabinet will remain the source of truth for source-owned records and assets.
Publish action placeholder
Snapshot publishing is not wired yet
This panel uses future CMS language without performing persistence, GitHub writes, Netlify deploys, or production publishes.
- Last Published
- Not connected yet
- Publish Target
- Nexxspan website snapshot
- Current Handoff
- /nexxspan/handoff/nexxspan.published.snapshot.json
Current CMS configuration
Client-specific meaning stays in config files. Feasure core remains generic and does not learn Nexxspan-specific product concepts.
Field mappings
6
Homepage components
5
Theme preset
technical