Services Hub and Industry Pages Implementation Plan

For agentic workers: REQUIRED SUB-SKILL: Use superpowers:subagent-driven-development (recommended) or superpowers:executing-plans to implement this plan task-by-task. Steps use checkbox (- [ ]) syntax for tracking.

Goal: Add a cumulative services hub at /services/ and six industry landing pages under /industries/, all on the existing service-modern design system, with complete SEO scaffolding.

Architecture: New Awestruct HAML pages reusing existing partials and CSS classes (no new SCSS, no inline styles). The hub mirrors consulting/index.html.haml; industry pages mirror cloudmanagement/index.html.haml. Case studies are hand-curated by customer slug from site.customer. Navigation gets the Solutions link repointed and a new top-level Industries dropdown.

Tech Stack: Awestruct, HAML, the service-modern CSS bundle. The user runs the build (gulp + Awestruct); do not run build or test commands. The user manages all git commits; do not stage or commit.

Conventions (apply to every file)

Reference A: Icon SVG library

Every pain-point card wraps its icon shapes in this exact opening tag (copied from cloudmanagement/index.html.haml):

haml %svg{xmlns: "http://www.w3.org/2000/svg", viewbox: "0 0 48 48", fill: "none", stroke: "rgba(255,255,255,0.7)", "stroke-width" => "1.5", "stroke-linecap" => "round", "stroke-linejoin" => "round"}

Inner shapes by icon name (indent one level under the %svg):

Reference B: Industry page skeleton

Every industry page (Tasks 5 to 10) uses this exact structure. Replace the <<...>> slots with the values given in each task. Card .bg-green / .bg-blue alternate in the order shown.

```haml

layout: base type: service css: service-modern title: «TITLE» meta_title: «META_TITLE» meta_description: «META_DESCRIPTION» keywords: «KEYWORDS» description: «DESCRIPTION» banner: /images/banners/webp/«BANNER».webp mobile_banner: /images/banners/webp/480/«BANNER»-480w.webp tablet_banner: /images/banners/webp/800/«BANNER»-800w.webp banner_title: «BANNER_TITLE» banner_sub: «BANNER_SUB» search: high flyout_active: false exit_popup_active: false —

content.page

.container.inner %h2 «INTRO_HEADING» %p.center «INTRO_PARA» .flex-container %a.btn-primary.blue.findoutmore.center{:href=>"#contact"} Talk to Us

%a#what-you-get .svc-what-you-get .svc-wyg-inner %h2 «PAIN_HEADING» .svc-wyg-grid -# 4 cards. For each: .svc-wyg-card.bg-green / .bg-blue, .svc-wyg-icon with -# the chosen Reference A icon, %h4 title, %p copy. «PAIN_CARDS»

.container.inner %h2 How we help %p.center «HELP_SUB» .cards.«CARDS_COUNT_WORD» «SERVICE_CARDS»

.svc-trust-bar .svc-trust-inner %p.svc-trust-label Audited and certified .svc-trust-badges «TRUST_BADGES»

.container.inner %h2.center Case Studies %p.center.case-studies-intro «CASE_INTRO» .case-studies-grid «CASE_STUDY_RENDER» .case-studies-cta %a.btn-primary.blue.findoutmore{:href=>"/customers/"} See More Results

«OPTIONAL_TESTIMONIALS»

= partial "«FAQ_PARTIAL»"

.svc-crosslink-section .svc-crosslink-inner %h2 Not quite what you need? %p Every team is different. These may fit better. .svc-crosslinks «CROSSLINKS»

.section-cta .section-inner .cta-content %h2.cta-heading «CTA_HEADING» %p.cta-sub «CTA_SUB» .cta-actions %a.cta-primary{:href => "#contact"} Talk to Us

%a#contact = partial("contact_forms/inbuilt_contact_form.html.haml") ```

Note: .section-cta sits inside #content.page in cloudmanagement but the crosslink section sits outside. Match cloudmanagement/index.html.haml: the .svc-crosslink-section and %a#contact are at top level (zero indent), and the .section-cta is the last block inside #content.page. To keep ordering correct, place .section-cta as the final child of #content.page (before the FAQ partial is fine; in cloudmanagement the CTA precedes the FAQ). Follow this order inside #content.page: intro, pain points, how we help, trust bar, case studies, optional testimonials, then .section-cta. Then at top level: FAQ partial, crosslink section, %a#contact, contact form. (This mirrors cloudmanagement/index.html.haml exactly.)

