A real lesson player
A course is a folder of lesson files. The theme renders the curriculum, the per-lesson player with its rail, and prev/next navigation.
Open source · MIT · Jekyll
A Jekyll theme for Salesforce developers.
Courses with a lesson player. A resume that prints from YAML. A certification wall, repo-style project cards, and a design system that re-brands from one hex. No build step beyond Jekyll.
Click Use this template above, name your repository, then set Settings → Pages → Source to GitHub Actions. Live in about a minute — full walkthrough.
git clone the repository, then bundle install && bundle exec jekyll serve. Everything else is three files of config.
Grab the archive from GitHub, unzip, bundle install, serve. Same theme, no git history.
Why this one
Built for the job, not adapted to it
Every feature below links to the live page proving it — this demo site is the spec.
A resume that prints
Generated from two YAML files — experience, education with GPA, skills with meters, and a certification wall coloured by track. Ctrl-P is the export.
Repo cards & galleries
GitHub-style cards with live-preview and source buttons, and a keyboard-navigable screenshot carousel on the case study.
Chapters that seek
YouTube, Vimeo or a hosted file. Video posts get a timestamp rail — click a chapter and the player jumps there.
Every article shape
Sidebar left, right or none; split headers; series with stepper navigation; a numbered blog index with thumbnails. All front matter.
One hex re-brands it
Two-tier tokens: change theme_style.accent and buttons, badges, shields, code accents and both colour schemes move together.
Content model
Eight collections, zero extra layouts
Each declares its schema.org type, hero, card style and sidebar in config — adding a ninth is three files, none of them a layout.
See it working
The demo site, in three samples
Fictional persona, real pages — everything you see is what a fresh install ships.
The field audit: deleting 178 fields without an incident
Part two — the staged deletion: describe, hide, freeze, delete, and the one rollback we needed at step three.
The field audit: finding the 200 fields nobody uses
Part one of cleaning up a nine-year-old org — how to prove a field is dead before you are allowed to delete it.
The anatomy of a deployment that goes well
A demonstration of the split header — the title and the image share the fold — wrapped around a real checklist.
MIT licensed
Start your site tonight.
Template it, follow the fifteen-minute setup, push. The docs cover everything from the first serve to the custom domain — and the contribution guide is open if you make it better.
Free forever · credit appreciated, not required