User-facing display strings now read from config.appName so forks can
rebrand without code changes, and localStorage keys are namespaced by
config.appId so forks running on the same origin don't clobber each
other's preferences. Module-level cache-key constants that previously
hardcoded 'ditto:' have been refactored into hook-scoped reads from
config.appId (via a new getStorageKey() helper). The helpContent FAQ
template now uses {appName} placeholders substituted at read-time
through getFAQCategories(appName)/getFAQItem(appName, id).
- Add visible border-t dividers between FAQ category sections
- Shorten relay question to just 'What are relays?'
- Make questions bigger (text-base) and bolder (font-semibold)
- Darken answer text from muted-foreground to foreground/80
- Clarify report answer to mention the three-dot menu on posts
Introduce a new /help route with beginner-friendly FAQ content covering
getting started, apps, payments, content safety, and why Nostr differs
from big tech. Includes reusable HelpFAQSection and TeamSoapboxCard
components that can be embedded on other pages. Help appears in the
default sidebar so new users see it without manual configuration.
Alex Gleason