11
public routes
Clickable public pages in the current frontend
5
auth routes
Login, registration, verification, and recovery flows
32
protected routes
Common, member, scientist, and admin workspaces
15
service domains
Feature hooks, service modules, and contracts by domain
Innovation Lab
Turn scientist submissions into review-ready Eco Spark records.
The lab story follows real scientist creation routes, attachment handling, draft tracking, admin review queues, featured ideas, and archive flows already present in the app.
7
pipeline routes
Scientist and admin submit-to-review pages
4
architecture controls
Contract, query, service, and analytics modules
3
taxonomy tools
Categories, tags, and specialties for idea context
Contract-first API layer
Request payloads and backend responses are validated with Zod contracts before UI state depends on them.
TanStack Query hooks
Feature hooks wrap loading, error, retry, stale data, and mutation behavior for each domain.
Protected routing
Proxy and server layouts guard protected member, scientist, admin, and common account routes.
Adoption Hub
Move public discovery into member adoption and paid access.
The adoption story is built from the public idea, campaign, scientist, community, member browsing, saved idea, vote, and purchase routes instead of static demo cards.
8
adoption routes
Public discovery and member activity pages
3
commerce surfaces
Checkout, payment success, and purchase history
4
public catalogs
Ideas, campaigns, scientists, and community reports
Purchase access
Commerce hooks and services support checkout session creation for paid idea access.
Payment success route
The `/payments/success` route resolves successful checkout state and links users back to purchases.
Community reports
The `/community` route presents experience reports that connect member feedback to idea adoption.
Live Ideas
Loading the public idea catalog.
Loading live ideas
Fetching the public idea catalog for the homepage showcase.
Success System
Eco Spark success is tracked from idea intake to paid access.
The path below is built from the project's real scientist submission routes, admin moderation routes, member adoption routes, service domains, commerce surfaces, and taxonomy tools.
15
success routes
Submit-to-review and discovery-to-adoption paths
3
role workspaces
Member, scientist, and admin dashboards
15
service domains
Feature hooks, services, and contracts by domain
3/3
commerce + taxonomy
Paid access surfaces paired with category metadata
01
Scientist pipeline
Submission becomes review-ready
Scientists move from create idea, draft records, attachments, and submitted ideas into admin review.
02
Admin controls
Moderation turns records into trusted listings
Admins use pending review, featured ideas, archives, reports, categories, tags, and specialties to keep public data reliable.
03
Member adoption
Discovery turns into member adoption
Members browse public ideas, save records, vote, comment, purchase, and return through account activity routes.
Public Routes
Every public home section points to a real route.
These links are the actual public pages available in this frontend, including the newly added company, support, and legal pages.
Auth Flows
Authentication and recovery are shown as first-class flows.
The project includes registration, email verification, login, forgot password, and reset password routes.
Role Workspaces
Member, scientist, and admin routes are mapped from the app.
These dashboard groups reflect the protected route folders and role defaults already present in the project.
Member workspace
Browse ideas, create reports, review purchases, votes, comments, saved ideas, and profile data.
6 routes
Scientist workspace
Create ideas, manage drafts, attach supporting files, and track submitted ideas.
6 routes
Admin workspace
Manage ideas, reports, users, campaigns, tags, categories, specialties, and review queues.
13 routes
Common Protected Routes
Account activity routes come from real protected pages.
These common protected routes are shared across authenticated roles for profile, security, purchases, saves, votes, and comments.
Product Surface
Public discovery matches the existing feature pages.
Ideas, campaigns, scientists, and community reports are the core public browsing areas already implemented in the app.
Idea catalog and detail pages
The `/idea` and `/idea/[id]` routes use the idea service for published ideas, pricing, metrics, and detail views.
Campaign directory
The `/campaigns` routes expose campaign records and connect voting activity to protected account flows.
Scientist directory
The `/scientist` route presents scientist records from the scientist service and profile-related fields.
Community reports
The `/community` route presents experience reports that connect member feedback to idea adoption.
Workflow
The product lifecycle follows the real role model.
The lifecycle starts in public discovery and continues through auth, scientist submission, admin moderation, and member adoption.
Discover
Public users review ideas, scientists, campaigns, and community reports before signing in.
Register or login
Auth routes handle registration, email verification, login, password recovery, and reset.
Submit
Scientists create structured idea records with category, impact, access, attachments, and status data.
Moderate
Admins review ideas, manage statuses, feature records, archive items, and moderate reports.
Adopt
Members save, vote, comment, purchase, and track ideas through protected account routes.
Commerce
Paid idea access is covered by existing routes and services.
Commerce content references the real checkout, purchase, and payment-success surfaces already present in the project.
Purchase access
Commerce hooks and services support checkout session creation for paid idea access.
Payment success route
The `/payments/success` route resolves successful checkout state and links users back to purchases.
My purchases
Protected purchase routes show member purchase records from the commerce service.
Taxonomy
Admin taxonomy tools are part of the home story.
Categories, tags, and specialties are real admin-managed records used by ideas and scientist profiles.
Idea categories
Admins maintain categories through `/admin/dashboard/create-idea-category` for idea filtering and organization.
Idea tags
The tag management route supports idea metadata used across admin and scientist workflows.
Scientist specialties
Specialty management supports scientist profiles and search-friendly expertise records.
API Domains
Service domains come from the project architecture.
The list below mirrors the repository's feature, service, and contract domains.
authideacampaigncategorytagspecialtycommercecommunityscientistinteractionmoderationuseradmin-analyticsmember-analyticsscientist-analytics
Architecture
Data flow follows the repo's contract-first pattern.
Pages use feature hooks, feature hooks call services, services use the shared HTTP client, and contracts validate data.
Contract-first API layer
Request payloads and backend responses are validated with Zod contracts before UI state depends on them.
TanStack Query hooks
Feature hooks wrap loading, error, retry, stale data, and mutation behavior for each domain.
Axios service modules
Service files call the backend through the shared HTTP client and `/api/v1` rewrite path.
Typed analytics modules
Admin, member, and scientist analytics services feed dashboard overview pages.
Governance
Authentication, routing, and errors use existing utilities.
This section is based on the current session helpers, proxy protection, dashboard defaults, token behavior, and API error handling.
Role defaults
Members, scientists, admins, and super admins land on the correct dashboard after authentication.
Protected routing
Proxy and server layouts guard protected member, scientist, admin, and common account routes.
Typed failures
Shared API error helpers normalize network, validation, and backend errors into user feedback.
Token refresh
The HTTP client injects access tokens and attempts refresh behavior when requests return unauthorized responses.
Technical Stack
Built with the stack declared in the project README.
This section summarizes the actual framework, form, query, validation, HTTP, styling, and routing tools used by the app.
Next.js 16 App Router
React 19 Server and Client Components
Tailwind CSS 4 design tokens
TanStack Query data orchestration
TanStack Form and Zod validation
Axios service modules
Lucide icon system
Role-based proxy protection
FAQ
Answers are specific to this repository.
The FAQ explains where the homepage content comes from and how it connects to real project code.
What project data does this homepage use?
The sections are based on actual Eco Spark routes, dashboard groups, service domains, auth flows, README architecture, and the live idea query hook.
Which roles are represented?
The homepage describes member, scientist, admin, and super admin behavior through the real dashboard routes and role defaults.
Where does live data appear?
The live idea showcase uses the existing `useIdeasQuery` hook and the idea service instead of static idea records.
How is the backend connected?
The app rewrites `/api/v1` requests to `NEXT_PUBLIC_API_BASE_URL`, and service modules validate responses with Zod contracts.
Next Step
Continue through real Eco Spark routes.
Browse public ideas, create an account, or use the support route for setup details around the backend API and protected workspaces.