← Geof Miller project

Design foundation · October 7, 2026 · Proposed v1

A place to read.
A way to keep creating.

Information architecture, page patterns, and a first publishing loop. Based on the initial scope approved by Geof, as reported by John.

Read the approved scope · This design is a proposal for review.

Three areas, distinct responsibilities

Public navigation follows readers’ interests. The workspace follows tasks. Family access follows explicit permission.

Public · Anyone

Geof’s website

  • HomeWhat matters → Current work → Archive
  • Parkinson’sNotes, stories, and selected resources → Reading page
  • Current workComing soon → Project detail when cleared
  • ArchiveSearch and browse → Work detail → Read or view original
  • ScreenwritingApproach, feedback, classes → Inquiry
  • About / ContactBiography, ways to reach and follow
Authorized · Geof and helpers

Publishing workspace

  • HomeStart an update; resume work; attention items
  • Drafts and approvalsCapture → Review → Approval → Publish
  • ContentParkinson’s, current work, archive, screenwriting
  • Recent changesWho acted, what changed, restore
  • People and accessAssigned responsibilities; grant or revoke
Separately authorized · Family

Family starting point

  • Start herePriority instructions and where to go next
  • Records and accountsReferences to existing secure systems
  • People to contactRole, reason to contact, current details
  • Recipes and personal materialPrivate by default; public sharing is deliberate
  • Access helpRecovery and designated assistance
Proposed navigation: Parkinson’s · Current work · Archive · Screenwriting. Geof’s name returns home; About and Contact remain visible utility links. Workspace sign-in is separate. Family navigation appears only to authorized people.

Access model to validate

These are proposed responsibilities, not permissions already assigned to anyone.

RolePrepare and editApprove and publishFamily material
GeofAll contentApproves content and delegates authorityControls access
Editorial helperAssigned content and draftsMay publish the exact approved version only if delegatedNo default access
Family stewardFamily references and instructionsPublic publishing requires separate authorizationExplicitly granted areas
Technical stewardSite and integrationsNo default editorial approval authorityNo default access

Content foundations

Use a few reusable objects: post, project, archive item, service, contact, private reference. Each needs a title, body or source, author, contributors, dates, revision history, and publication state. Archive items also retain original date, format, and provenance.

Visibility and publication state are separate: a private item must never become public just because its status changes. Private content belongs in protected storage, outside the public repository. Unannounced project material is held until explicitly cleared.