Clean up pal-e-playground repo — single HTML landing page #180

Open
opened 2026-03-26 23:12:20 +00:00 by forgejo_admin · 2 comments

Type

Feature

Lineage

standalone — playground overhaul scoped 2026-03-26

Repo

forgejo_admin/pal-e-playground

User Story

As Lucas
I want the pal-e-playground repo to contain only the approved single-page landing
So that it's the clean CSS philosophy reference and pipeline hub

Context

New landing page approved (written to ~/pal-e-playground/index.html on 2026-03-26). Repo still contains stale content: guide/ (1,144 line CSS guide, now absorbed into index.html), pal-e-app/ (29MB Svelte hybrid with node_modules), westside logo images, .current-issue, and 4 stale branches (2 already deleted). Need to remove all cruft and commit just the landing page.

File Targets

Files to keep:

  • index.html — the approved landing page (CSS philosophy + pipeline stages + definition of done)
  • README.md — update to reflect new purpose

Additional file target (different repo):

  • pal-e-deployments/overlays/playground/prod/configmap.yaml — nginx /guide/ route needs removal

Files to remove:

  • guide/ directory (content merged into index.html)
  • pal-e-app/ directory (29MB Svelte hybrid, doesn't belong)
  • westside-logo.jpeg, westside-logo.png (project-specific assets)
  • .current-issue (stale)

Branches to delete:

  • 1-scaffold-repo, 3-feat-add-asset-upload-card-to-playground, 45-kanban-board-playground, 46-svelte-kanban-board-prototype, 5-sync-westside-contract-html-with-deploye, add-mcd-tracker-link

Acceptance Criteria

  • Repo contains only index.html and README.md
  • playground.tail5b443a.ts.net renders the approved landing page
  • All stale branches deleted
  • No node_modules, no package.json, no build artifacts
  • nginx /guide/ location block removed from configmap

Test Expectations

  • playground.tail5b443a.ts.net loads correctly on phone
  • No broken links on the page

Constraints

  • This is the pal-e-playground repo (hub), not a project playground
  • The landing page was already approved by Lucas — no design changes

Checklist

  • PR opened
  • Stale content removed
  • Branches cleaned
  • No unrelated changes
  • project-frontend-playground — project page needs updating after this
  • project-capacitor-mobile — pipeline stages section references this
### Type Feature ### Lineage standalone — playground overhaul scoped 2026-03-26 ### Repo `forgejo_admin/pal-e-playground` ### User Story As Lucas I want the pal-e-playground repo to contain only the approved single-page landing So that it's the clean CSS philosophy reference and pipeline hub ### Context New landing page approved (written to ~/pal-e-playground/index.html on 2026-03-26). Repo still contains stale content: `guide/` (1,144 line CSS guide, now absorbed into index.html), `pal-e-app/` (29MB Svelte hybrid with node_modules), westside logo images, `.current-issue`, and 4 stale branches (2 already deleted). Need to remove all cruft and commit just the landing page. ### File Targets Files to keep: - `index.html` — the approved landing page (CSS philosophy + pipeline stages + definition of done) - `README.md` — update to reflect new purpose Additional file target (different repo): - `pal-e-deployments/overlays/playground/prod/configmap.yaml` — nginx `/guide/` route needs removal Files to remove: - `guide/` directory (content merged into index.html) - `pal-e-app/` directory (29MB Svelte hybrid, doesn't belong) - `westside-logo.jpeg`, `westside-logo.png` (project-specific assets) - `.current-issue` (stale) Branches to delete: - `1-scaffold-repo`, `3-feat-add-asset-upload-card-to-playground`, `45-kanban-board-playground`, `46-svelte-kanban-board-prototype`, `5-sync-westside-contract-html-with-deploye`, `add-mcd-tracker-link` ### Acceptance Criteria - [ ] Repo contains only `index.html` and `README.md` - [ ] `playground.tail5b443a.ts.net` renders the approved landing page - [ ] All stale branches deleted - [ ] No node_modules, no package.json, no build artifacts - [ ] nginx `/guide/` location block removed from configmap ### Test Expectations - [ ] `playground.tail5b443a.ts.net` loads correctly on phone - [ ] No broken links on the page ### Constraints - This is the pal-e-playground repo (hub), not a project playground - The landing page was already approved by Lucas — no design changes ### Checklist - [ ] PR opened - [ ] Stale content removed - [ ] Branches cleaned - [ ] No unrelated changes ### Related - `project-frontend-playground` — project page needs updating after this - `project-capacitor-mobile` — pipeline stages section references this
Author
Owner

Scope Review: NEEDS_REFINEMENT

Review note: review-402-2026-03-27

Ticket is well-structured and all file targets verified against the filesystem. Three issues found:

  • CRITICAL: Missing nginx configmap update. The playground nginx config at pal-e-deployments/overlays/playground/prod/configmap.yaml has a location /guide/ block (lines 19-24) that will 404 after guide/ is removed. This must be added to scope as a file target and acceptance criterion.
  • Minor: 2 of 6 listed branches already deleted. 1-scaffold-repo and 3-feat-add-asset-upload-card-to-playground no longer exist on the Forgejo remote. Agent will skip them, but the list should be corrected.
  • Note: Cross-repo work. Issue is on pal-e-platform, work targets pal-e-playground + pal-e-deployments. Acceptable for platform board but agent needs explicit multi-repo targets.
## Scope Review: NEEDS_REFINEMENT Review note: `review-402-2026-03-27` Ticket is well-structured and all file targets verified against the filesystem. Three issues found: - **CRITICAL: Missing nginx configmap update.** The playground nginx config at `pal-e-deployments/overlays/playground/prod/configmap.yaml` has a `location /guide/` block (lines 19-24) that will 404 after `guide/` is removed. This must be added to scope as a file target and acceptance criterion. - **Minor: 2 of 6 listed branches already deleted.** `1-scaffold-repo` and `3-feat-add-asset-upload-card-to-playground` no longer exist on the Forgejo remote. Agent will skip them, but the list should be corrected. - **Note: Cross-repo work.** Issue is on pal-e-platform, work targets pal-e-playground + pal-e-deployments. Acceptable for platform board but agent needs explicit multi-repo targets.
Author
Owner

Issue body updated per scope review corrections.

Issue body updated per scope review corrections.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
forgejo_admin/pal-e-platform#180
No description provided.