Pain card pattern (one card)

haml .svc-wyg-card.bg-green .svc-wyg-icon %svg{xmlns: "http://www.w3.org/2000/svg", viewbox: "0 0 48 48", fill: "none", stroke: "rgba(255,255,255,0.7)", "stroke-width" => "1.5", "stroke-linecap" => "round", "stroke-linejoin" => "round"} -# Reference A shapes for the chosen icon %h4 <<CARD_TITLE>> %p <<CARD_COPY>>

Service card pattern (one card)

haml %a.card.blue{:href => "<<SERVICE_PATH>>"} %h3 <<SERVICE_NAME>> %p <<SERVICE_BLURB>> %span.read-more Learn more &rarr;

Trust badge options (pick the three named in each task)

haml .svc-trust-badge %img{src: "/images/partners/2022_aws_partner.svg", alt: "AWS DevOps Competency Partner", loading: "lazy"} %span AWS DevOps Competency .svc-trust-badge %img{src: "/images/ISO-27001-certified_col.svg", alt: "ISO 27001 Certified", loading: "lazy"} %span ISO 27001 Certified .svc-trust-badge %img{src: "/images/partners/saas_dark_bckgnd.svg", alt: "AWS SaaS Competency", loading: "lazy"} %span AWS SaaS Competency

For APRA CPS 234 use a text-only badge (no logo asset exists), styled the same:

haml .svc-trust-badge %img{src: "/images/security-compliances.svg", alt: "Security accreditations and compliance", loading: "lazy"} %span APRA CPS 234

Reference C: Case-study render snippet (curated by slug)

site.customer is a hash keyed by the customer filename slug (for example customers/customer/dubber.md is site.customer['dubber']). Render an ordered curated list. The conditional guards against any customer with a missing link or description.

haml - %w[<<SLUGS>>].each do |k| - a = site.customer[k] - if a && a.description.to_s.strip.length > 10 .case-study-card - if a.link.to_s.strip.length > 1 %a.case-study-card-link{href: "#{a.link}"} .case-study-header %img.case-study-logo{:src => "#{a.img}", :alt => "#{a.title}"} .case-study-content %p.case-study-description #{a.description} .case-study-link %span.read-more Read Case Study &rarr; - else .case-study-card-link .case-study-header %img.case-study-logo{:src => "#{a.img}", :alt => "#{a.title}"} .case-study-content %p.case-study-description #{a.description}

Reference D: FAQ partial skeleton

Every FAQ partial (one per industry) follows faq_devops.html.haml exactly: a FAQPage JSON-LD block, then .svc-faq-section. The JSON-LD mainEntity array must contain the same six questions and answers as the visible cards (text can be a touch shorter in JSON-LD, same meaning). Never accordion. No offboarding, exit or handover questions.

```haml -# «INDUSTRY» FAQ Partial -# Usage: = partial "«FAQ_PARTIAL»"

-# SEO Structured Data for FAQ %script{:type => "application/ld+json"} :plain { "@context": "https://schema.org", "@type": "FAQPage", "mainEntity": [ { "@type": "Question", "name": "«Q1»", "acceptedAnswer": { "@type": "Answer", "text": "«A1»" } }, { "@type": "Question", "name": "«Q2»", "acceptedAnswer": { "@type": "Answer", "text": "«A2»" } }, { "@type": "Question", "name": "«Q3»", "acceptedAnswer": { "@type": "Answer", "text": "«A3»" } }, { "@type": "Question", "name": "«Q4»", "acceptedAnswer": { "@type": "Answer", "text": "«A4»" } }, { "@type": "Question", "name": "«Q5»", "acceptedAnswer": { "@type": "Answer", "text": "«A5»" } }, { "@type": "Question", "name": "«Q6»", "acceptedAnswer": { "@type": "Answer", "text": "«A6»" } } ] }

.svc-faq-section .svc-faq-inner %h2 Frequently asked questions .svc-faq-grid .svc-faq-card %h4 «Q1» %p «A1» .svc-faq-card %h4 «Q2» %p «A2» .svc-faq-card %h4 «Q3» %p «A3» .svc-faq-card %h4 «Q4» %p «A4» .svc-faq-card %h4 «Q5» %p «A5» .svc-faq-card %h4 «Q6» %p «A6» ```

