Markdown Content

Built-in blog and documentation system powered by markdown

Markdown Content

Built-in blog and documentation system. No CMS, no admin panel, no database queries, no API requests. Just markdown files in your repo.

Why Not WordPress/Contentful/Strapi?

Most SaaS apps don’t need a CMS. You need:

  • A blog for SEO (5-10 posts, updated quarterly)
  • Product docs (update with each release)

You don’t need:

  • ❌ Admin panel with WYSIWYG editor
  • ❌ User roles and permissions
  • ❌ Media library with image cropping
  • ❌ Draft/publish workflows
  • ❌ API requests on every page load
  • ❌ Another service to pay for and maintain

goilerplate ships with markdown-based content. Version controlled, Git-based, editor-agnostic. Write in VS Code, push to deploy. That’s it.

Blog

Markdown-based blog with posts, tags, and automatic routing.

Location: /content/blog/*.md

Routes:

  • /blog - All posts (newest first)
  • /blog/{slug} - Individual post
  • /blog/tag/{tag} - Filter by tag

Frontmatter:

---
title: "Your Post Title"
description: "SEO description"
date: 2024-01-15
tags: ["saas", "golang", "startup"]
---

Your markdown content here...

Posts sorted by date. Tags extracted automatically for filtering.

Documentation

Hierarchical docs with folders, sections, and automatic navigation tree.

Location: /content/docs/**/*.md

Routes:

  • /docs - Documentation homepage
  • /docs/{slug} - Root-level page (e.g., /docs/installation)
  • /docs/{folder}/{slug} - Nested page (e.g., /docs/features/authentication)

Folder Structure

content/docs/
├── introduction.md           # /docs/introduction
├── installation.md           # /docs/installation
├── features/                 # Section folder
│   ├── _index.md            # Folder metadata (title, description, order)
│   ├── authentication.md     # /docs/features/authentication
│   └── subscriptions.md      # /docs/features/subscriptions
└── guides/
    ├── _index.md
    └── deployment.md         # /docs/guides/deployment

Folder Metadata: _index.md

Use _index.md to define folder properties (title, description, order):

---
title: "Features"
description: "Core product features"
order: 3
---

Optional markdown content shown when folder is clicked.

Without _index.md: Folder title auto-generated from folder name (features → “Features”).

Frontmatter

---
title: "Page Title"
description: "SEO description"
order: 1  # Lower numbers appear first in navigation
---

Sorting:

  1. By order (ascending)
  2. By title (alphabetical) if order is equal

Features

  • SEO: Every page gets meta tags, OpenGraph, Twitter cards
  • Sitemap: All posts/docs auto-included in /sitemap.xml
  • Syntax highlighting: Code blocks with language support
  • Navigation tree: Automatic sidebar generation from folder structure
  • Fast: Parsed on-demand, no build step
  • Search-friendly: Clean URLs, semantic HTML

Why Markdown?

  • ✅ Version control with Git (track changes, revert, blame)
  • ✅ Write in any editor (VS Code, Vim, Sublime, Obsidian)
  • ✅ No database needed (one less thing to break)
  • ✅ Easy to migrate (just markdown files)
  • ✅ Simple deployment (files in repo, deploy with code)
  • ✅ No vendor lock-in (markdown is universal)

For 99% of SaaS apps, this is all you need.

← Storage & File Uploads