Your account
HOL-D074Story implementation: Planned

Create and publish stories galleries and videos

content · Proposed launch phase 1

Start from Home

Review as Editor · Full workflow planned

User story

As an editor, I want to prepare and publish canonical editorial work with correct credits and associations so readers see one trustworthy version everywhere.

Draft requirements for review · Updated 2026-10-19

What the app should do

  • Create and edit story, gallery and video records with title, body/media, captions, accessible descriptions and explicit public/member eligibility.
  • Manage credited people, topics, places and events as approved relationships, keeping identifiers stable and attribution actionable.
  • Save private drafts and preview the intended reader presentation before publishing; publishing authority belongs to an assigned Editor.
  • Publish or correct a selected revision, or remove it from public discovery through a reversible unpublish action. Explain what happens to links and existing engagement.
  • Home, Community, Groups, Search, creator portfolios and place/event hubs reference the same canonical object and appropriate engagement; programming Home remains D028.
  • Validate required metadata, credit/rights confirmation and content eligibility before publication; video assets and processing still need an approved delivery approach.
  • Associate canonical published work with approved organizations as well as credited people, places and events. Give each relationship its actual meaning—subject, host, affiliated organization or explicitly disclosed sponsor—without replacing creator credits.

What to check in the demo

Follow these steps from the role’s landing page through navigation and feature checks.

Review as

Editor

Start here: Home

Choose the Nora Vale dummy account and open its assigned Editor Home without a password or authenticator prompt. This dev-only Home review does not verify MFA or unlock protected staff actions. Use your own provisioned staff account and authenticator when reviewing those actions.

Navigation from sign-in

  1. 01Open the fictional Editor account through the connected sign-in service. Seeded Home review opens directly. Real HOL staff access and protected actions require an authenticator check.
  2. 02On Editor Home, select Editorial library. The existing collection is a preview, not a complete authoring/publishing tool.

Feature checks start here

Create and publish stories galleries and videos · Full workflow planned

Planned full workflow. Existing workspace samples, where present, demonstrate only isolated controls. Backend implementation is on hold; no completed end-to-end outcome or stakeholder approval is claimed. Public people and organization pages are available; this operator handoff remains incomplete. Backend implementation is on hold.

  1. 03Inspect the published examples and draft row; record the absence of complete authoring controls.
  2. 04Once built, prepare a fictional story, gallery and video draft with credits, accessibility and public/member metadata.
  3. 05Preview an unpublished revision; verify it is unavailable to ordinary readers and that missing required credits block publication.
  4. 06Publish one revision and open the same object from its attributed profile, Search and place/event associations; check stable identity and access.
  5. 07Correct and unpublish the sample through reversible controls; inspect link behavior and preserved engagement history.
  6. 08Once built, associate a fictional work with a credited person and a separately approved organization; open the same work from both public pages and verify attribution, disclosure and independent content access.

Backend work for this feature

Requirements only · Backend implementation on hold

What needs to be supported

  • Persist canonical content IDs, typed story/gallery/video payloads, revisions, media references, publication state, eligibility and a relationship table for credited people/topics/places/events.
  • Restrict draft/edit/publish operations to assigned editorial scope and validate relation targets, attribution/rights and accessibility requirements on the server.
  • Serve only the current permitted published revision to public/free/paid readers; changing a published object’s eligibility must not leak cached protected bodies or private drafts.
  • Publish atomically with a version check and actor/time/reason record; update discovery indexes and related surfaces from the same canonical ID without copying engagement.
  • Define safe media upload, processing/readiness and storage delivery before connection; an unavailable asset must not publish as a working video. No provider or pipeline is enabled in this task.
  • Support correction/unpublish, conflict recovery, repeated publish and failed index/media updates; preserve lawful records and relationships according to the approved retention policy.
  • Extend canonical content associations to approved organization IDs and typed relation meanings; gate publication on valid public targets and required sponsorship disclosure without copying authorship.

How to verify when implementation is approved

  1. Use an assigned Editor, another operator, free reader and paid reader to test private drafts and content eligibility.
  2. Publish the same revision twice and concurrently edit a stale draft; verify one canonical publication and clear conflict handling.
  3. Open the work from multiple discovery surfaces, change eligibility, correct and unpublish it; verify consistent content, attribution, access and engagement.
  4. Publish/correct/unpublish an organization-associated story and confirm public person/org/place/Search references share one entitled work with the original credits.

Before this can work

  • Choose the Nora Vale dummy account and open its assigned Editor Home without a password or authenticator prompt. This dev-only Home review does not verify MFA or unlock protected staff actions. Use your own provisioned staff account and authenticator when reviewing those actions.
  • Confirm editorial assignments, media limits/delivery, rights/credit checks and correction/unpublish policy. Commercial staff do not gain editorial publish authority.
  • Use fictional role-preview records. Frontend prototypes may simulate the workflow; no backend implementation or real service operation is authorized.

Connected stories