in root.html). Outputs custom og:image with assets_prefix normalisation and non-Google site verification. --> Jekyll Frontmatter CMS | IT-Journey in _layouts/root.html. What this file adds: - Custom og:image with preview_images.assets_prefix path normalisation for the theme-specific page.preview and page.header.og_image keys. When page.image is set, jekyll-seo-tag handles og:image and this file skips its own og:image output to avoid duplicate tags. - Non-Google site verification tags (Bing, Yandex, Naver, Baidu) Dependencies: - jekyll-seo-tag plugin (loaded in _layouts/root.html via Jekyll Frontmatter CMS | IT-Journey ) - site.preview_images config in _config.yml =================================================================== --> Jekyll Frontmatter CMS | IT-Journey Skip to main content
Settings
Search
Appearance
Theme Mode
About
Jekyll v3.10.0
Environment Production
Last Build
2026-04-11 02:52 UTC
Current Environment Production
Build Time Apr 11, 02:52
Jekyll v3.10.0
Build env (JEKYLL_ENV) production
Quick Links
Page Location
Page Info
Layout default
Collection docs
Path _docs/jekyll/jekyll-frontmatter-cms.md
URL /docs/docs/jekyll/cms/jekyll-frontmatter-cms/
Date 2022-06-11
Theme Skin
SVG Backgrounds
Layer Opacity
0.6
0.04
0.08

Jekyll Frontmatter CMS

By bamr87

Guide on using Jekyll and Frontmatter as a Content Management System for static site generation

Estimated reading time: 2 minutes

This is a comprehensive guide on how to use Jekyll and Frontmatter to build a powerful Content Management System (CMS).

What is Jekyll Frontmatter?

Jekyll frontmatter is YAML metadata that sits at the top of your markdown files, enclosed between triple dashes (---). It allows you to define variables and configuration options that Jekyll can use when building your site.

Setting Up Frontmatter as a CMS

Essential Frontmatter Fields

---
title: Your Post Title
description: A brief description of your content
author: Your Name
date: 2024-01-01T00:00:00.000Z
lastmod: 2024-01-01T00:00:00.000Z
categories:
  - category1
  - category2
tags:
  - tag1
  - tag2
draft: false
---

Advanced Frontmatter Configuration

For a more robust CMS-like experience, you can include additional fields:

  • excerpt - Short summary for previews
  • featured - Boolean for featured content
  • image - Hero image for the post
  • permalink - Custom URL structure
  • sidebar - Navigation configuration

Benefits of Using Frontmatter as a CMS

  1. Version Control - All content changes are tracked in Git
  2. No Database - Static files are easier to backup and migrate
  3. Performance - Static sites load faster than database-driven sites
  4. Security - No database means fewer attack vectors
  5. Portability - Markdown files can be used with any static site generator

Tools and Integrations

Visual Editors

  • Forestry - Web-based editor for Jekyll sites
  • NetlifyCMS - Open-source content management for static sites
  • Frontmatter Extension - VS Code extension for managing frontmatter

Automation

  • Git hooks for automatic builds
  • GitHub Actions for CI/CD
  • Automated frontmatter validation

Best Practices

  1. Consistent Schema - Use the same frontmatter fields across similar content types
  2. Validation - Implement checks to ensure required fields are present
  3. Templates - Create frontmatter templates for different content types
  4. Documentation - Document your frontmatter schema for team members

Example Workflow

  1. Create content using markdown with frontmatter
  2. Use VS Code with frontmatter extensions for easier editing
  3. Commit changes to Git repository
  4. Automated build process generates the static site
  5. Deploy to hosting platform (GitHub Pages, Netlify, etc.)

This approach provides the benefits of a traditional CMS while maintaining the simplicity and performance of static sites.