Task 1: Services hub page

Files: - Create: services/index.html.haml

```haml

layout: base type: service css: service-modern title: Cloud Services on AWS | base2Services meta_title: AWS Cloud Services | Managed, DevOps, Migration and AI | base2Services meta_description: Every base2Services offering on AWS in one place. Managed cloud operations, DevOps, platform engineering, compliance, migration and AI. Run in your own accounts with full handover. keywords: aws managed services, devops as a service, cloud management, platform engineering, aws migration, aws consulting, compliance, ai factory description: From your first AWS review to fully managed operations, compliance and AI. Pick where you are and we take it from there. banner: /images/banners/webp/mwm48207.webp mobile_banner: /images/banners/webp/480/mwm48207-480w.webp tablet_banner: /images/banners/webp/800/mwm48207-800w.webp banner_title: Cloud services, end to end banner_sub: From your first AWS review to fully managed operations, compliance and AI. Pick where you are and we take it from there. search: high flyout_active: false exit_popup_active: false —

content.page

.container.inner %h2 One partner across your whole AWS journey. %p.center Whether you start with a focused review or hand over day to day operations, every engagement runs in your own AWS accounts, with full handover and people you reach on Slack rather than a ticket queue. .flex-container %a.btn-primary.blue.findoutmore.center{:href=>"#contact"} Talk to Us

.container.inner %h2 Get started %p.center A low commitment first step that shows you exactly where you stand. .cards.three %a.card.blue{:href => "/products/kickoff/"} %h3 KickOff %p A guided assessment of your AWS environment that scores your readiness and hands you a prioritised action plan. %span.read-more Learn more → %a.card.blue{:href => "/products/securecompass/"} %h3 SecureCompass %p A free scan of your AWS security posture and public exposure, with findings ranked by impact. %span.read-more Learn more → %a.card.blue{:href => "/consulting/services/discovery-and-review/"} %h3 Focused AWS Review %p A structured Well-Architected assessment of architecture, security, cost and operations, prioritised for action. %span.read-more Learn more → %a.card.blue{:href => "/aws-cost-reliability-review/"} %h3 AWS Cost Review %p Find and remove waste in your AWS bill, with a clear view of how and where you save. %span.read-more Learn more → %a.card.blue{:href => "/aws-downtime-reliability-review/"} %h3 AWS Reliability Review %p Find the weak points behind recurring incidents and recovery risk before the next outage. %span.read-more Learn more →

.container.inner %h2 Managed services %p.center Hand over the running of your environment at a fixed monthly fee. .cards.three %a.card.blue{:href => "/cloudmanagement/"} %h3 Cloud Management %p 24/7 monitoring, incidents, patching, backups, cost management and security on AWS. %span.read-more Learn more → %a.card.blue{:href => "/platform-engineering/"} %h3 Platform Engineering %p The internal platform your developers build on, designed, built and run for you. %span.read-more Learn more → %a.card.blue{:href => "/security/"} %h3 Compliance and Risk %p Security and compliance run as an ongoing service, with the evidence your auditors expect. %span.read-more Learn more →

.container.inner %h2 Bundled and specialist engagements %p.center Scoped work with clear deliverables and full handover. .cards.three %a.card.blue{:href => "/devops/"} %h3 DevOps as a Service %p Managed DevOps on AWS covering pipelines, infrastructure and 24/7 support in one engagement. %span.read-more Learn more → %a.card.blue{:href => "/consulting/services/cloud-migration/"} %h3 Migration %p Move your workloads to AWS, assessed, planned and executed with minimal disruption. %span.read-more Learn more → %a.card.blue{:href => "/artificialintelligence/aifactory/"} %h3 AI Factory %p A managed AI backbone with guardrails, so you can build and run AI safely on AWS. %span.read-more Learn more → %a.card.blue{:href => "/artificialintelligence/generativeai/"} %h3 Generative AI %p Generative AI solutions designed, built and operated on secure AWS foundations. %span.read-more Learn more → %a.card.blue{:href => "/artificialintelligence/data/"} %h3 Data %p Get your data ready for analytics and AI, from pipelines to readiness assessment. %span.read-more Learn more → %a.card.blue{:href => "/consulting/services/saas-cto/"} %h3 SaaS CTO %p Fractional technology leadership for SaaS products scaling on AWS. %span.read-more Learn more →

.svc-trust-bar .svc-trust-inner %p.svc-trust-label Audited and certified .svc-trust-badges .svc-trust-badge %img{src: "/images/partners/2022_aws_partner.svg", alt: "AWS DevOps Competency Partner", loading: "lazy"} %span AWS DevOps Competency .svc-trust-badge %img{src: "/images/ISO-27001-certified_col.svg", alt: "ISO 27001 Certified", loading: "lazy"} %span ISO 27001 Certified .svc-trust-badge %img{src: "/images/partners/saas_dark_bckgnd.svg", alt: "AWS SaaS Competency", loading: "lazy"} %span AWS SaaS Competency

.section-testimonials .section-inner .testimonials-featured .testimonials-featured-inner %h2.testimonials-heading What our customers say .testimonials-grid .testimonial-card %img.testimonial-logo{src: "/images/customers/servicestream.svg", alt: "Service Stream", loading: "lazy"} %p.testimonial-quote base2Services capabilities with open source and cloud computing significantly reduced the business risk associated with a project of this size. .testimonial-author %span.author-name Alistair Legge %span.author-role CTO, Service Stream %a.testimonial-link{href: "/community/casestudies/info/servicestream-testimonial.html"} Read case study .testimonial-card %img.testimonial-logo{src: "/images/customers/urbanise.svg", alt: "Urbanise", loading: "lazy"} %p.testimonial-quote We went to Amazon and said, give us your best people. And they said, you don't want our people, you want base2Services. .testimonial-author %span.author-name Adam Bate %span.author-role Software Development Manager, Urbanise .testimonial-card %img.testimonial-logo{src: "/images/customers/emv.svg", alt: "Emergency Management Victoria", loading: "lazy"} %p.testimonial-quote base2 has been a long-term partner for us, providing ongoing infrastructure support and strong advice throughout our journey. .testimonial-author %span.author-name Michael Jenkins %span.author-role Chief Architect, Emergency Management Victoria

.section-cta .section-inner .cta-content %h2.cta-heading Not sure where to start? %p.cta-sub Tell us where you are and what you are trying to achieve. We will point you to the right starting point. .cta-actions %a.cta-primary{:href => "#contact"} Talk to Us

%a#contact = partial("contact_forms/inbuilt_contact_form.html.haml") ```

