Moving from Jekyll to OrgMode, an experience report
summary
Migration replaces Jekyll with Org Mode to get literate programming and single-file publishing while keeping site generation inside Emacs. Dynamic lists and tag-based pages are produced by Babel to generate HTML and a Ruby script reading Org metadata that replicates Liquid-style indexes. Shared navigation uses #+INCLUDE for shared navigation, preview runs via a local node server and deploys with rsync. Result is a simpler, more robust Emacs-centric workflow with per-file publishing and repo-contained site specs.
AI-written summary · about
chapters (8)
- 0:00Introduction and background
- 3:58Why switch to Org Mode
- 5:27Org Mode as static site generator
- 6:54Challenges and solutions
- 10:53Live demo and workflow
- 12:18Advantages of the new setup
- 14:26Resources and next steps
- 15:11Q&A session
related talks
46mThe Underrated (But Amazing) Emacs org-mode
47mOrg-Mode for Science, Reproducible Research, and Organization
32mSwitching from Sphinx to Markdown
23mHow Rmarkdown changed my life
42mEngineering Documentation
35mSwitching from Sphinx to Markdown
32mThe Evolution and Future of Content Publishing
40mFrom resistance to adoption: navigating the challenges of docs-like-code