build with
markgo
A blog engine in one Go binary
Posts are markdown files in a directory. markgo serve puts them on the web
with search and feeds, from one binary with its web assets embedded.
A post needs no type. No title and under a hundred words makes a thought. A link field makes a link. Anything else is an article.
Set an admin login and a compose form writes the same files, published at once. An edit made on disk shows after a restart.
why it exists
A static site generator has the files and no server. A hosted platform has the server and keeps the files.
markgo keeps the files on disk and runs the server.
what it taught
markgo shows that a blog can be markdown files in a directory and a compose form, in one binary, with no database and no build step.
markgo init --quick, then markgo serve, and a blog is on port
3000.
Source is public and kept current.