Check: every :href above matches a path verified to exist (/products/kickoff/, /products/securecompass/, /consulting/services/discovery-and-review/, /aws-cost-reliability-review/, /aws-downtime-reliability-review/, /cloudmanagement/, /platform-engineering/, /security/, /devops/, /consulting/services/cloud-migration/, /artificialintelligence/aifactory/, /artificialintelligence/generativeai/, /artificialintelligence/data/, /consulting/services/saas-cto/). File is ASCII only, no em-dash, two-space indent.

Files: - Modify: _partials/navigation/header_navigation_v4.html.haml

Find (around line 3 to 5):

haml %li.has_children %a{:href => "#"} Solutions

Replace the %a{:href => "#"} on that Solutions item with:

haml %a{:href => "/services/"} Solutions

Find (around line 97 to 99):

haml %li.has_children.mega-dropdown %a{:href => "#"} Solutions

Replace with:

haml %li.has_children.mega-dropdown %a{:href => "/services/"} Solutions

Only these two # Solutions links changed. No other nav entry touched in this task.

Task 3: Industries index page

Files: - Create: industries/index.html.haml

```haml

layout: base type: service css: service-modern title: Industries We Serve on AWS | base2Services meta_title: AWS Solutions by Industry | SaaS, Financial Services, Healthcare and More | base2Services meta_description: AWS expertise shaped to your sector. SaaS and ISVs, financial services, healthcare and life sciences, government and enterprise, media and education. keywords: aws by industry, saas aws, financial services aws, healthcare aws, government aws, media aws, education aws description: AWS expertise shaped to your sector, with the same foundation of security, reliability and cost control. banner: /images/banners/webp/mwm48212-customers.webp mobile_banner: /images/banners/webp/480/mwm48212-customers-480w.webp tablet_banner: /images/banners/webp/800/mwm48212-customers-800w.webp banner_title: Built for your industry banner_sub: AWS expertise shaped to the demands of your sector, with the same foundation of security, reliability and cost control underneath. search: high flyout_active: false exit_popup_active: false —

content.page

.container.inner %h2 Different sectors, different pressures. %p.center We bring the same AWS foundation of security, reliability and cost control, shaped to what your industry actually demands. Find your sector below. .flex-container %a.btn-primary.blue.findoutmore.center{:href=>"#contact"} Talk to Us

.container.inner %h2 Industries we serve %p.center Pick the sector closest to yours. .cards.three %a.card.blue{:href => "/industries/saas-and-isvs/"} %h3 SaaS and ISVs %p Run the AWS platform underneath your product so your engineers stay on the roadmap. %span.read-more Learn more → %a.card.blue{:href => "/industries/financial-services/"} %h3 Financial Services %p Regulated workloads on AWS, run to the standards your auditors and APRA expect. %span.read-more Learn more → %a.card.blue{:href => "/industries/healthcare-and-life-sciences/"} %h3 Healthcare and Life Sciences %p Sensitive data handled with the security and privacy your sector demands. %span.read-more Learn more → %a.card.blue{:href => "/industries/government-and-enterprise/"} %h3 Government and Enterprise %p Accountable organisations run on AWS with governance, security and resilience built in. %span.read-more Learn more → %a.card.blue{:href => "/industries/media/"} %h3 Media and Streaming %p Platforms that absorb traffic spikes and keep live and on demand experiences up. %span.read-more Learn more → %a.card.blue{:href => "/industries/education/"} %h3 Education and EdTech %p Platforms that scale through enrolment and exam peaks and protect student data. %span.read-more Learn more →

.svc-trust-bar .svc-trust-inner %p.svc-trust-label Audited and certified .svc-trust-badges .svc-trust-badge %img{src: "/images/partners/2022_aws_partner.svg", alt: "AWS DevOps Competency Partner", loading: "lazy"} %span AWS DevOps Competency .svc-trust-badge %img{src: "/images/ISO-27001-certified_col.svg", alt: "ISO 27001 Certified", loading: "lazy"} %span ISO 27001 Certified .svc-trust-badge %img{src: "/images/partners/saas_dark_bckgnd.svg", alt: "AWS SaaS Competency", loading: "lazy"} %span AWS SaaS Competency

.section-cta .section-inner .cta-content %h2.cta-heading Not sure which page fits? %p.cta-sub Tell us about your organisation and what you are trying to achieve. We will point you to the right place. .cta-actions %a.cta-primary{:href => "#contact"} Talk to Us

%a#contact = partial("contact_forms/inbuilt_contact_form.html.haml") ```

