Playground: search page prototype #3

Closed
opened 2026-03-27 07:53:23 +00:00 by forgejo_admin · 0 comments
Contributor

Type

Feature

Lineage

Discovered scope from pal-e-app#65 alignment review. The review AC included "search page spec added to playground" but conflicted with the "read-only, no code changes" constraint. Broken out as its own ticket.

Repo

forgejo_admin/pal-e-docs-playground

User Story

As a reader searching the knowledge base,
I want a search results page prototype in the playground,
So that the SvelteKit port includes search from day one.

Context

The alignment review (pal-e-app#65) identified that the playground has 6 pages but no search page. The existing pal-e-app has a search route (/search) with working API integration. This prototype should validate the search UX before the SvelteKit port.

File Targets

  • ~/pal-e-docs-playground/search.html — new file
  • ~/pal-e-docs-playground/app.css — may need search-specific styles
  • ~/pal-e-docs-playground/index.html — add nav link to search

Acceptance Criteria

  • Search results page prototype with hardcoded sample results
  • Consistent with playground design system (app.css)
  • Mobile-first layout
  • Data contract comments (@route, @data, @api) for SvelteKit port
  • Navigation updated to include search

Test Expectations

  • No code to test — this is a static HTML prototype
  • Run command: Open search.html in browser, verify layout on mobile viewport

Constraints

  • Vanilla HTML/CSS/JS only — no build tools
  • Hardcoded data, no live API calls

Checklist

  • search.html created with data contracts
  • Navigation links updated
  • Mobile-first verified on phone
  • forgejo_admin/pal-e-app#65 — alignment review that identified this gap
  • story:superuser-query — search user story
  • board-pal-e-docs — project board
### Type Feature ### Lineage Discovered scope from pal-e-app#65 alignment review. The review AC included "search page spec added to playground" but conflicted with the "read-only, no code changes" constraint. Broken out as its own ticket. ### Repo `forgejo_admin/pal-e-docs-playground` ### User Story As a reader searching the knowledge base, I want a search results page prototype in the playground, So that the SvelteKit port includes search from day one. ### Context The alignment review (pal-e-app#65) identified that the playground has 6 pages but no search page. The existing pal-e-app has a search route (`/search`) with working API integration. This prototype should validate the search UX before the SvelteKit port. ### File Targets - `~/pal-e-docs-playground/search.html` — new file - `~/pal-e-docs-playground/app.css` — may need search-specific styles - `~/pal-e-docs-playground/index.html` — add nav link to search ### Acceptance Criteria - [ ] Search results page prototype with hardcoded sample results - [ ] Consistent with playground design system (app.css) - [ ] Mobile-first layout - [ ] Data contract comments (@route, @data, @api) for SvelteKit port - [ ] Navigation updated to include search ### Test Expectations - [ ] No code to test — this is a static HTML prototype - Run command: Open `search.html` in browser, verify layout on mobile viewport ### Constraints - Vanilla HTML/CSS/JS only — no build tools - Hardcoded data, no live API calls ### Checklist - [ ] search.html created with data contracts - [ ] Navigation links updated - [ ] Mobile-first verified on phone ### Related - `forgejo_admin/pal-e-app#65` — alignment review that identified this gap - `story:superuser-query` — search user story - `board-pal-e-docs` — project board
Commenting is not possible because the repository is archived.
No labels
No milestone
No project
No assignees
1 participant
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
ldraney/pal-e-docs-playground#3
No description provided.