Essential session storage is required to sign in. Optional analytics remain off unless you allow them.
Build a small editorial site with an original block theme. Define a plugin-owned content model, a bounded theme.json design system, semantic templates and parts, two reusable patterns, responsive behavior, keyboard-visible focus, long and missing-content fixtures, clean local setup, and a production build. Measure one representative page before and after asset or image optimization and publish the verification evidence.
Content types, taxonomies, metadata, fixtures, and capabilities support the stated workflow, and persistent domain behavior remains portable across a theme change.
Templates, parts, patterns, and theme.json have distinct responsibilities, avoid copied compositions, and provide a coherent editor experience.
Semantic landmarks, focus, keyboard flow, contrast, long text, missing media, and mobile-to-desktop layouts are verified without incoherent overflow.
A clean setup path, build command, representative fixtures, before/after measurements, and deployed smoke checks make the result reproducible.
Use this README structure to make the work reviewable.
DevPath fetches a read-only, size-capped snapshot. Submitted code is never executed.
# A custom block theme ## Goal Build a small editorial site with an original block theme. Define a plugin-owned content model, a bounded theme.json design system, semantic templates and parts, two reusable patterns, responsive behavior, keyboard-visible focus, long and missing-content fixtures, clean local setup, and a production build. Measure one representative page before and after asset or image optimization and publish the verification evidence. ## Acceptance criteria - [ ] Editorial model and portability: Content types, taxonomies, metadata, fixtures, and capabilities support the stated workflow, and persistent domain behavior remains portable across a theme change. - [ ] Block-theme architecture: Templates, parts, patterns, and theme.json have distinct responsibilities, avoid copied compositions, and provide a coherent editor experience. - [ ] Accessible responsive rendering: Semantic landmarks, focus, keyboard flow, contrast, long text, missing media, and mobile-to-desktop layouts are verified without incoherent overflow. - [ ] Reproduction and performance evidence: A clean setup path, build command, representative fixtures, before/after measurements, and deployed smoke checks make the result reproducible. ## Verification - [ ] Document installation and run commands. - [ ] Record automated checks and their exact commands. - [ ] Add representative output, screenshots, or a short demo where useful. - [ ] Confirm failure paths and known constraints. ## Decision log ### Decision title - Context: - Choice: - Alternatives considered: - Tradeoffs: ## Evidence - Link each rubric criterion to the file, test, or artifact that demonstrates it. ## Known limitations - List what is intentionally out of scope and what should be improved next.