Deploying

GitHub Pages

If you started from the template, your site is already on GitHub Pages (see Getting started). Every push to main publishes it again within a minute or two.

GitHub Pages builds the site with its own Jekyll and plugins. Alcor only uses plugins on GitHub’s list, so it needs no GitHub Actions.

Your own domain

1. In your repository, open Settings → Pages → Custom domain, enter your domain (www.example.com or example.com) and save.
2. At your domain provider, add the DNS record GitHub asks for:
   • For www.example.com, or any subdomain: a CNAME record pointing to your-username.github.io.
   • For example.com itself: A records pointing to GitHub’s addresses, listed in GitHub’s guide.
3. When the check passes, tick Enforce HTTPS.
4. Set url in _config.yml to the new address, and keep baseurl: "".

If your domain is on Cloudflare, set the record to DNS only (grey cloud) until GitHub has issued the HTTPS certificate.

Netlify or Cloudflare Pages

Connect your repository and use these settings:

Setting	Value
Build command	bundle exec jekyll build
Output folder	_site
Ruby version	3.3 (set RUBY_VERSION=3.3.4 if asked)

Both read the Gemfile, which pins the same versions GitHub Pages uses.

Any other web host

Build on your computer with bundle exec jekyll build and upload the contents of the _site folder.