Templates
Templates define page-level shells and composition rules. They do not replace shortcode authoring or renderer logic.
Each section keeps one preview and a short constraint note.
Generic reading shell
The default page and single templates frame reading content without taking reusable rendering away from the plugin.
Preview
Case Study
Portfolio
Reducing Cognitive Load During Peak Traffic
The Company approached its holiday campaigns with a clear ambition: convert seasonal traffic into meaningful engagement and confident purchasing decisions.
Earlier campaigns assumed that high holiday intent meant users already understood the product value and needed only visual appeal and refreshed layouts to convert. In reality, users required reassurance, guidance, and clearer differentiation, especially under time pressure.
I led UX research and usability testing across successive holiday campaigns, guiding their evolution from surface-level optimisation toward behaviourally informed experiences.
- Constraint: the shell frames the page, but the dominant reading structure still belongs to the component family inside content.
Global shell header and footer
The site header and footer are shell-owned global structures. They frame plain pages, singles, docs pages, and archives, but they are not plugin components.
- Ownership: theme shell
- Scope: global banner, primary navigation, and contentinfo
- Accessibility contract: shell navigation landmarks are explicitly labeled Primary, Connect, Areas of Practice, and Experiment
- Constraint: document these as shell structures, not as az_visual families
Archive shell
Archive templates provide shared framing and card layout while the queried posts supply the real content.
Facilitation template specimen
Geometries of Use is the clearest dedicated template specimen in the current system.
Preview
Facilitation Specimen
Facilitation
Geometries of Use is a facilitation page built from service blueprint logic. It does not replace the blueprint. It adds a compact visual language for reading what kind of condition is taking shape in a service moment: access, threshold, interruption, dependency, shelter, exchange, return.
The page is meant to sit between editorial explanation and workshop material. It translates observations from research, case studies, and reflective writing into artefacts that teams can compare, move around, and discuss while a problem is still open enough to be reframed.
Jump to the paired comparison cardsStarter set
Four starting signals for reading entry, continuity, and backstage support before the discussion becomes too abstract.
- Constraint: this remains a validated specimen, not a plugin-side shortcode family.
Docs page shell
Docs pages are ordinary WordPress pages that enter the normal shell and then render the dedicated az_docs organism.
Preview
Docs Layout
Shared structural patterns
Across the live runtime, the most common shared pattern is item-plus-fields. The generic visual parser reads az_item blocks, collects az_field name values, normalizes az_list content into point arrays, and turns az_section or az_substep content into titled body sections. That pattern powers the validated tabbed / indexed reader family.
The docs path uses a narrower grammar. az_docs accepts az_field name=”intro” and az_field name=”body”, a top-level az_list name=”points”, nested az_section blocks, and nested az_example blocks. The docs renderer then decides whether the current page is acting as an overview or as a section detail view.
The case-study family is separate and explicit. It uses az_case_hero, az_case_facts, az_case_fact, az_case_section, az_case_figure, az_case_video, az_case_related, and az_case_link rather than the generic az_item grammar.
- Constraint: this preview is intentionally a minimal docs fragment rather than a recursive full docs page.