What it is
Most themes carry opinionated layouts: sidebars, multi-column grids, sticky headers, built-in sliders. The Wigmorean Theme deliberately does none of that. It's a clean canvas: fixed nav, single-column content, carefully tuned typography. Marketing pages render themselves via wigmorean-pages; everything else (blog, search, 404, archives) falls through to the theme's minimal templates.
Template files
header.php— fixed nav with fonts preloadedfooter.php— one-line copyright + navsingle.php— blog post layout (eyebrow + title + date + content)page.php— WP page layout (wigmorean-pages overrides for matched pages)index.php— fallback for archives, search, blog home404.php— italic rust 404 glyph + back buttonsidebar.php— intentionally empty (theme is single-column)
CSS tokens
Every color and spacing value lives in custom properties at the top of style.css. Override them in a child theme to rebrand:
:root {
--cream: #faf8f5;
--rust: #c4572a;
--gold: #b8943e;
--text: #1a1a1a;
--text-2: #6b6560;
}
Customizer options
Via Appearance → Customize:
- Site identity — logo, site title, tagline
- Colors — override any CSS token from a color picker
- Typography — heading/body font family (DM Serif Display + Outfit by default)
- Navigation — primary menu + contact CTA
Changes preview live, then save to persist.
Supported features
- Post thumbnails, post formats, custom backgrounds, HTML5 markup
- Gutenberg wide and full-width alignments
- Editor-style styles (Gutenberg previews match the frontend)
- Block patterns (three curated starter patterns for blog posts)
Forking vs child theme
For light changes, always create a child theme — Theme Development walks through it. Forking the whole theme is overkill for CSS tweaks and disconnects you from upstream improvements.