Bansos Develop Feature

Goal

Ship focused bansos.dev improvements that preserve the static SvelteKit architecture, SEO quality, contributor workflow, and small open-source PR style.

Workflow

1. Identify the smallest files needed for the requested UI or feature change.
2. Follow the existing SvelteKit, component, and data conventions before introducing new abstractions.
3. Keep the site static-friendly for Cloudflare Pages. Avoid server-only state, databases, secrets in client code, and runtime-only dependencies unless the user explicitly wants an architecture change.
4. Preserve SEO basics for public pages: useful titles, descriptions, canonical/social metadata when the local pattern supports them, and crawlable content.
5. For UI changes, keep desktop clean and make mobile feel native: tight spacing, readable text, stable tap targets, and bottom navigation where the existing design uses it.
6. For data or contributor changes, coordinate with the bansos entry workflow instead of bypassing validation.
7. Run the narrowest useful validation when the user asks for testing or when the change affects shared behavior.
8. Prepare PRs with a clear summary, screenshots or preview notes for UI work, and explicit source/evidence notes for SEO or data behavior.

Project Constraints