Draft
Conversation
Create a new /resources/ content section for educational guides, comparisons, and evaluations. Migrate two high-performing blog posts (IaC tools, secrets management) and add a new AI infrastructure tools guide. Includes Hugo layouts with guides-matching sidebar styling, schema.org structured data, and archetype for future content.
This comment was marked as resolved.
This comment was marked as resolved.
- Remove duplicate FAQ: drop frontmatter faq from ai-infrastructure-tools since the article body already has a comprehensive FAQ section - Fix author schema: resolve slugs to display names via Site.Data.team.team lookup instead of outputting raw slugs like "asaf-ashirov" - Remove unattributed stats: replace unsourced 18x/90% claims with general language - Fix typography: use en-dash for 20-45% range, em-dash in Key trends - Remove unnecessary /blog/ai-infrastructure-tools/ alias (new article, no existing blog post at that URL) - Combine duplicate html CSS rules in single.html Note: ai-infrastructure-tools/meta.png is a placeholder (same image as IaC tools) and needs a unique image before merge.
Collaborator
|
Your site preview for commit 52ca5ed is ready! 🎉 http://www-testing-pulumi-docs-origin-pr-17842-52ca5ed9.s3-website.us-west-2.amazonaws.com. |
Collaborator
|
Your site preview for commit b6ba8ee is ready! 🎉 http://www-testing-pulumi-docs-origin-pr-17842-b6ba8ee0.s3-website.us-west-2.amazonaws.com. |
Restructure the flat /resources/<slug>/ layout into nested solution area directories with pillar-content category pages. This creates a hub-and-spoke architecture for SEO topical clustering and AEO optimization. Content structure changes: - Move articles into /resources/<solution-area>/<slug>/ directories - Create category pillar pages for Infrastructure Unification (~1,200 words) and Security & Compliance (~1,200 words) with FAQ sections - Defer AI-Ready Infrastructure category until first article is ready - Update secrets management title year from 2025 to 2026 - Standardize solution_areas slug: security-and-compliance -> security-compliance Template changes: - list.html dispatches between hub and category via .Parent.IsHome - New hub-page.html with solution area cards, featured articles, all articles - New category-page.html with breadcrumb, pillar content, frontmatter-queried article grid, FAQ rendering, related areas/capabilities, CTA - New category-card.html with article count badge - resource-card.html reads from data/resources/labels.yaml, supports HideParentArea context flag, solution area badges link to category pages - single.html sidebar uses category-aware relevance (same area first, limit 5) with "More in [Category]" link; breadcrumb includes category level Schema and SEO: - CollectionPage schema for category section pages - FAQPage schema extended to category pages with faq frontmatter - BreadcrumbList schema includes resources section and category level - llms.txt uses hierarchical category grouping Data: - New data/resources/labels.yaml centralizes display names (replaces inline $labels dicts in templates) - Archetype updated: security-compliance, ai-ready-infrastructure slugs
Hugo's `with .Parent` rebinds context, so `.Parent.IsHome` inside the block accesses the grandparent (which is nil for the top-level /resources/ section page). Replace all `with .Parent` + `.Parent.IsHome` patterns with `if and .Parent (not .Parent.IsHome)` which stays in the original context and nil-checks safely. Fixes build failure: "nil pointer evaluating page.Page.IsHome" on content/resources/_index.md.
Collaborator
|
Your site preview for commit 1c3fffb is ready! 🎉 http://www-testing-pulumi-docs-origin-pr-17842-1c3fffb6.s3-website.us-west-2.amazonaws.com. |
Visually differentiate solution area badges (purple, linked) from capability/topic badges (gray, unlinked) across resource cards, article hero, and category pages. Add topic page infrastructure so capability badges automatically link to topic pages when they exist via Site.GetPage. New files: - topic-page.html partial (cluster page: breadcrumb, article grid by capability tag, "Part of" solution area back-links, FAQ, CTA) - topic-card.html partial (hub card with article count) - content/resources/topics/_index.md section index Changes: - labels.yaml: add "topics" key for user-facing topic display names - list.html: dispatch topic subsections to topic-page partial - hub-page.html: "Browse by topic" section alongside solution areas - resource-card.html: div wrapper with linked badges, Site.GetPage for both solution areas and topic pages - single.html: capability badges link to topic pages when available - category-page.html: "Related topics" badges use gray styling and topic page linking No topic sub-pages created yet (thin-page rule: only when a capability reaches 2+ articles). Templates are ready to activate per-topic.
Collaborator
|
Your site preview for commit c7905bf is ready! 🎉 http://www-testing-pulumi-docs-origin-pr-17842-c7905bf0.s3-website.us-west-2.amazonaws.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
3 participants
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.
Summary
/resources/content section for SEO/AEO-optimized educational guides, comparisons, and tool evaluationsTest plan
/resources/list page renders card grid with all 3 articles/guides/styling)/blog/infrastructure-as-code-tools/,/blog/secrets-management-tools-guide/)make lint(passes clean)