bundle install no longer succeeds
A Gemfile.lock pinned to versions that are no longer on rubygems, or a native gem that does not build on the current Ruby. The site cannot be served or deployed locally.
Dependencies updated and lockfile valid
Running on Jekyll?
A Jekyll site is often the oldest thing in a company, which also means it is the one with a Gemfile no laptop can bundle and a plugin list GitHub Pages no longer whitelists. We pick these up, port them onto a Ruby you can still install, and either keep them on GitHub Pages where that still makes sense or move them onto Netlify or Cloudflare Pages where the restrictions no longer apply.
What it is
Jekyll is a static site generator written in Ruby, created by Tom Preston-Werner in 2008 and still the engine behind GitHub Pages. Content is written in Markdown with YAML front matter, layouts and includes use the Liquid template language, and the output is a folder of static HTML suitable for hosting almost anywhere.
The GitHub Pages integration made Jekyll the default choice for developer blogs and documentation sites for many years. GitHub Pages runs a pinned Jekyll version with a short whitelist of plugins, which is why many sites migrated to running their own Jekyll on Netlify, Cloudflare Pages or a CI build. Hugo, Eleventy and newer SSGs have taken a lot of new projects, but a large installed base of Jekyll sites is still quietly deployed.
The honest version
No technology is all upside. This is where Jekyll earns its place and where it tends to cause trouble.
Sound familiar?
The Jekyll problems that bring people to us, and what you have once each one is fixed.
A Gemfile.lock pinned to versions that are no longer on rubygems, or a native gem that does not build on the current Ruby. The site cannot be served or deployed locally.
Dependencies updated and lockfile valid
A custom Liquid tag provided by a plugin that is no longer loaded, or a Jekyll-Compose shortcut that stopped being supported. The build halts on the first file that uses it.
Templates valid on the current Jekyll
A plugin not on the whitelist, a configuration key the Pages gem does not recognize, or a theme being set directly instead of through remote_theme. The repository builds locally but Pages does not deploy it.
Pages build succeeds, or move handled
Ruby 3 removed implicit conversions and tightened keyword arguments, and Jekyll 3 code paths trip on both. A machine on current macOS cannot run the site at all.
Running on a supported Ruby and Jekyll
A theme upgrade removed a layout the posts still reference, or an old post front matter set a layout that was never defined in this site. Pages render but without the surrounding chrome.
Layouts resolving for every page
Older sites used kramdown, newer ones use kramdown-parser-gfm for GitHub-flavored Markdown, and a mismatch between the Gemfile and the config produces a load error at build time.
Markdown parsing consistent and tested
A collection permalink rule that collides with the posts default, or two posts with the same slug in different folders. Jekyll overwrites one with the other silently.
Permalinks unique and documented
A large archive with no incremental build enabled, SCSS compilation that re-runs every time, and plugins that walk every post on every file change.
Build times back to seconds
What we do
Call us for one failing build, or hand us the whole site.
How it works
Tell us what's going wrong. We look at it, then tell you plainly what's wrong and what it will cost.
We fix the cause, not the symptom. If something is down, getting it back up comes first.
Backups, monitoring, updates and access, so the same problem can't quietly come back.
You get a plain-language write-up. Or we stay on for hosting, upkeep and new work.
Often found together
We work on the whole stack, so the problem can be wherever it actually is.
Usually a Gemfile.lock full of gem versions that no longer compile on a modern Ruby, combined with a Jekyll 3 runtime that does not play well with Ruby 3. The honest fix is to port the site onto a supported Jekyll and gem set rather than pinning the laptop to a Ruby from 2017; we do that port in a branch and keep the existing content untouched.
For small blogs and project sites where the plugin whitelist is not a constraint, GitHub Pages is still the right answer. Once you want a plugin outside the whitelist, SEO features Pages does not support, or a custom build step, you move the build into CI and deploy to Netlify, Cloudflare Pages or an S3 bucket. The Pages URL can be redirected so links keep working.
The common causes are a plugin that is not whitelisted, a theme set in a way the Pages gem does not recognize, a Gemfile that disagrees with the Pages Ruby version, and a recently added Liquid tag that Pages treats as unsafe. The GitHub Pages build log is the source of truth, and every failure has a specific line we can act on.
Yes, and it is a frequent request. Jekyll's Markdown is largely portable, front matter translates with a small script, and the real work is in rebuilding the layouts in Go templates and preserving the existing permalink structure so inbound links still resolve. We leave the Jekyll repo in place until the new build is live and verified.
The content itself is almost always fine. The Gemfile, the Ruby version, the theme and a handful of plugins are where the work is. We rebuild the dependency graph against a current Jekyll, replace or rewrite any plugin that has stopped being maintained, and move the build into CI so the setup is reproducible rather than tied to one engineer's laptop.
We give estimates for free. Send us the repository or the Gemfile and the current error, and we respond with a price before any work is done.
Free estimate
Tell us what you're running and what's going wrong. A person reads it and comes back with an estimate.
Your message is with a real person, and we'll get back to you soon.
Rather talk now? Call us: