Where is my content stored?

GoBlogger is file-based: your posts, pages, images, and theme overrides are stored as files you can back up, edit, and version.

Where things live

• Content: content/posts/... and content/pages/... inside your configured BLOG_CONTENT_DIR.
• Bundled example content: site/content/ in the repository.
• Theme overrides (templates, static assets, locales): theme/....
• Generated runtime artifacts: search/tag index files (configured by BLOG_SEARCH_INDEX_FILE, BLOG_TAG_INDEX_FILE) and feed files.
• Runtime config and credentials: .env and the .admin-credentials file near your runtime working directory (or at the configured paths).

Filenames and image folders

• Pages and posts have a human title, but the slug is used for the filename.
• Images for a post/page are stored in a sibling folder named .assets (i.e., the filename with .assets appended).
• Renaming a slug also renames the underlying file and its .assets folder so image links stay correct.

Example filenames:

• content/posts/2026/my-first-post.md (images → my-first-post.md.assets/)
• content/pages/about.md (images → about.md.assets/)

Short example post

---
title: Hello, world
description: A tiny first post.
date: "2026-02-27 12:00"
draft: false
tags: ["intro"]
slug: hello-world
---

"Start writing, and the rest will follow." — adapted from Ernest Hemingway

This is a small test post to show where content files live and how a simple Markdown post looks.

What is critical

• Content files are the source of truth — back them up first.
• Theme overrides capture visual/behavior customizations.
• .env and admin credentials are needed for operation and admin access.
• Generated indexes and feeds can be rebuilt and are not strictly required in backups.

Backup recommendation

At minimum, back up:

• BLOG_CONTENT_DIR (your content/posts and content/pages)
• theme/ (your overrides)
• .env
• .admin-credentials

With those assets you can restore a working site quickly.