Skip to content

Updating Staging from Main#144

Merged
hawkandheron-dev merged 3 commits into
Stagingfrom
main
May 16, 2026
Merged

Updating Staging from Main#144
hawkandheron-dev merged 3 commits into
Stagingfrom
main

Conversation

@hawkandheron-dev
Copy link
Copy Markdown
Owner

No description provided.

claude and others added 3 commits May 16, 2026 17:16
Reorder the landing nav, rename the Timeline component entry to "Base
timeline component," and add a visually distinct Contributor Portal link
backed by a new .button-accent design-system variant.

Open the portal page to anyone: drop the contributor/admin gate that
swapped in CollaboratorsOnlyNotice, gate the write affordances (Submit
Feedback, IssueCreatorModal, contribution list) on canWrite, and skip
the RLS-restricted fetch when the visitor can't write. Rewrite the
WelcomeHeader copy to be role-aware and explain who can do what without
inviting visitors to become contributors.
The Contributor Portal used to live inside the Church History Timeline app
with hard-coded ch-timeline scoping, which hid feedback submitted from the
Bible Atlas and First Century Church Directory. Make it a standalone page
that aggregates feedback across every app and lets submitters tag the
section their feedback is about.

- New apps/contributor-portal.html entry, with its own React shell that
  reuses GettingStartedPage in aggregate mode and shows a generic
  "Windhover · Contributor Portal" header.
- Add a section picker to IssueCreatorModal, defaulting to the host app
  but always editable so contributors can re-tag.
- Group the contribution list by section (General, CH Timeline, FCC,
  Bible Atlas) and badge each row with its section.
- Wire entry points: landing-page link, side nav, header buttons on each
  app. Legacy #getting-started hash redirects to the standalone page.

https://claude.ai/code/session_016esLPiFAgz8c6aBoLuA1rg
…portal-menu-U48c5

Extract Contributor Portal to standalone app
@hawkandheron-dev hawkandheron-dev merged commit 948db2a into Staging May 16, 2026
4 of 5 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants