How can you organize blog drafts effectively in Jekyll

By -

Managing drafts in Jekyll using the _drafts folder is one of the most overlooked yet powerful workflows for bloggers who publish on GitHub Pages. This guide will help you understand why the drafts folder matters, how to use it effectively, and how it can transform the way you build and refine your content strategy.

Practical Guide to Jekyll Drafts Workflow

Why use drafts in Jekyll

Many beginners wonder why they should bother with drafts when they could just write posts directly in the _posts directory. The main reason is clarity and flexibility. Drafts give you a sandbox where unfinished ideas can live without being visible to your readers or indexed by search engines. This separation of published and unpublished content ensures that you maintain control over your editorial calendar and prevent half-finished thoughts from leaking onto your live site.

Think of drafts as your notebook inside Jekyll. You can brainstorm topics, experiment with outlines, and refine language over time. Unlike posts, drafts do not require a date in the filename, which makes them easier to shuffle, rename, or combine into larger articles later. This freedom is crucial when you are working on multiple articles simultaneously.

Creating and storing drafts

To start using drafts, create a folder named _drafts in the root of your Jekyll project. Inside this folder, add markdown or HTML files just like you would for posts. The difference is that drafts do not need a date prefix in their filename. For example:

_drafts/
  jekyll-drafts-guide.md
  seo-optimization-ideas.md
  workflow-improvements.md

Each draft should still have a YAML front matter section at the top. This allows you to predefine metadata such as title, tags, and categories. Later, when you are ready to publish, you can simply move the draft into the _posts directory and add a proper date to the filename.

Previewing drafts locally

By default, drafts are not rendered when you run jekyll serve. To preview them, you must add the --drafts flag:

bundle exec jekyll serve --drafts

This command tells Jekyll to include all files in the _drafts folder when building the site locally. The generated pages will use the current system date as a placeholder for the publish date. This makes it easy to see how the draft will look on your site without committing to an actual publishing schedule.

Previewing drafts also helps you test internal links, check formatting, and ensure images or code snippets display correctly before making them live. For content-heavy blogs, this reduces mistakes and builds confidence in your writing workflow.

Transitioning from drafts to posts

When your draft is ready to become a published article, the transition is simple. Move the file from _drafts into _posts and add a date prefix to the filename. For example:

_drafts/jekyll-drafts-guide.md

would become:

_posts/2025-09-25-jekyll-drafts-guide.md

This workflow allows you to spend as much or as little time as needed polishing your content before publishing. You can also schedule posts by assigning a future date, ensuring that articles go live automatically when the date arrives.

Workflow tips for bloggers

Here are some strategies to make the most of your drafts folder:

  • Batch your writing sessions: Spend a day creating multiple drafts and revisit them later to refine.
  • Tag your drafts: Use categories and tags in the front matter to organize by theme.
  • Outline first: Start with a structure of headings and bullet points before fleshing out paragraphs.
  • Use drafts for research: Collect links, notes, or references inside a draft before writing the final version.

These tips help bloggers stay organized, especially when balancing personal writing with professional commitments. A disciplined draft workflow reduces the stress of publishing deadlines and keeps your ideas flowing.

Common mistakes to avoid

Even though the drafts folder is simple, many beginners make mistakes that undermine their productivity. Some of these include:

  • Forgetting to run jekyll serve --drafts, which leads to confusion about missing content.
  • Keeping drafts forever without ever finishing them, turning the folder into a digital graveyard.
  • Publishing drafts without proper editing, leading to low-quality articles on your live site.
  • Failing to update metadata in the front matter before moving drafts to posts.

Avoiding these pitfalls ensures that your drafts folder remains a tool for progress rather than a place where ideas get stuck indefinitely.

Drafts and collaboration

If you are working in a team environment, the drafts folder becomes even more valuable. You can use version control in GitHub to manage draft edits, track changes, and discuss improvements before moving to publication. Team members can leave comments on pull requests, refine sections, or suggest improvements. This collaborative workflow keeps the editorial process transparent and efficient.

For solo bloggers, collaboration might mean sharing your repository with a mentor or friend for feedback. Since drafts are not visible on the public site, you can safely experiment and invite private review without worrying about exposing incomplete work to your audience.

Frequently asked questions

Do drafts get deployed to GitHub Pages?

No, drafts are not included when you push your Jekyll site to GitHub Pages. They only render locally when you explicitly run the --drafts flag. This ensures that unfinished content never goes live accidentally.

Can I organize drafts into subfolders?

Yes, you can use subfolders inside _drafts to organize by topic or project. However, remember that once you move them into _posts, you must rename the files according to Jekyll’s post format with dates.

What if I want to archive old drafts?

You can create a separate folder like _archive or simply push abandoned drafts to a different branch in GitHub. This keeps your main _drafts folder clean and focused.

Final thoughts and next steps

Using the _drafts folder in Jekyll is more than just a convenience. It is a workflow strategy that helps you separate ideas from published content, maintain quality standards, and reduce the pressure of immediate publishing. By taking advantage of this feature, you can build a healthier writing habit and deliver polished articles consistently.

If you have not yet tried working with drafts, create your first one today. Experiment with outlines, play with formatting, and preview the results locally. The more you use drafts, the more you will appreciate how they streamline your blogging process on GitHub Pages.

Call to action: Start organizing your next blog idea in the _drafts folder and see how much smoother your workflow becomes.