FAQ & Roadmap

Common questions, and what's deliberately not built yet.

Do I need Adhara to use this?

No. Every feature works against local JSON files with zero external services, zero API keys, zero account. Adhara is an optional upgrade path, connected feature by feature — see Overview.

Is this a 1:1 port of the Python original?

No — this is a core-first v1. Everything content-related (blog, events, portal, scheduling, links, forms) is ported. A few things are new to this port and didn’t exist in Python at all: a real e-commerce storefront via the Adhara Commerce SDK, a podcast page, a media gallery, Netlify as a fifth deploy target, and an idempotent “install your tools” script. A handful of things are deliberately deferred — see the roadmap below.

Why does /admin need GRAVITY_DEV_ADMIN=1 locally?

Real Adhara-backed admin login isn’t implemented yet — the documented SDK surface has no confirmed user-auth (client.auth.login) resource. GRAVITY_DEV_ADMIN=1 is the supported local admin path until that’s confirmed. Never set it in production.

Can I add an eighth cloud storage backend?

Yes — implement the ContentStore interface in a new src/stores/<name>.ts, register it in src/stores/index.ts’s BUILDERS map, and add its auto-detect env var. See Storage.

The SDK is missing something I need. What do I do?

Don’t work around it here — fix it at the SDK’s source (a sibling repo), the same way six real gaps were found and fixed while building this project’s Adhara-backed features. See The Adhara SDK.

Roadmap / known gaps

Deliberately out of scope for this v1, roughly in the order they’d be worth adding:

1. Real Adhara admin login — see above.
2. Portal OAuth/social login — see Customer Portal.
3. Theme Tweaks UI — the Python original’s in-browser CSS-token override panel; not built here (the builder canvas covers block content/layout, not theme-wide styling).
4. Paid event ticket checkout — free-event registration is real (see Features); Adhara’s own public registration endpoint refuses paid-tier events, and this port doesn’t attempt ticket checkout on top of it (needs Adhara Commerce, same gap as paid membership tiers below).
5. Paid membership tiers — present in the Python original, not attempted here (needs Adhara Commerce).
6. Links-page admin write API — Adhara’s authenticated create/update/delete/reorder endpoints for links are confirmed but not wired up (no in-app admin UI calls them yet).
7. A public, session-based multi-item shopping cart on Adhara’s real backend — confirmed to exist, not yet wrapped by the SDK. See Commerce.

Where do I report a bug or ask something not covered here?

Open an issue against this repo, or — if you’re an AI coding agent reading this — check /llms-full.txt for the complete documentation corpus in one file before guessing at an answer.