π― Goal
Take the func(kode) landing page from a visually assembled state to a fully production-shipped product β every section rendering correctly at all viewports, every CTA and form wired to both Supabase (actions) and PostHog (tracking), and every known backend integration gap patched so no user journey ends in a silent failure or broken state.
This EPIC sits between the structural rebuild (EPIC #92) and the analytics instrumentation (EPIC #108). It is the connective tissue that makes both of those EPICs actually work for real users.
π Context
π¦ Child Issues
| # |
Issue |
Area |
Priority |
| 1 |
#125 β AboutSection + HowItWorks landing sections β implement remaining above-fold sections |
Landing |
π΄ High |
| 2 |
#126 β ForTeams + ForDevelopers + ContactUs landing sections β complete the page |
Landing |
π΄ High |
| 3 |
#127 β Hero CTAs wiring β "Start Contributing" β /auth/login, "Explore the project" β /projects |
Landing / CTA |
π΄ High |
| 4 |
#128 β Fix GitHub OAuth redirect loop (Bug #86) β patch @supabase/ssr callback handling |
Auth / Backend |
π΄ Critical |
| 5 |
#129 β ContactUs section form β Supabase insert + PostHog contact_submitted event |
Landing / Backend |
π‘ Medium |
| 6 |
#130 β Event Announcement Popup (#103) β date/time config, Discord CTA link, and PostHog events |
Landing / Analytics |
π‘ Medium |
| 7 |
#131 β Landing page Footer component β links, social icons, PostHog footer_link_clicked |
Landing |
π‘ Medium |
| 8 |
#132 β RELEASE_VERSION sourced from package.json β remove hardcoded version string |
Tech Debt |
π’ Low |
π¦ Definition of Done
π Related EPICs & Issues
π― Goal
Take the func(kode) landing page from a visually assembled state to a fully production-shipped product β every section rendering correctly at all viewports, every CTA and form wired to both Supabase (actions) and PostHog (tracking), and every known backend integration gap patched so no user journey ends in a silent failure or broken state.
This EPIC sits between the structural rebuild (EPIC #92) and the analytics instrumentation (EPIC #108). It is the connective tissue that makes both of those EPICs actually work for real users.
π Context
SiteChrome([Landing] SiteChrome layout wrapper + layout.tsx refactorΒ #93), design tokens ([Landing] Design tokens β Tailwind config extensions for landing page typography & spacingΒ #95),LandingBackground([Landing] LandingBackground component + landing-assets.ts registryΒ #96) are merged.Navbar([Landing] Navbar rewrite β new design with auth state + GitHub fork countΒ #94) andHeroSection([Landing] HeroSection + HeroEditorMockup + page.tsx wiringΒ #97) are the remaining PRs in flight.π¦ Child Issues
AboutSection+HowItWorkslanding sections β implement remaining above-fold sectionsForTeams+ForDevelopers+ContactUslanding sections β complete the page/auth/login, "Explore the project" β/projects@supabase/ssrcallback handlingContactUssection form β Supabase insert + PostHogcontact_submittedeventFootercomponent β links, social icons, PostHogfooter_link_clickedRELEASE_VERSIONsourced frompackage.jsonβ remove hardcoded version stringπ¦ Definition of Done
ContactUsform inserts to Supabase and firescontact_submittedto PostHog on successFootercomponent exists with all required links and PostHog click trackingRELEASE_VERSIONno longer hardcoded β sourced from env orpackage.jsonnpm run buildpasses with zero type errors after all PRs mergefix/ui-tweaksβdevπ Related EPICs & Issues
@supabase/ssrcallback handling (Bug #86)Β #128 is the fix)