Where Is My Content?
Pure Blog is a flat file system, so there's no database to create or maintain. So, where does your content actually live when you create it?
The first time you create either a post or a page, a new folder is created within your Pure Blog installed, called /content. This folder then has 2 folders within it, /content/posts and /content/pages.
You guessed it, posts are stored in /content/posts and pages are stored in /content/pages. All content is stored in plaintext markdown with front matter, very similar to how Static Site Generators store content.
Both pages and posts follow a simple naming convention. Pages are simply named [page-name].md and posts follow a naming convention of YYYY-MM-DD-[post-name].md.
Here's what an example post would look like if you opened it in your text editor instead of Pure Blog:
---
title: This is a Test Post
slug: this-is-a-test-post
date: 2026-01-29 14:27
status: draft
tags: [test, writing]
description: This is just a test post, nothing special.
---
I wrote these notes so I wouldn’t need to **remember** them later. The page is a quiet place to store the stuff that [doesn’t need](https://example.com) to live in your head.
I found a few small frictions hiding in the usual routine. They were tiny, but together they were heavy enough to slow everything down. Naming them helped more than I expected.The front matter is the block of text at the top of the file that's wrapped in three dashes. This is the meta data for the post, most of which is from the sidebar in the Pure Blog editor. The rest of the content is pulled directly from the main Pure Blog editor.
Other files in the content folder
If you look inside the /content folder, you will likely see a couple of other files in there. These are search-index.json and tag-index.json.
These are both automatically generated by Pure Blog and are used to improve efficiency when filtering posts, such as generating search results, looking at posts with a particular tag.
These files are automatically updated whenever you save a post/page.
Here's a video that goes over what we covered in this post: