Services Hub and Industry Pages

Date: 2026-05-23 Branch: homepage-refresh Status: Approved design, pending spec review

Goal

Close two gaps in the refreshed site:

A cumulative services hub at /services/ that introduces every service in one place. Today the "Solutions" mega-menu top-level link points to #; this page becomes its destination.
Six industry landing pages under /industries/ that speak to a specific vertical, map our services to that vertical's problems, and surface the real case studies we have in that space.

Both serve the launch goal of 100 new customers in 12 months: the hub is an internal routing and SEO surface, the industry pages are keyword-targeted entry points that convert through to "Talk to Us".

SEO is a first-class requirement. Copy here is a solid first draft with complete SEO scaffolding (meta tags, keywords, FAQ JSON-LD, internal linking, canonical). The user will layer a Codex SEO pass on top, so structure and scaffolding must be complete and correct even where copy will later be refined.

Approach

Reuse the existing service-modern design system. No new SCSS, no inline styles. Try existing classes first, restructure HAML second.
The hub mirrors consulting/index.html.haml (clickable .cards.three / %a.card.blue offering cards, trust bar, CTA), scaled to cover all services.
Each industry page mirrors cloudmanagement/index.html.haml (layout: base, type: service, css: service-modern, banner via frontmatter).
Case studies are hand-curated per page rendered in the existing .case-studies-grid / .case-study-card markup. No industry: tagging of customer files. Each page hard-picks its 2 to 3 strongest, and stays trivially editable when a pending client lands.

Phase 1: Services hub

File: services/index.html.haml

Frontmatter: layout: base, type: service, css: service-modern, full SEO set (title, meta_title, meta_description, keywords, description), banner + mobile_banner + tablet_banner (reuse an existing banner image already in the repo), banner_title, banner_sub, search: high.

Sections (top to bottom):

Hero (frontmatter banner).
.container.inner intro: one short positioning paragraph + Talk to Us button.
Grouped offering cards, using .cards.three (or .cards.four) with %a.card.blue, one group per mega-menu category, each card = %h3 + %p + %span.read-more:
- Get Started: KickOff /products/kickoff/, SecureCompass /products/securecompass/, Focused AWS Review /consulting/services/discovery-and-review/, AWS Cost & Reliability Review /aws-cost-reliability-review/, AWS Downtime & Reliability Review /aws-downtime-reliability-review/.
- Managed Services: Cloud Management /cloudmanagement/, Platform Engineering /platform-engineering/, Compliance and Risk /security/.
- Bundled Engagement: DevOps as a Service /devops/.
- Specialist Engagements: Migration /consulting/services/cloud-migration/, AI Factory /artificialintelligence/aifactory/, Generative AI /artificialintelligence/generativeai/, Data /artificialintelligence/data/, SaaS CTO /consulting/services/saas-cto/.
.svc-trust-bar (AWS DevOps Competency, ISO 27001, AWS SaaS Competency), as in consulting/index.html.haml.
.section-testimonials reusing 3 existing testimonial cards.
.section-cta "Not sure where to start" + Talk to Us.
%a#contact + = partial("contact_forms/inbuilt_contact_form.html.haml").

JSON-LD: an OfferCatalog block listing the services (extend the pattern already present in _layouts/home-v4.html.haml).

Nav wiring: in _partials/navigation/header_navigation_v4.html.haml, change the two "Solutions" top-level links (mobile nav line 4, desktop mega-dropdown line 98) from # to /services/.

Phase 2: Industries

2a. Industries index (lean)

File: industries/index.html.haml. Same skeleton as consulting/index.html.haml: hero, intro, one .cards grid of 6 clickable cards (one per industry), trust bar, CTA, contact form. Acts as the landing target for the top-level Industries nav item and an SEO hub that internally links to all six.

2b. Six industry pages

Files: industries/<slug>/index.html.haml

Industry	Slug	Page title direction
SaaS & ISVs	`saas-and-isvs`	AWS for SaaS and ISVs
Financial Services	`financial-services`	AWS for Financial Services
Healthcare & Life Sciences	`healthcare-and-life-sciences`	AWS for Healthcare and Life Sciences
Government & Enterprise	`government-and-enterprise`	AWS for Government, Public Sector and Enterprise
Media	`media`	AWS for Media and Streaming
Education	`education`	AWS for Education and EdTech

Section structure per page (mirrors cloudmanagement/index.html.haml):

Hero (frontmatter banner, industry-specific banner_title / banner_sub).
.container.inner intro paragraph + Talk to Us.
Pain points as .svc-what-you-get > .svc-wyg-grid with 3 to 4 .svc-wyg-card (alternating .bg-green / .bg-blue, inline SVG icon, %h4 + %p) naming the industry's real problems.
How we help as a .cards grid of %a.card.blue linking to the relevant existing service pages (mapped per industry below).
.svc-trust-bar with the certifications most relevant to that industry.
Case studies as .case-studies-grid with the hand-curated cards below (logo + description + read-more only, per house rule).
Industry FAQ partial (see 2c).
.svc-crosslink-section "Not quite what you need?" linking to true alternatives (other industries or core services), per the crosslink rule.
.section-cta + %a#contact + inbuilt contact form.

