← All posts
Notes · · Eleventor Design · 1 min read

Why we write our apps in Markdown first

How a tiny Markdown-powered blog keeps writing easy without a build step, and what we care about when we ship Android apps.

Why we write our apps in Markdown first

A blog that gets out of the way

We wanted to write posts the way we think - in plain text, with headings, lists, and links - without standing up a CMS or a JavaScript build step. So this blog is just Markdown files parsed on the server with PHP.

Each post is one .md file in the blog/ folder. The bit at the top between the --- lines is the frontmatter: title, description, date, and so on. Everything below it is the post.

What Markdown gives us

  • Headings like the one above
  • Bold and italic text
  • Links back to the site
  • Lists, naturally

Restraint is a design constraint. The fewer moving parts, the fewer things to break.

A little code, too

fun greet(name: String): String {
    return "Hello, $name"
}

That is the whole idea. Write Markdown, save the file, and the post is live - no compile, no deploy pipeline beyond what the site already does.

Want the long version of how we build Android apps? Get in touch.

Read the rest of the blog.

All posts