build-resource-pages

Transform markdown resource content into production-ready website pages with metadata.

1.3k|43|Updated Feb 26, 2026

Search Tags:#markdown #frontmatter #json-ld #seo-metadata #static-generation #resource-centers

Ready to run

npx skills add https://github.com/onvoyage-ai/gtm-engineer-skills --skill build-resource-pages

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: build-resource-pages
Source: https://github.com/onvoyage-ai/gtm-engineer-skills/tree/main/build-resource-pages
Command: npx skills add https://github.com/onvoyage-ai/gtm-engineer-skills --skill build-resource-pages

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill automates the transformation of existing markdown content into production-ready resource pages, ensuring consistent design and seamless deployment across client sites.

Core Features & Use Cases

Discovers the frontend stack and design system to render content as production-ready pages.
Builds a Resource Center hub, section listing pages, and article pages with standardized metadata and cross-linking.
Enforces accessibility, responsive layouts, and structured data (JSON-LD, Open Graph) for SEO.

Quick Start

Copy the build-resource-pages folder into your skills directory and run the static generation workflow to generate production-ready resource pages.

Frequently Asked Questions about build-resource-pages

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I convert markdown content into production-ready website pages?▼

To convert markdown content into production-ready website pages, you need to parse YAML frontmatter and render static HTML with SEO metadata. This process generates hub, listing, and article pages while injecting JSON-LD structured data and Open Graph tags for optimal search visibility.

What is JSON-LD structured data and why is it needed for static resource pages?▼

JSON-LD structured data is a standardized metadata format injected into static resource pages to help search engines understand content context. It is needed for static generation workflows to automatically provide search engines with article schemas, canonical URLs, and cross-linking relationships without manual HTML intervention.

How do I generate resource center hub and listing pages from existing markdown?▼

Generating resource center hub and listing pages from markdown requires an automated static generation workflow that parses content sections like Learn, Guides, and Blog. The workflow discovers your frontend stack to render responsive layouts and automatically creates standardized cross-links between the hub and article pages.

Does this markdown to HTML generation work with any frontend stack?▼

Markdown to HTML static generation can work with different client frontend stacks by automatically discovering the existing design system during the build process. It adapts the rendering to match your production environment, ensuring responsive layouts and consistent design without forcing a specific framework dependency.

What is the best way to automate SEO metadata injection for static markdown articles?▼

The best way to automate SEO metadata injection for static markdown articles is using a build workflow that parses YAML frontmatter during static generation. This approach automatically extracts metadata to generate canonical URLs, Open Graph tags, and JSON-LD structured data, ensuring consistent SEO compliance across all article pages.

Why are my static markdown pages missing Open Graph metadata after generation?▼

Static markdown pages missing Open Graph metadata usually indicate the generation workflow did not parse the YAML frontmatter correctly or skipped metadata injection. Ensure your static build process explicitly enforces Open Graph tag generation alongside canonical URLs and JSON-LD structured data during the HTML rendering phase.