nextjs, markdown, self-hosted
Welcome to the raw blog setup
This first sample post shows the file-based workflow, shared layout, image handling, and the shape a future admin tool can write into.
This post is the first example entry for the blog. It lives as a plain Markdown file under content/posts, which keeps the authoring flow simple today and leaves plenty of room for a future authenticated CMS to create or update the same files later.
How this blog is organized
- Each article is a single Markdown file with frontmatter.
- Images live in
public/images/posts/<slug>/. - The blog homepage reads all posts from disk and sorts them by date.
- Each post page uses the same layout, metadata, and SEO structure.
Why this approach fits the future plan
Because the content model is file-based, you can start with Git-backed authoring now and add an admin UI later that writes the same Markdown and image files. When you introduce authentication, Docker, Traefik, and PostgreSQL, the blog renderer can stay almost unchanged while the admin layer grows around it.
Next natural steps
The next features to add are straightforward:
- draft mode and unpublished posts
- an authenticated admin area for creating posts
- image uploads that automatically place assets in the matching slug folder
- optional PostgreSQL storage for editorial metadata while keeping Markdown as the publishing source