NOISSUE - feat(seo): implement pillar pages, FAQs, and schema markup across all solution and industry pages - #70
Merged
Merged
Conversation
… solution and industry pages Signed-off-by: ianmuchyri <ianmuchiri8@gmail.com>
Deploying with
|
| Status | Name | Latest Commit | Preview URL | Updated (UTC) |
|---|---|---|---|---|
| ✅ Deployment successful! View logs |
uvc-website | 7d63aea | Commit Preview URL Branch Preview URL |
Jun 09 2026, 04:32 PM |
Signed-off-by: ianmuchyri <ianmuchiri8@gmail.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What type of PR is this?
This is a feature because it implements a comprehensive SEO content and schema architecture across all solution, industry, and product pages — extending the existing
LensPagecomponent with optional content sections and adding structured data markup site-wide.What does this do?
Infrastructure
lensPageSchemainsrc/content/config.tswith optional Zod-validated fields:explainerEyebrow/H2/Body/Chips,detailsEyebrow/H2/Sub/Items,stepsEyebrow/H2/Sub/Items,faqsLensPage.astroto conditionally render explainer, details grid, steps (usingprin__gridlayout), and FAQ sections — all backwards-compatible (new fields are optional)solutions/[slug].astroandindustries/[slug].astroto pass all new propsSolution pages — new
/solutions/confidential-computing— full pillar: definition, CC vs encryption comparison, 5-step how-it-works, 3-item TEE hardware breakdown (AMD SEV-SNP, Intel TDX, NVIDIA H100), 8-question FAQ/solutions/secure-ai-deployment— full pillar: deployment architectures, on-prem vs cloud comparison, 5-step how-to, 8-question FAQ/solutions/confidential-computing/use-cases— cluster page with 8 TEE use cases, FAQPage + BreadcrumbList schemaSolution pages — expanded
sovereign-ai— definition block, expanded comparison, 6-item details grid, 5-step deployment guide, 8-question FAQai-governance— 6 regulatory frameworks (GDPR, EU AI Act, DORA, NIS2, HIPAA, CMMC), 5 technical controls, 7-question FAQprivate-ai,enterprise-ai,secure-collaboration,agentic-ai— explainer sections and 6–7 question FAQs added to eachIndustry pages — expanded
Product pages
cube-ai.astro,cocos-ai.astro, andprism-ai.astrolinking to relevant pillar pagesHeader
LensPageon all pages with FAQsDeliverables
SEO/SEO_IMPLEMENTATION_REPORT.md— full audit of implementation status, keyword coverage, internal linking, and remaining gapsSEO/BLOG_CONTENT_BACKLOG.md— 15 prioritised blog article briefs for remaining keyword clustersWhich issue(s) does this PR fix/relate to?
No issue — this implements the SEO action plan documented in
SEO/seo-plan-draft.md.Have you included tests for your changes?
No automated tests — this is content and component changes. Verified with
astro check(0 errors, 0 warnings) and manual visual review in the browser.Did you document any new/modified features?
Yes.
SEO/SEO_IMPLEMENTATION_REPORT.mddocuments all changes, schema markup status, keyword coverage, internal linking, and outstanding gaps.SEO/BLOG_CONTENT_BACKLOG.mdcovers remaining content work.Notes
All new
lensPageSchemafields are optional — no existing solution or industry YAML requires changes to remain valid. TheLensPagecomponent is fully backwards-compatible.