mykg-github-pages

# mykg GitHub Pages Publishes a purpose-built `pages/` folder from the `SenolIsci/mykg` `main` branch as a website, via a GitHub Actions workflow that builds it with Jekyll and pushes the built `_site/` output to a `gh-pages` branch, which is what GitHub Pages actually serves. ``` main branch gh-pages branch ├── src/ ← software ├── index.html ← built site ├── pages/ ← Pages source ├── blog/... │ ├── _config.yml └── ... (generated — never hand-edit) │ ├── _posts/ (blog articles) │ ├── index.md (landing page, adapted from README.md) │ └── diagrams/ └── .github/workflows/pages.yml pages.yml: on push to main (pages/** changes) → jekyll build pages/ → _site/ → peaceiris/actions-gh-pages pushes _site/ to gh-pages Settings > Pages: source = gh-pages branch ``` ## Why a dedicated `pages/` folder A dedicated `pages/` folder holds *only* content written for the public site, so there's never anything to accidentally publish. This skill's default and only source for initial content is `README.md` (see Step 1) — it never assumes any other folder in the repo is publishable. Any other repo artifact (a diagram, a logo, a screenshot, an existing doc) is fair game to feature on the site, but only when the user explicitly points at it — see "Sourcing artifacts from the repo" below. Don't scan the repo looking for content to publish; ask instead. ## Check state before doing anything ```bas...