Publish with Markdown.
No CMS, database, or external deployment service to manage. Articles live in the repository and GitHub Pages builds the website.
1. Create an article
Add a file inside the _posts directory. Use a date-first filename such as 2026-10-20-a-better-way-to-validate-a-saas-idea.md.
2. Add front matter
---
layout: post
title: "A clear, specific article title"
description: "A useful summary of what the reader will learn."
date: 2026-10-20
categories: [startups]
tags: [validation, product]
author: IndieFounder Editorial Team
cover: /assets/images/covers/validate-a-saas-idea.svg
image: /assets/images/covers/validate-a-saas-idea.png
permalink: /startups/validate-a-saas-idea/
---cover is the image shown on article cards and at the top of the article; image is the 1200×630 PNG used for social previews. See the README for how to generate both.
3. Write for the reader
Answer the main question early. Explain concepts, show reasoning, include realistic examples, describe limitations, and link relevant primary sources. Avoid padding, generic introductions, repeated templates, invented facts, and keyword stuffing. Length should follow the subject's needs; word count is not a substitute for usefulness.
4. Review and publish
Check spelling, links, claims, title uniqueness, category, date, author, and mobile readability. Commit the Markdown file to main and check the GitHub Actions tab after the build. Fix build errors before considering the article published.
Editorial rule
Do not publish unreviewed AI output, near-duplicate articles, fabricated case studies, or pages written mainly to manipulate search rankings. Publish less often rather than publishing something that offers no real reader value.