Admin management

Editorial admin is the editorial workflow surface: drafts, review, scheduling, publishing, cross-module mention curation, and archive. Phase 1 uses repo-based authoring (TypeScript content files). Phase 2 admin UI is in the roadmap when manual editorial volume exceeds ~50 articles per month.

Phase 1 workflow (current)

1. Editor opens `core/data/mock-editorial.ts` in a PR.
2. Adds the new EditorialArticle entry with all required fields + the bilingual body HTML.
3. Authors manual cross-module link entries in `mock-ecosystem-links.ts` keyed `editorial:<article-id>`.
4. Opens PR. CI checks: TypeScript compile, EN+AR present, slug unique, mentioned IDs exist, structured-data validity.
5. Editorial lead reviews + merges. Next deployment includes the article.

Phase 2 — Admin UI (planned)

Article editor

WYSIWYG markdown editor with EN/AR side-by-side panes. Live preview of card and detail rendering.

Mention picker

Search-as-you-type widget that resolves founders / startups / events / opportunities and inserts the proper IDs into the article entity.

Cross-module link editor

Side panel showing auto-suggested links. Editor approves, hides, or replaces with manual reasons.

Schedule + publish

Date picker for `publishedAt`. State transitions: draft → in-review → scheduled → published → archived.

Audit log

Every change recorded: who, when, what changed. Used for editorial transparency and version recovery.