All six /industries/<slug>/ hrefs match the slugs created in Tasks 5 to 10. ASCII only, two-space indent.

Task 4: Add the Industries top-level nav dropdown

Files: - Modify: _partials/navigation/header_navigation_v4.html.haml

After the closing of the Solutions %li.has_children block (the mobile Solutions item ends at the SaaS CTO link, around line 47) and before the %li.has_children for "AWS Advanced Partner" (around line 48), insert this new %li at the same indentation as the other %li.has_children items under #mobile-nav %ul:

haml %li.has_children %a{:href => "/industries/"} Industries %ul.children %li %a{:href => "/industries/saas-and-isvs/"} SaaS &amp; ISVs %li %a{:href => "/industries/financial-services/"} Financial Services %li %a{:href => "/industries/healthcare-and-life-sciences/"} Healthcare &amp; Life Sciences %li %a{:href => "/industries/government-and-enterprise/"} Government &amp; Enterprise %li %a{:href => "/industries/media/"} Media %li %a{:href => "/industries/education/"} Education

In the desktop %ul.nav, immediately after the closing of the Solutions %li.has_children.mega-dropdown block (which ends at the SaaS CTO mega-menu link, around line 134) and before %li.has_children.more-dropdown (around line 135), insert this new top-level item at the same indentation as the other %li items under %ul.nav:

