Input Model
06
Name, email, optional phone, occupation, state, era
Request IntakeLead-FirstFirebase-OnlyNo Custom Backend
Contribute To The Living Map
Contributions now start on Home with a quick form, then hand off to map exploration and optional quiz enrichment.
This page documents the real runtime path: Home lead capture writes to Firebase, map handoff carries era context, and quiz responses enrich interpretation.
Storage Mode
Firestore
Firebase client writes
Map Handoff
URL + Brief
Explorer seeded from Home
Timeline
Contribute On Home
Start on Home with a quick contribution form. Name, email, occupation, state, and era are captured first; phone number can be added optionally without blocking progress.
Timeline
Continue To Map
After submit, the handoff keeps era context in the URL and sends users into `/map` for deeper exploration and filtered story nodes.
Timeline
Optional Quiz Enrichment
A short quiz can be completed after contribution to enrich era/theme fit. It supports interpretation and segmentation, not account creation.
Readiness Checklist
Validate the Home -> Map -> Quiz flow
- Ready state
Home form validates required fields: name, email, occupation, state, and era.
- Ready state
Firestore write succeeds and returns a stable record reference.
- Ready state
Map handoff keeps era in URL and loads the corresponding map context.
- Ready state
Quiz remains optional and never blocks map access after contribution.
Preview Limitations
This page describes the live participation flow
Firebase-only runtime
This web slice runs on Firebase Hosting with client writes to Firestore and analytics instrumentation in the browser.
No custom backend
There is no standalone API server for request orchestration in this phase. Scope stays inside Firebase-managed services.
Generation is out of scope
This flow does not queue portrait generation. It focuses on lead capture, map participation, and optional quiz enrichment.
What to Expect
FAQ + Signals
Can I queue a real portrait request from here?
No. Public V1 does not include generation queue infrastructure. The current product goal is contribution-first map participation.
What happens after I submit from Home?
Your contribution is written to Firestore, then era context is carried into `/map` through URL state so you can continue exploration immediately.
Do I need an account to contribute?
No account is required in public V1. Contribution is open, with data handling and access constraints documented on policy pages.
Ready to proceed?
Start from Home, submit a contribution, continue to `/map`, and optionally complete the short quiz for better era/theme relevance.
Current Public Summary
Search-Friendly Context
Request flow documentation explains how contribution data is captured on Home and transferred into seeded map exploration inside the wider America250 archive surface.
Where does contribution start?
Contribution starts on the Home page through a quick form that captures identity and context fields for map seeding.
Which fields are collected during request intake?
The current model stores name, email, optional phone, occupation, state, and era as the initial intake profile.
Is quiz completion required before map access?
No. The quiz is optional and can enrich interpretation, but users can continue to the map without it.
Related Information
These pages reduce ambiguity around the current preview build and tie the America250 topic cluster back to the archive surface, policies, and trust model.