Landing page, frontend SOP, and where projects live

### Type Feature ### Lineage Standalone — board-remember backlog item (converted from todo note `remember-landing-page-frontend-sop`) ### Repo TBD — likely a new SvelteKit repo for the landing page, plus convention docs in `pal-e-docs` ### User Story As the superuser I want a landing page on the cluster that captures leads and a frontend SOP convention So that posts have a real CTA destination and every project follows a repeatable frontend pattern ### Context Stream-of-consciousness captured on 2026-03-14 while building the Posts project. The CTA link in posts needs a real destination — a landing page on the cluster that captures leads. This spawns several threads of work: - **Landing page repo**: SvelteKit frontend on Tailscale that captures leads (email, maybe name) - **Lead capture backend**: Where to receive and store contact info - **Frontend SOP**: Convention for how frontends are built across projects (fork impeccable to Forgejo, deploy SvelteKit apps to cluster — repeatable pattern) - **Project placement**: Determine if this lives under pal-e-agency or a separate project ### File Targets - New SvelteKit repo (TBD) - Convention note in pal-e-docs for frontend SOP - Lead capture endpoint (TBD — could be pal-e-api or standalone) ### Acceptance Criteria - [ ] Decision on project placement documented - [ ] Landing page repo created with SvelteKit scaffold - [ ] Lead capture endpoint functional - [ ] Frontend SOP convention written ### Test Expectations - [ ] Landing page loads on cluster URL - [ ] Lead capture form submits and stores data - [ ] Convention note exists in pal-e-docs ### Constraints - Must be on Tailscale (no public ingress unless explicitly decided) - Minimal friction: email only at first - Frontend SOP should be a convention, not a project ### Checklist - [ ] Scope reviewed - [ ] Implementation complete - [ ] Tests pass ### Related - Original todo note: `remember-landing-page-frontend-sop` - Board: board-remember - Converted from deprecated todo item_type per `feedback_no_todo_notes`

forgejo_admin commented

2026-03-24 20:42:55 +00:00

Owner

Type

Feature

Lineage

Standalone — board-remember backlog item (converted from todo note remember-landing-page-frontend-sop)

Repo

TBD — likely a new SvelteKit repo for the landing page, plus convention docs in pal-e-docs

User Story

As the superuser
I want a landing page on the cluster that captures leads and a frontend SOP convention
So that posts have a real CTA destination and every project follows a repeatable frontend pattern

Context

Stream-of-consciousness captured on 2026-03-14 while building the Posts project. The CTA link in posts needs a real destination — a landing page on the cluster that captures leads. This spawns several threads of work:

Landing page repo: SvelteKit frontend on Tailscale that captures leads (email, maybe name)
Lead capture backend: Where to receive and store contact info
Frontend SOP: Convention for how frontends are built across projects (fork impeccable to Forgejo, deploy SvelteKit apps to cluster — repeatable pattern)
Project placement: Determine if this lives under pal-e-agency or a separate project

File Targets

New SvelteKit repo (TBD)
Convention note in pal-e-docs for frontend SOP
Lead capture endpoint (TBD — could be pal-e-api or standalone)

Acceptance Criteria

Decision on project placement documented
Landing page repo created with SvelteKit scaffold
Lead capture endpoint functional
Frontend SOP convention written

Test Expectations

Landing page loads on cluster URL
Lead capture form submits and stores data
Convention note exists in pal-e-docs

Constraints

Must be on Tailscale (no public ingress unless explicitly decided)
Minimal friction: email only at first
Frontend SOP should be a convention, not a project

Checklist

Scope reviewed
Implementation complete
Tests pass

Original todo note: remember-landing-page-frontend-sop
Board: board-remember
Converted from deprecated todo item_type per feedback_no_todo_notes

forgejo_admin referenced this issue from forgejo_admin/pal-e-api

2026-03-24 20:44:23 +00:00

Convert 31 deprecated todo-type board items to Forgejo issues #205

Rows
Columns

Landing page, frontend SOP, and where projects live #158