opensourcerisk.org — GitHub Pages

Static site migration of opensourcerisk.org from WordPress to GitHub Pages.

How it works

• The site is a static HTML export generated via the Simply Static WordPress plugin.
• On every push to main, GitHub Actions deploys the site to GitHub Pages (see .github/workflows/deploy.yml).
• The custom domain www.opensourcerisk.org is configured via the CNAME file.

DNS cutover (when ready to go live)

Point www.opensourcerisk.org to GitHub Pages by updating your DNS records:

Type	Name	Value
A	@	185.199.108.153
A	@	185.199.109.153
A	@	185.199.110.153
A	@	185.199.111.153
CNAME	www	opensourcerisk.github.io

Once DNS has propagated and the site is confirmed live, decommission the old WordPress server.

Testing locally

The site is plain static HTML — just serve the repo root with any local HTTP server. Do not open index.html directly in a browser (file:// breaks root-relative links like /content/...).

Option 1 — Node.js npx serve (recommended):

npx serve .

✅ Automatically serves 404.html for broken links, matching GitHub Pages behaviour exactly.

Option 2 — Python (no install needed):

python3 -m http.server 8000

⚠️ Does not serve 404.html for missing paths — Python shows its own built-in error. Use npx serve to test 404 handling locally.

Option 3 — Ruby (if you have it):

ruby -run -e httpd . -p 8000

Then open http://localhost:3000 (npx serve) or http://localhost:8000 (Python/Ruby) in your browser.

---

TODO

⚠️ Blocker before making the repo public or doing DNS cutover: Two commercial Envato plugins have assets committed to this repo (revslider and js_composer). Their licenses permit use on your own site but prohibit redistribution. A public GitHub repo constitutes redistribution. Resolve both issues below before going live publicly.

✅ Resolved: Both commercial plugins have been removed and replaced with open-source equivalents (see commit history for details).

---

Push to GitHub

⚠️ Requires an org admin to create the repo first — you cannot create repos under OpenSourceRisk without org permissions.

Step 1 — Ask an OpenSourceRisk org admin to:

• Create a new public repository named opensourcerisk.org (or website) — leave it empty (no README, .gitignore, or license)
• In the repo's Settings → Pages, set Source to "GitHub Actions"
• Grant you Write or Admin access

Step 2 — Once the empty repo exists, push:

git remote add origin https://github.com/OpenSourceRisk/<repo-name>.git
git push -u origin main

GitHub Actions will deploy the site automatically on the first push.

DNS cutover and old server shutdown

• Update DNS A records (see table above) to point www.opensourcerisk.org to GitHub Pages
• Verify the site is live, then decommission the old WordPress server

✅ Replace Revolution Slider (revslider) — done

Replaced with Swiper.js (MIT). wp-content/plugins/revslider/ deleted.

✅ Replace WPBakery Page Builder (js_composer) — done

Replaced with wp-content/js_composer_shim.css (1KB). wp-content/plugins/js_composer/ deleted.

---

Migrate large videos to external hosting

• wp-content/uploads/2020/09/ORE_XML_Introduction_August2020.mp4 is 59MB (GitHub recommends files under 50MB)
• Upload to YouTube or Vimeo and replace the <video> / <source> tag in the relevant HTML pages with an embed

Migrate forum (bbpress) to a hosted alternative

• Forum reply forms do not work on static hosting — the archived topics are readable but users cannot post
• Options:
  • GitHub Discussions — free, integrates with the repo
  • Discourse — self-hosted or hosted forum
  • Leave as read-only archive and add a notice pointing to the new forum

Migrate contact/feedback form

• The Contact Form 7 form on /feedback/ did not render in the static export (shows as a raw shortcode)
• Replace with a static-compatible form service:
  • Formspree — easy drop-in replacement
  • Netlify Forms — if migrating to Netlify
  • EmailJS — client-side email sending