haml %li.has_children.full-nav-only %a{:href => "/industries/"} Industries %ul.children %li %a{:href => "/industries/saas-and-isvs/"} SaaS &amp; ISVs %li %a{:href => "/industries/financial-services/"} Financial Services %li %a{:href => "/industries/healthcare-and-life-sciences/"} Healthcare &amp; Life Sciences %li %a{:href => "/industries/government-and-enterprise/"} Government &amp; Enterprise %li %a{:href => "/industries/media/"} Media %li %a{:href => "/industries/education/"} Education

The Industries item appears once in the mobile list and once in the desktop list. Indentation matches sibling %li items (count the leading spaces against the Solutions item directly above). The desktop item carries .full-nav-only like the other secondary top-level items.

Task 5: SaaS and ISVs page + FAQ partial

Files: - Create: industries/saas-and-isvs/index.html.haml - Create: _partials/faq_saas.html.haml

  1. Q: Do you work with multi-tenant SaaS architectures? A: Yes. We design and run multi-tenant AWS platforms, with isolation, scaling and per-tenant cost visibility built in.
  2. Q: Can you support our product through rapid growth? A: Yes. We build platforms that absorb traffic spikes and new tenants through autoscaling and Infrastructure as Code, without forcing a re-architecture.
  3. Q: How do you help with enterprise security reviews? A: We operate ISO 27001 certified controls and provide SOC 2 audit support, so your sales team has the evidence enterprise buyers ask for.
  4. Q: Will our engineers lose control of the platform? A: No. Everything runs in your own AWS accounts with full handover. You own everything we produce and your team keeps full visibility.
  5. Q: How quickly can you get started? A: Typically within 1 to 2 weeks. The exact timeline depends on the complexity of your environment.
  6. Q: Do you offer fractional technical leadership? A: Yes. Our SaaS CTO engagement provides strategy, architecture guidance and team uplift for products scaling on AWS.

Hrefs /devops/, /platform-engineering/, /cloudmanagement/, /consulting/services/saas-cto/, /aws-saas-solutions/, /industries/financial-services/, /industries/media/ all exist or are created in this plan. Six FAQ cards match the six JSON-LD entries. ASCII only.

Task 6: Financial Services page + FAQ partial

Files: - Create: industries/financial-services/index.html.haml - Create: _partials/faq_financial_services.html.haml

  1. Q: Do you align with APRA CPS 234? A: Yes. We operate AWS controls aligned to CPS 234 and support your own attestation with evidence and reporting.
  2. Q: Are you SOC 2 certified? A: We are not a SOC 2 auditor. We provide SOC 2 audit support and operate controls aligned to SOC 2, and we are ISO 27001 certified.
  3. Q: Where does our data live? A: In the AWS regions and accounts you choose. Data residency, segregation of duties and least privilege access are enforced across the environment.
  4. Q: How do you handle change control? A: Every change runs through approval and review gates, is logged and is reversible, so governance does not slow delivery.
  5. Q: Can you help us pass a financial services security review? A: Yes. ISO 27001 certified processes, SOC 2 audit support and full evidence give you what reviewers and procurement teams ask for.
  6. Q: Do you have experience with payments and PCI? A: Yes. We helped Parakeet reach PCI compliance roughly three times faster while reducing cost, working entirely in their own AWS account.

Task 7: Healthcare and Life Sciences page + FAQ partial

Files: - Create: industries/healthcare-and-life-sciences/index.html.haml - Create: _partials/faq_healthcare.html.haml

  1. Q: How do you protect sensitive health data? A: Through encryption, least privilege access and continuous monitoring, backed by ISO 27001 certified controls, all in your own AWS account.
  2. Q: Where is our data stored? A: In the AWS regions you choose. Data residency, segregation and access controls are enforced to respect patient and participant privacy.
  3. Q: Are you ISO 27001 certified? A: Yes. base2Services is ISO 27001 certified, and we are APRA CPS 234 compliant.
  4. Q: Can you support our privacy and compliance obligations? A: Yes. We operate controls aligned to your obligations and provide SOC 2 audit support and the evidence assessors ask for.
  5. Q: How do you ensure availability for critical health services? A: Validated backups, tested recovery and 24/7 monitoring keep services available, with recovery times measured rather than assumed.
  6. Q: Can you migrate our existing health platform to AWS? A: Yes. We assess, plan and run the migration with minimal disruption and full handover to your team.

