forgejo_admin/pal-e-docs-app

Fork 0

Port: project page from playground #73

New issue

Closed

opened 2026-03-27 21:14:47 +00:00 by forgejo_admin · 2 comments

forgejo_admin commented

2026-03-27 21:14:47 +00:00

Owner

Type

Feature

Lineage

Depends on #68 (CSS + sidebar foundation). Part of SvelteKit port pipeline.

Repo

forgejo_admin/pal-e-app

User Story

As a user, I want project pages with architecture diagrams and structured sections, matching the playground design.

Context

Port ~/pal-e-docs-playground/note-project.html to the project page renderer. Projects live at src/routes/projects/[slug]/+page.svelte (NOT notes/[slug]). Project pages have Vision, User Stories, Architecture, Board sections. Data fetching uses client-side onMount, not SvelteKit load functions — no +page.ts needed.

Note: Architecture diagram rendering (mermaid/SVG) is net-new functionality — the existing project page does not render diagrams. This may require adding mermaid rendering support.

File Targets

src/routes/projects/[slug]/+page.svelte — project page rendering (dedicated project route)
src/lib/components/ProjectLayout.svelte — existing project layout component (may need restyle)
May need project-specific layout component for architecture diagram section

Acceptance Criteria

Project page layout matches playground note-project.html
Architecture diagram section renders (net-new)
App builds without errors

Test Expectations

Run command: cd ~/pal-e-app && npm run build

Constraints

Copy playground HTML literally, swap data bindings.
Depends on #68 being merged first.

Checklist

Project page restyled
Architecture diagram rendering added
Build passes

forgejo_admin/pal-e-app#68 — foundation (dependency)
board-pal-e-docs — project board

### Type Feature ### Lineage Depends on #68 (CSS + sidebar foundation). Part of SvelteKit port pipeline. ### Repo `forgejo_admin/pal-e-app` ### User Story As a user, I want project pages with architecture diagrams and structured sections, matching the playground design. ### Context Port `~/pal-e-docs-playground/note-project.html` to the project page renderer. Projects live at `src/routes/projects/[slug]/+page.svelte` (NOT `notes/[slug]`). Project pages have Vision, User Stories, Architecture, Board sections. Data fetching uses client-side `onMount`, not SvelteKit load functions — no `+page.ts` needed. **Note:** Architecture diagram rendering (mermaid/SVG) is net-new functionality — the existing project page does not render diagrams. This may require adding mermaid rendering support. ### File Targets - `src/routes/projects/[slug]/+page.svelte` — project page rendering (dedicated project route) - `src/lib/components/ProjectLayout.svelte` — existing project layout component (may need restyle) - May need project-specific layout component for architecture diagram section ### Acceptance Criteria - [ ] Project page layout matches playground note-project.html - [ ] Architecture diagram section renders (net-new) - [ ] App builds without errors ### Test Expectations - Run command: `cd ~/pal-e-app && npm run build` ### Constraints - Copy playground HTML literally, swap data bindings. - Depends on #68 being merged first. ### Checklist - [ ] Project page restyled - [ ] Architecture diagram rendering added - [ ] Build passes ### Related - `forgejo_admin/pal-e-app#68` — foundation (dependency) - `board-pal-e-docs` — project board

forgejo_admin referenced this issue from a commit

2026-03-27 21:41:34 +00:00

feat: port project page layout from playground

forgejo_admin referenced this issue from a pull request that will close it,

2026-03-27 21:42:09 +00:00

feat: port project page layout from playground #80

forgejo_admin referenced this issue from a commit

2026-03-27 21:56:27 +00:00

feat: port project page layout from playground

forgejo_admin commented

2026-03-27 21:56:27 +00:00

Author

Owner

Scope Review: NEEDS_REFINEMENT

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

Three issues found:

Wrong file target: src/routes/notes/[slug]/+page.svelte — project pages live at src/routes/projects/[slug]/+page.svelte. Projects have a dedicated route at /projects/{slug} loading via listProjects API.
"Architecture diagram section renders" is net-new functionality — current project page has no architecture section. Needs clarification on how diagrams are stored (blocks? mermaid? inline HTML?).
"May need project-specific layout component" — replace vague language with a concrete decision.

## Scope Review: NEEDS_REFINEMENT Review note: `review-475-2026-03-27` Three issues found: - **Wrong file target**: `src/routes/notes/[slug]/+page.svelte` — project pages live at `src/routes/projects/[slug]/+page.svelte`. Projects have a dedicated route at `/projects/{slug}` loading via `listProjects` API. - "Architecture diagram section renders" is net-new functionality — current project page has no architecture section. Needs clarification on how diagrams are stored (blocks? mermaid? inline HTML?). - "May need project-specific layout component" — replace vague language with a concrete decision.

forgejo_admin closed this issue

2026-03-27 21:56:33 +00:00

forgejo_admin commented

2026-03-27 22:06:11 +00:00

Author

Owner

Issue body updated per scope review corrections.

forgejo_admin reopened this issue

2026-03-27 22:09:13 +00:00

forgejo_admin referenced this issue from a commit

2026-03-28 05:00:29 +00:00

feat: rewrite project route to use ProjectLayout with architecture diagrams