Drafts and reviews
No editorial data connected.
Private Stage A · editorial prototype
Manage all demo listings · add more items
Website publishing workspace
Prepare content, review evidence and plan approved publishing from the Karibu Pwani command centre.
No live publishing or staff accounts
This static preview does not save edits, enforce editorial roles or publish content. The separate Next.js/MDX repository handoff remains incomplete.
What needs attention?
Freshness and verification
Review dates and provider evidence must be checked before publishing.
Media and search
Rights, alt text, metadata and search updates require review.
Publishing checklist
- Draft the content and identify its owner, sources and intended route.
- Check facts, media rights, alt text, links and metadata.
- Verify provider, price, availability and safety claims separately.
- Submit for independent editorial and specialist review as needed.
- Obtain approval, preview and publish through the approved source workflow.
- Record the version, reviewer, review due date and rollback reference.
One operational source of truth
Website content belongs in source-controlled editorial records. Nuvendi remains canonical for suppliers, customers, inquiries, inventory, bookings and finance. Listing approval does not verify a supplier or confirm availability.
Content lifecycle
Draft → submitted → review → approved → published → reverify → suspended or archived. Revisions and rejection return to the responsible editor. Real state transitions require server authorization and audit.
Editorial roles
Founder, admin, editor, reviewer, listing coordinator, supplier verifier and auditor need separate create, edit, approve, publish, archive and delete permissions. These roles are design requirements, not active accounts.