Service mapping for "How we help" (true paths only):

SaaS & ISVs: DevOps as a Service, Platform Engineering, Cloud Management, SaaS CTO.
Financial Services: Compliance and Risk /security/, Cloud Management, DevOps as a Service, Focused AWS Review.
Healthcare & Life Sciences: Compliance and Risk /security/, Cloud Management, DevOps as a Service, Migration.
Government & Enterprise: Compliance and Risk /security/, Cloud Management, Migration, Platform Engineering.
Media: Platform Engineering, Cloud Management, DevOps as a Service, Migration.
Education: Cloud Management, DevOps as a Service, Compliance and Risk /security/, Migration.

Compliance posture (Financial Services, Healthcare, Government): lead with real credentials only: ISO 27001 certified, APRA CPS 234 compliant, "SOC 2 audit support" (never "SOC 2 compliant"), data residency and segregation, everything in the customer's own AWS account. Show approval and change-control gates where relevant. No invented SLAs, savings percentages or customer counts beyond the canonical set (18+ years, 1000+ migrations, 200+ customers, founded 2005, 5 countries).

2c. Six FAQ partials

Files: _partials/faq_saas.html.haml, faq_financial_services.html.haml, faq_healthcare.html.haml, faq_government_enterprise.html.haml, faq_media.html.haml, faq_education.html.haml.

Each follows faq_devops.html.haml exactly: a FAQPage JSON-LD block followed by .svc-faq-section > .svc-faq-inner > .svc-faq-grid with 6 .svc-faq-card (%h4 question + %p answer). Never accordion. No offboarding, exit or handover questions. Questions are industry-specific (e.g. FS: CPS 234, data residency; Education: seasonal scaling, student data privacy).

Add a new top-level Industries dropdown in _partials/navigation/header_navigation_v4.html.haml, in both the mobile #mobile-nav list and the desktop .nav list (as a .has_children with a %ul.children of 6 links, alongside the existing .full-nav-only items). Parent link targets /industries/. Footer changes are out of scope for this pass.

Case study mapping (hand-curated, real data from customers/customer/*.md)

Industry	Cards (logo + description + read-more)
SaaS & ISVs	Dubber, Tuned Global, Attache, Loop11, DingGo
Financial Services	Parakeet (PCI compliance 3x faster, 53% saved), Tallie, Attache
Education	Boddle (50x growth, 85% less downtime), Open Universities Australia
Healthcare & Life Sciences	Carbon Diet Coach (wellness), plus compliance-led narrative; leave structure for pending clients
Government & Enterprise	Emergency Management Victoria, RSL Art Union, Service Stream, SA Power, VISY
Media	Sardius Media (live video), Tuned Global (music, millions), All Day, JUST AUTO

Cards render only customers that have a real description. EMV has a strong testimonial but an empty description, so feature it via a testimonial card rather than a case-study card on the Government page.

SEO requirements (every new page)

Distinct meta_title, meta_description, keywords, description in frontmatter.
Canonical handled by _layouts/base.html.haml (automatic from page.url).
FAQPage JSON-LD on each industry page via its FAQ partial.
OfferCatalog / Service JSON-LD on the services hub.
Internal linking: hub links to all services; industry pages link to mapped services and to alternative industries; industries index links to all six.
Real H1 from banner_title, real %h2 section headings, descriptive alt text.

Conventions and constraints

SCSS is ASCII-only; HAML copy avoids em-dashes and en-dashes, avoids the Oxford comma, avoids stacked staccato full stops, avoids transactional jargon (sold, retainer, purchase, billable).
No pricing anywhere; route price questions to a call.
Reuse existing classes; no new SCSS, no inline :style.
Verify every internal href against a real path. Compliance and Risk is /security/.
Case-study cards: logo + description + read-more only. No title or industry line.
Vendor-neutral when describing integrations.
Crosslinks must be true alternatives.
Solid first-draft copy; do not pad for completeness.

File manifest

New: - services/index.html.haml - industries/index.html.haml - industries/saas-and-isvs/index.html.haml - industries/financial-services/index.html.haml - industries/healthcare-and-life-sciences/index.html.haml - industries/government-and-enterprise/index.html.haml - industries/media/index.html.haml - industries/education/index.html.haml - _partials/faq_saas.html.haml - _partials/faq_financial_services.html.haml - _partials/faq_healthcare.html.haml - _partials/faq_government_enterprise.html.haml - _partials/faq_media.html.haml - _partials/faq_education.html.haml

Edited: - _partials/navigation/header_navigation_v4.html.haml (Solutions link to /services/; new Industries top-level dropdown in mobile and desktop nav).

Build and review

The user runs the Awestruct build (no build steps performed here). The user runs a Codex review pass after implementation, so diffs stay scoped and decisions explicit.

Open notes

Healthcare case studies are thin by design; pages built compliant-led with Carbon as the single wellness proof point. Revisit when pending healthcare or life-sciences clients are referenceable.
The existing /aws-saas-solutions/ page (AWS SaaS Competency, thin) is left as is. The SaaS industry page links to it where the AWS SaaS Competency story is relevant.