Crane Design System

Templates and Editable Page Models

Templates turn the visual design system into maintainable pages. Editors manage structured content; the system controls layout, semantics, styling, and schema.

Template Library

The template library should stay small. Add a new template only when the information architecture or content model materially changes.

HomePageTemplate

Enterprise homepage for industry-led positioning, capabilities, technology proof, and conversion.

Sections

  • Hero with metrics
  • Quick actions
  • Industry cards
  • Capability cards
  • Technology band
  • Proof cards
  • Final CTA

Editable Fields

  • Hero copy
  • Metrics
  • Industry cards
  • Capability summaries
  • Proof cards
  • CTA labels and URLs

IndustryPageTemplate

Reusable industry detail page. Aerospace is the first implementation.

Sections

  • Hero with badges
  • Risk grid
  • Service solution cards
  • Why choose Crane
  • Technology band
  • Case studies
  • Final CTA

Editable Fields

  • Industry title
  • Risk cards
  • Service relationships
  • Differentiators
  • Case studies
  • SEO fields

ServiceIndexTemplate / ServicePageTemplate

Service discovery and detail pages for freight, logistics, compliance, and time-critical capabilities.

Sections

  • Service hero
  • Overview
  • Capability cards
  • Related industries
  • FAQ
  • CTA

Editable Fields

  • Service copy
  • Capabilities
  • Industry relationships
  • FAQ
  • SEO fields

IndustryIndexTemplate

Index page that exposes industry solution pages and their structured relationships.

Sections

  • Index hero
  • Industry cards
  • Internal links

Editable Fields

  • Industry records
  • Descriptions
  • SEO fields

TechnologyProductTemplate

Technology/product page for visibility, analytics, and operational workflows.

Sections

  • Technology hero
  • Product cards
  • Integration relationships
  • CTA

Editable Fields

  • Product names
  • Features
  • Integration list
  • CTA fields

InsightArticleTemplate

Semantic article page for insight content and related internal links.

Sections

  • Article hero
  • Body sections
  • Related links

Editable Fields

  • Article metadata
  • Body sections
  • Related pages
  • SEO fields

CaseStudyTemplate

Proof page connecting challenge, solution, outcome, metrics, services, and industries.

Sections

  • Case-study hero
  • Metrics
  • Challenge/solution/outcome
  • Related expertise
  • CTA

Editable Fields

  • Problem statement
  • Metrics
  • Relationships
  • SEO fields

LocationFinderTemplate

Crawlable location directory with a client-side map/filter island.

Sections

  • Hero with metrics
  • Filter controls
  • Map region
  • Location result cards

Editable Fields

  • Intro copy
  • Generated location records
  • Region/service/industry relationships

LocationTemplate

Server-rendered location detail page using structured Sanity location data.

Sections

  • Location hero
  • Contact
  • Quick facts
  • About
  • Services
  • Industries
  • Capabilities
  • Related locations
  • FAQ
  • CTA

Editable Fields

  • Location fields
  • Quick facts
  • Related records
  • FAQ
  • CTA URL
  • SEO fields

Section Patterns

Sections are reusable content structures that appear across templates. They are not freeform layout blocks.

Risk / Problem Grid

AOG downtime costs

Short operational explanation with one or two concrete proof bullets.

Regulatory compliance

Short operational explanation with one or two concrete proof bullets.

Global MRO supply

Short operational explanation with one or two concrete proof bullets.

Visibility gaps

Short operational explanation with one or two concrete proof bullets.

Service Solution Cards

Time Critical

Service summary, capability bullets, outcome statement, and internal service link.

Learn More →

Air Freight

Service summary, capability bullets, outcome statement, and internal service link.

Learn More →

How Changes Cascade

Approved Path

  1. Document the decision on the published design-system page.
  2. Update tokens or reusable components.
  3. Let templates inherit the change.
  4. Keep editor content structured and layout-safe.

Governance

Do not solve page-by-page.

If a page needs something new, classify it as a component variant, template section, data-only change, or anti-pattern before implementation.