Author the manual: articles, journeys, shelves and federation

A journey is an ordered path through the manual for one kind of reader: a name, a subtitle, the outcomes it promises, its prerequisites, and its steps. A step usually points at an article, but it does not have to — a step with no article is pure narration, which is how a journey explains a transition between two chapters. Each step carries its own description (why the reader is here) and a checkpoint (how they know it worked). Consecutive steps that share a phase render as one block, and a journey cannot be published without steps.

Journey Groups are the shelves those journeys are filed on. A group has a name, a subtitle and a sequence; each journey points at one through its Group field. Grouping is presentation only — it never changes who may read a journey. Journeys left without a group are gathered under More journeys, and that fallback shelf only appears when there is more than one of them.

Process Maps opens the canvas where the department mind map and the workflow diagrams are drawn — boxes, lanes, groups and the arrows between them, in either a mind-map or a workflow layout. A box can link to an article, a journey or an action, which is what makes a map a navigation surface rather than a picture. Process Map Records is the same content as ordinary lists, which is the faster way to fix many links at once. Maps that shipped with WindoorERP can be reset to their original drawing; a map drawn here cannot, because there would be nothing to restore from.

This instance is the master. Tenants subscribe, and articles, journeys and their groups are pushed out to them; a group travels with the journeys that belong to it, so shelves arrive already assembled. Matching is by a stable identifier that survives renaming, translation and slug changes — not by title.

On a subscribed tenant, federated content is read-only and says so when someone tries to edit it; Customize makes an editable local copy, and anything created locally is never overwritten by a later sync. An article archived on the tenant stays archived — the sync will not resurrect it. Tools & Federation holds the subscriber registry, the import package wizard, the import audit logs and the background export jobs.

Four screens that tell you what to write next: Health Signal scores the corpus, Reader Feedback collects what readers said about individual articles, Search Backlog lists the searches that found nothing — the most honest to-do list in the app — and Usage Telemetry shows what is actually read.

An article will not save because it is too deep — the tree has a depth limit; deeper trees stop being navigable. Re-parent it higher rather than fighting the guard.

Saving reports the slug is already used — two articles cannot share a URL in one language. Change the slug; old slugs keep redirecting, so renaming does not break existing links.

Publishing is refused — setting the website flag or changing the audience needs the publisher right, not merely the author right.

A journey refuses to publish — it has no steps yet.

An article on a tenant cannot be edited — it is federated from here. Use Customize there, or fix it at the master so every tenant gets the correction.