Scaffold SvelteKit product runtime #2

New issue

Closed

opened 2026-06-18 16:11:44 +02:00 by vince · 0 comments

vince commented

2026-06-18 16:11:44 +02:00

Owner

Parent: #1

Goal

Create the first real website/app foundation for the Homepage competitor using SvelteKit and TypeScript. This replaces the idea of extending Homepage config with a proper product runtime.

Scope

Scaffold a SvelteKit + TypeScript app in the repository.
Configure a Node/container-friendly adapter and basic scripts for dev, check, build, and preview.
Add the top-level route structure for the one-page dashboard app.
Add a minimal server-side data-loading path that can later read a fixture dashboard model through the validation layer.
Add project README notes for local development and production shape.
Ensure no Homepage runtime, Homepage config, or Homepage-specific frontend code is used as a dependency.

Initial dependency decisions

Use SvelteKit, TypeScript, Vite, and a Node/container adapter.
Add vitest only if needed for scaffold-level checks; deeper tests belong in later issues.
Do not add Tailwind, a large UI kit, Redux-style state management, or charting libraries in this scaffold PR.
Keep package setup minimal so later PRs introduce TypeBox/Ajv, Drizzle, Iconify, uPlot, Playwright, and MCP deliberately.

Acceptance criteria

npm run dev starts a local app.
npm run build succeeds.
The initial route renders a placeholder dashboard shell from app-owned code.
The repo has a clear package/script baseline for future PRs.
README explains that this is a standalone product runtime, not a Homepage customization.

Out of scope

Final brutalist visual system.
Agent configuration API.
Live telemetry integrations.

Parent: #1 ## Goal Create the first real website/app foundation for the Homepage competitor using SvelteKit and TypeScript. This replaces the idea of extending Homepage config with a proper product runtime. ## Scope - Scaffold a SvelteKit + TypeScript app in the repository. - Configure a Node/container-friendly adapter and basic scripts for dev, check, build, and preview. - Add the top-level route structure for the one-page dashboard app. - Add a minimal server-side data-loading path that can later read a fixture dashboard model through the validation layer. - Add project README notes for local development and production shape. - Ensure no Homepage runtime, Homepage config, or Homepage-specific frontend code is used as a dependency. ## Initial dependency decisions - Use SvelteKit, TypeScript, Vite, and a Node/container adapter. - Add `vitest` only if needed for scaffold-level checks; deeper tests belong in later issues. - Do not add Tailwind, a large UI kit, Redux-style state management, or charting libraries in this scaffold PR. - Keep package setup minimal so later PRs introduce TypeBox/Ajv, Drizzle, Iconify, uPlot, Playwright, and MCP deliberately. ## Acceptance criteria - `npm run dev` starts a local app. - `npm run build` succeeds. - The initial route renders a placeholder dashboard shell from app-owned code. - The repo has a clear package/script baseline for future PRs. - README explains that this is a standalone product runtime, not a Homepage customization. ## Out of scope - Final brutalist visual system. - Agent configuration API. - Live telemetry integrations.