How Jekyll Solves Problems WordPress Doesn’t Need To

Most of the websites I build for clients run on WordPress or WooCommerce. It’s a platform I trust and recommend because it gives businesses the power to manage content easily, scale their online presence, and integrate with the tools they rely on every day.

So why did I choose Jekyll for my own brinkerwebdesign.com website?

Because every project deserves the tool that fits it best.

My site isn’t an eCommerce hub or a dynamic application. It’s a place to showcase my work (see portfolio), share insights, and help potential clients understand what I do through my Web Development Packages.

A static-site generator like Jekyll gives me:

  • Zero database overhead
  • Near-instant page loads
  • A minimal attack surface with no backend to exploit
  • No ongoing patching or plugin updates
  • Full control of HTML, SCSS, and layout structure

For a small business site that doesn’t require user accounts, complex forms, shopping carts, or editorial workflows, this level of speed and simplicity is hard to beat.

Clean, Predictable Code With Liquid Templates

One of the reasons I enjoy working with Jekyll is the Liquid templating system.

Liquid powers Shopify and many modern platforms, and it offers huge advantages for building structured, maintainable websites.

Using Liquid in Jekyll gives me:

  • Reusable components via includes and partials
  • Organized, predictable page structures
  • Readable logic that stays out of the way
  • Complete front-end control without a PHP/LAMP stack

It lets me build the site exactly how I want, down to the last class name.

A Development Workflow I Love: Gulp + Git + Deploy Hooks

My Jekyll site isn’t “just static files.” It’s part of a modern front-end pipeline powered by Gulp JS.

Automated tasks

  • SCSS compilation & minification
  • Autoprefixing for browser support
  • JavaScript concatenation
  • Image optimization (symlink in dev, copy in prod)
  • HTML minification for production builds

Deploy-aware builds

I use two Git branches: master for development and production for live deployment.

  • gulp push → pushes changes to master
  • gulp deploy → builds static output, writes .gitignore + .nojekyll, and pushes the production branch

Then I log into the server and pull the latest production branch. Clean. Predictable. Zero surprises.

Gulp.js logo

Why This Doesn’t Conflict With Recommending WordPress

Choosing Jekyll for my site doesn’t mean WordPress isn’t the right choice for clients. In fact, most businesses should absolutely be on WordPress, especially when they need:

  • Client-editable content
  • Built-in SEO tools and visibility controls
  • WooCommerce and eCommerce workflows
  • API integrations and plugin-powered features
  • CRM and lead capture integrations
  • Marketing automation
  • Multi-user editorial workflows

Static sites solve some problems beautifully. WordPress solves most client problems even better.

Knowing when to use each one is the real skill.

The Professional Choice Is Using the Right Tool for the Work

Nearly two decades of building websites has taught me this:

A good developer doesn’t force one platform into every project, they choose the right tool for the job.

For most clients, that tool is WordPress.
For my own portfolio and service site, Jekyll is perfect.

Because I work deeply in both ecosystems, I help clients make strategic decisions based on real-world use, not hype or trends.

If you’re unsure which direction your next site should take, I’m happy to walk through the options.

Contact Brinker Web Design

Ask About Static Site Support

WordPress + WooCommerce Still Have a Big Role Here

Even though this site runs on Jekyll, I’ll be using WordPress and WooCommerce in concert with my marketing section soon for client dashboards, gated tools, application workflows, and specialized lead-gen experiences.

Stay tuned.