GitHub Pages variant blog

What changed

A standalone, GitHub Pages-compatible Jekyll blog was added at the repository root alongside the existing SSSF material. It models each Markdown post as a variant of a logical article: shared article_id and article_title metadata groups related posts, while language, format, and variant_rank describe and order the variants. The site has no CMS, database, accounts, comments, scheduled publishing, custom domain, or custom application server.

The sample Ship Small article contains four linked variants: English short, English long, Chinese short, and Chinese long. The home page groups these as one logical article and lists all four links; every post page renders navigation to its related variants.

Files carrying the change

Use and verification

For deployment, rename or create the GitHub repository as <account>.github.io, replace the url placeholder in _config.yml, push the default branch, and configure GitHub Pages to deploy that branch from the repository root. This produces https://<account>.github.io/ rather than a project-site subpath.

For local checking, install Ruby/Bundler and run:

bundle install
bundle exec jekyll serve
bundle exec jekyll build

Preview the displayed local URL and inspect _site/. A new variant belongs in a date-prefixed file under _posts/ with a shared article_id/article_title for an existing article, a unique stable variant_rank, language, format, and an explicit unique permalink. A new article_id starts a new logical article. The documented Git loop is branch, author metadata/content, build and preview, commit, push, merge into the deployment branch, push, then check the root Pages URL and deployment status.

The diff adds the build and preview instructions but does not record an executed build result; run bundle exec jekyll build to verify the current environment.