Playground: kanban board prototype with improved UX #46
Labels
No labels
domain:backend
domain:devops
domain:frontend
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
forgejo_admin/pal-e-docs-app#46
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Type
Feature
Lineage
Standalone — board-pal-e-docs kanban MVP
Repo
forgejo_admin/pal-e-playgroundUser Story
As the superuser
I want a playground kanban prototype I can iterate on with my own eyes
So that the board design feels like mine before it goes into production
Context
The current pal-e-app kanban was agent-built without visual iteration with Lucas. This ticket is the design phase — build it in the playground, iterate until it feels right, then promote to pal-e-app in a separate ticket.
File Targets
Files to modify:
~/pal-e-playground/pal-e-app/board.html— iterate on kanban design~/pal-e-playground/pal-e-app/app.css— evolve styles as design changes~/pal-e-playground/pal-e-app/app.js— add interactivity (drag-drop, filters, mock data rendering)Files NOT to touch:
~/pal-e-app/— don't change production until design is approvedAcceptance Criteria
Test Expectations
Constraints
Checklist
Related
project-pal-e-docs— pal-e-app is the frontendScope Revision: Vanilla JS → Svelte (no SvelteKit)
The vanilla JS prototype (PR #7 on pal-e-playground) proved the layout but drag-and-drop and state management are broken — vanilla DOM manipulation can't handle interactive kanban.
Revised approach: Svelte compiler only, no SvelteKit
5 flat files, no directories:
User stories
Human: As the superuser, I can interact with my kanban board visually — drag to reorder priority, filter by type, expand children — so that the board is a thinking tool I use daily.
AI: As an AI agent (Betty Sue), I need the human to verify board state visually, so that column flow violations, priority mistakes, and stale items are caught by human eyes.
Key design decisions
.svelte files ARE HTML— promotes directly to pal-e-app with zero translationapp.cssis pure CSS, no Tailwind — playground→production copy-pastenpm run devfor hot reload iteration,npm run buildoutputs static files for playground nginxAcceptance criteria (unchanged)