Task 8: Government and Enterprise page + FAQ partial

Files: - Create: industries/government-and-enterprise/index.html.haml - Create: _partials/faq_government_enterprise.html.haml

  1. Q: Do you work with government and public sector organisations? A: Yes. We support public sector and enterprise organisations including Emergency Management Victoria, Open Universities Australia and RSL Art Union.
  2. Q: How do you handle governance and change control? A: Through approval gates, full audit trails and reversible change. Every action is logged and reviewable.
  3. Q: What security certifications do you hold? A: AWS DevOps and SaaS Competencies, AWS Advanced Partner status, ISO 27001 certification and APRA CPS 234 compliance.
  4. Q: Can you manage large multi-account AWS estates? A: Yes. We provide and operate landing zones, account governance and continuous monitoring across complex estates.
  5. Q: Can you migrate our legacy systems to AWS? A: Yes. We assess, plan and run migrations of large environments with minimal disruption and full handover.
  6. Q: How do you ensure availability for essential services? A: Validated backups, tested recovery and 24/7 monitoring keep essential services available, with recovery times measured.

Task 9: Media page + FAQ partial

Files: - Create: industries/media/index.html.haml - Create: _partials/faq_media.html.haml

  1. Q: Can you handle large traffic spikes? A: Yes. We build platforms that scale on demand through autoscaling and Infrastructure as Code, and shed load gracefully under pressure.
  2. Q: Do you support live video streaming? A: Yes. We helped Sardius Media speed up live video streaming on AWS, and we run real-time and on demand workloads.
  3. Q: How do you keep latency low? A: Through AWS native delivery and caching tuned to your audience, with workloads placed in the regions closest to your viewers.
  4. Q: How do you control streaming costs? A: Continuous rightsizing, commitment buying and architecture reviews keep delivery spend in line with audience and revenue.
  5. Q: Do you provide 24/7 support during events? A: Yes. We monitor around the clock and join the calls during your biggest moments, across AU, EU and US coverage.
  6. Q: How quickly can you get started? A: Typically within 1 to 2 weeks, depending on the complexity of your environment.

Task 10: Education page + FAQ partial

Files: - Create: industries/education/index.html.haml - Create: _partials/faq_education.html.haml

  1. Q: Can you handle enrolment and exam traffic peaks? A: Yes. We run platforms that scale up for predictable surges through autoscaling, then scale back down to control cost.
  2. Q: How do you protect student data? A: Through encryption, access controls and ISO 27001 certified processes, all running in your own AWS account.
  3. Q: Do you work with EdTech products and universities? A: Yes. We helped Boddle scale an EdTech platform and have supported Open Universities Australia.
  4. Q: How do you keep platforms available during assessments? A: 24/7 monitoring, tested recovery and validated backups keep platforms available when learners depend on them.
  5. Q: Can you help reduce our AWS costs? A: Yes. Continuous rightsizing and architecture reviews make sure constrained budgets go as far as possible.
  6. Q: How quickly can you get started? A: Typically within 1 to 2 weeks, depending on the complexity of your environment.

Task 11: Final cross-check

Files: none (review only)

Confirm every internal href across the new pages resolves to a directory with an index.html.haml or to a slug created in this plan. Pay attention to: /security/ (not /compliance-and-risk/), /industries/<slug>/ matching Tasks 5 to 10 exactly, /aws-saas-solutions/.

Grep the new files for em-dash, en-dash and the string ", and " / ", or " (Oxford comma). Grep for "SOC 2 compliant" and "SOC 2 certified" (must not appear; only "SOC 2 audit support" or "controls aligned to SOC 2"). Confirm ASCII only.

Confirm each industry page renders its FAQ partial name correctly and that each FAQ partial has six visible cards matching six JSON-LD entries. Confirm the nav shows Solutions linking to /services/ and a single Industries dropdown in both mobile and desktop lists.

Report the file list created and modified. The user runs the Awestruct build and a Codex review pass, then manages commits.

Self-review notes