Split FAQ into developer and community FAQs#53
Open
francismars wants to merge 4 commits into
Open
Conversation
Add /community/faq with accordion UI and Nostr-derived user copy. Refocus /docs/faq on publishing, signing, and developer support. Link User FAQ from footer Resources; add FAQ to community nav.
Enable SSR on /community/faq so meta and schema ship in prerendered HTML. Add per-question anchors, h3 headings, and docs canonical URLs.
Contributor
|
Going through this rn |
NielLiesmons
pushed a commit
that referenced
this pull request
Jun 3, 2026
…esign Integrate split community/developer FAQ (PR #53): /community/faq page, developer FAQ at /docs/faq, footer and sitemap updates. Resolve community layout conflict: keep Search (last) and FAQ nav, loadZapstoreCommunityEvent, and distinct sidebar icons for Search vs FAQ.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
The site had a single FAQ at
/docs/faqthat mixed end-user and developer topics. This PR splits that into two audiences:/community/faq— User FAQ (install, safety, comparisons, features, troubleshooting, support). Primary entry: Footer → Resources → FAQ./docs/faq— Developer FAQ (publishing, signing, trust model, relay issues, growth). Studio and docs links stay on this URL.I walked through both pages locally and the copy/UI look good to me; I would appreciate a review before merge.
What changed
src/content/docs/faq.mdas a developer-focused FAQ with a link to the community FAQ.src/lib/data/community-faq-content.js.data-main-scroll)./community/faq./community/faq.FAQPageJSON-LD (community-faq-seo.js), keyword-focused title/description, per-question#anchors,h3headings,ssr = trueon the FAQ page so meta and schema are in prerendered HTML.Where the questions came from
User FAQ questions and answers were drafted from recurring Nostr threads (Zapstore account + community replies). Rewrote for clarity on the website.
Developer FAQ content aligns with existing docs (
publish,trust-model) and developer-oriented items from that same research.Review requested
Test plan
/community/faq— sections render, accordions open/close, page scrolls inside community shell/docs/faq— developer topics only; link to community FAQ works/community/faq/community/faqFAQPageJSON-LD and meta tags presentbun run buildpasses