Skip to main content

Blueprint / reusable engineering asset

Blueprint-Nonprofit-Editorial

A canonical HubZero nonprofit reference implementation combining mission, programmes, impact reporting, field reporting, organisational accountability, and participation pathways in a publication-oriented editorial experience.

fieldstone-hero

System specification / v1.0.0

What is designed to be reused

Information architecture
Nonprofit
Design language
Editorial
Revision
Version 1.0.0

Included capabilities

  • Editorial nonprofit architecture
  • Programme directory & experiences
  • Impact & financial reporting
  • Six-region Field Notes
  • Long-form story publishing
  • Searchable story archive
  • Donation, volunteer & partner flows
  • Accessible, SEO-ready architecture

Documentation / implementation reference

Implementation guidance

Executive summary

The Nonprofit × Editorial blueprint is a canonical reference implementation for mission-led organisations. It demonstrates how to combine complex information architectures—programmes, impact reporting, field notes, and stories—into a cohesive editorial experience without relying on a CMS or backend database.

Fieldstone Collective home page masthead
The home page prioritizes the editorial mission statement over promotional imagery, establishing a narrative-first hierarchy.

Core engineering decisions

The architecture is strictly server-first. Content is defined in typed TypeScript modules and joined by slugs at build time, eliminating request-time data fetching and loading waterfalls. This approach ensures high performance and deterministic output while maintaining a complex, cross-referenced information architecture.

Interactivity is limited to 'client islands'—isolated components that require browser state such as the responsive navigation drawer, search filtering, and scroll-aware masthead transitions. This minimizes hydration overhead and keeps the majority of the site as static HTML.

Editorial design system

The design language focuses on typography as the primary driver of identity. Using Source Serif 4 for prose and Inter for interface elements, the system enforces a clear visual hierarchy. Surface-aware styling uses CSS custom properties to handle dark-mode section transitions automatically, ensuring consistent application of the color palette without manual prop drilling.

Limitations and considerations

The Fieldstone Collective implementation serves as a reference, not a production-ready application for real organisations. It intentionally omits backend services like payment processing or form handling, providing honest, inert alternatives instead. Developers should note that the mobile drawer does not implement a full cyclic focus trap, which may be required for specific accessibility compliance levels in production environments.