sapho-website2-github-pages

Migrate Sapho Website 2.0 rendering to GitHub Pages with environment-driven Python workflows.

Updated Mar 31, 2026
One-click install
npx skills add https://github.com/quiznat/Hermes_Sapho --skill sapho-website2-github-pages
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sapho-website2-github-pages
Source: https://github.com/quiznat/Hermes_Sapho/tree/main/.hermes/skills/software-development/sapho-website2-github-pages
Command: npx skills add https://github.com/quiznat/Hermes_Sapho --skill sapho-website2-github-pages

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

Migrates Sapho Website 2.0 to GitHub Pages while preserving the current static site style and layout, keeping the same custom domain, and deferring RSS/feed surfaces until stabilization.

Core Features & Use Cases

  • Structural migration to GitHub Pages without a visual redesign.
  • Preserve the canonical domain and hosting surface while validating a safe rollout.
  • Deferred RSS/feeds to avoid launch-time dependencies during migration.

Quick Start

Render the site locally with SAPHO_SITE_MODE=github-pages and SAPHO_SITE_BASE_URL and SAPHO_SITE_CUSTOM_DOMAIN set to the target values, then verify the output under sapho-native/public/site.

Frequently Asked Questions about sapho-website2-github-pages

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

FAQPage Schema
How do I migrate a static website to GitHub Pages without changing the visual layout or domain?

Migrating a static website to GitHub Pages safely requires a Python-based render workflow that preserves the current custom domain and site style without triggering a visual redesign during the hosting transition.

What environment variables are required to render a static site for GitHub Pages?

Rendering a static site for GitHub Pages requires setting SAPHO_SITE_MODE, SAPHO_SITE_BASE_URL, and SAPHO_SITE_CUSTOM_DOMAIN environment variables to target the correct hosting surface and canonical domain.

Can I keep my custom domain active while migrating to GitHub Pages?

Yes, you can keep your custom domain active during a GitHub Pages migration by configuring the SAPHO_SITE_CUSTOM_DOMAIN environment variable to maintain the canonical hosting surface throughout the rollout.

Why defer RSS feed generation during a static site migration?

Deferring RSS feed generation during a static site migration avoids launch-time dependencies and feed surface errors, allowing you to stabilize the core hosting environment and visual layout first.

How do I verify a static site migration locally before publishing to GitHub Pages?

To verify a static site migration locally, render the site with the target environment variables and check the generated output under the public/site directory to ensure the structure matches the expected rollout.

Does a GitHub Pages migration require a full site redesign?

No, a GitHub Pages migration does not require a full site redesign; you can structurally migrate the rendering workflow while explicitly preserving the current static site style and layout.