2026-03-17 — Prakta

What shipped today

Prakta went from a bare create-next-app scaffold to a fully architected application with production infrastructure and a complete marketing homepage. The session focused on two things: standing up the same technical foundation used across the Synaxis portfolio (Eclectis, Authexis), and building the entire issue #1 homepage spec.

The infrastructure layer mirrors Eclectis exactly — Supabase SSR auth with browser/server/middleware/admin client helpers, Next.js 16 proxy.ts for route protection, shadcn/ui (new-york style with the Synaxis warm editorial palette), next-themes, and route groups splitting the app into marketing, auth, and authenticated surfaces. The Supabase project was created and connected with env vars in place.

The homepage implements all eight sections from the issue #1 spec verbatim — hero, argument (two kinds of work), Option A vs Option B two-column layout, how it works steps, the Synaxis suite cards with “you are here” on Prakta, closing CTA with pricing, and footer with all cross-links. Design matches authexis.app: Playfair Display for headings, Inter for body, cream/brown/gold palette, paper grain texture, gold ribbon accent, knockout lines with left gold border. The Work of Being callout renders as an editorial aside.

Completed

No issues formally closed — issue #1 (homepage) is substantially built but needs visual review and the navigation question from #2 resolved before closing. Issue #3 (metadata/favicon) was partially addressed — metadata is set but favicon still needs a custom asset.

Carry-over

• Issue #1 — homepage: Copy is complete, design matches spec. Needs Paul’s visual review and any adjustments. Then close.
• Issue #2 — navigation destinations: Still open. “How it works” and “Pricing” are section anchors. Sign in/Get started link to /login and /signup stubs. Blog/Privacy/Terms link to placeholder routes. Needs a decision on which are real pages at launch vs. hidden.
• Issue #3 — metadata and favicon: <Metadata> is set with Prakta branding. Custom favicon still needed.
• Issue #4 — README: Still the create-next-app README.
• Issue #5 — CI: No GitHub Actions yet.
• Supabase migration: user_profiles migration written but not yet run against the live database.
• Auth pages: Login, signup, reset-password are stub pages — need actual Supabase auth forms.

Risks

• The Supabase publishable key was provided but the service role key wasn’t — admin operations won’t work until that’s added to .env.local.
• The migration hasn’t been applied to the live Supabase instance yet. Need to run it before auth flows will work.

Flags and watch-outs

• Port 3000 was occupied during dev — the server fell back to 3001. Check what’s on 3000 if it persists.
• shadcn v4 uses @base-ui/react buttons without asChild — the Radix pattern from Eclectis doesn’t carry over. Use buttonVariants() with plain <a>/<Link> instead.

Next session

1. Run the Supabase migration against the live database
2. Get Paul’s visual review of the homepage — adjust design if needed
3. Resolve issue #2 (nav destinations) and close #1 + #2 together
4. Build actual login/signup forms with Supabase auth
5. Add the service role key to .env.local
6. Replace favicon (issue #3)