You would like to write a blog or whatever, which is a bunch of notebooks on your hard disk which gets rendered to a normal web page on a server somewhere. You would like to not have to spend energy on maintaining some bit of fancy software.
Companion piece to academic writing workflow, wherein I will mention plain text blogging choices, but I do not worry so much about certain constraints which are important mostly to academics, i.e. e.g. the need to support mathematical equations, graphs, citations…
TODO: AFAICT there is not much to choose between the various site generators I mention below as far as the base functions go (taking some text files and making them look acceptable on the internet).
There are some advanced features which would be distinguishing, if I had treated them more thoroughly:
- Good graphical preview in an editor.
- Intuitive handling of images and diagrams and so on.
A.k.a. the static site generator. The core bit. The software that takes your plain text files and turns them into friendly websites.
There are lots of tools to do this. There are hundreds or maybe thousands of static site generators, stemming from the primordial (and no longer active) static site generators such as the venerable bloxsom.
The top few in my community seem to be
- Jekyll (ruby) which is the default for github, although I personally could never make it work for me.
Hugo (go) is a popular system.
b-ber is both a method and an application for producing publications in a variety of formats—EPUB 3, Mobi/KF8, static website, PDF, and XML file, which can be imported into InDesign for print layouts—from a single source that consists of plain-text files and other assets. b-ber also functions as a browser-based EPUB reader, which explains the name.
- Pelican (python)
There are some extra ones, below, that integrate specialised editor apps, a.k.a. CMSs, which are mentioned below.
One can find many more.
hugo are opinionated and provide a featureful setup per
Others, like lettersmith
take a DIY route where they provide the libraries to build something minimal.
There is an academic derivative of hugo called Blogdown which might be of interest to the general population, since it includes msuch luxuries as such as preview rendering using the rstudio editor. See the blogdown-book, or the various academic intros, e.g. by Emi Tanaka or Rob Hyndman.
Some themes have been tested against blogdown.
Try JAMstackthemes for a smörgåsbord of themes for various software.
Site hosting choice
Ultimately the content still has to be visible online, so I need to get a web-host.
If your static site system comes with some kind of app that will edit that site it is called a CMS, for content management system. There is a continuum between that and an editor with integrated static site generator capabilities. Also there there is no sharp distinction truly between online (internetty) and offline (on my laptop) editors, for all that I have tried to make one below for the sake of simplicity. Sometimes the local CMS can run on the internet, sometimes that would be unwise or inconvenient.
If you use markdown, which is the de facto standard markup for plain text blogging it might be a good start to simply preview that in the old text editor. If you are using some other weirder specialised markup, good on you but I will not cover that here since presumably if you know enough to do that, you know the consequences.
For a combination blogging tool and encrypted markdown edition note storage you might want to use something like standard notes, which costs some money when you use the bells and whistles, although might be worth it if your notes include confidential ones.
Preview tools, that show you plain text as rendered web-style HTML, make it all nicer.
- Lektor is a static site generator with an integrated local CMS that looks Wordpress-like. Seems to be made of python.
- publii is a desktop-based CMS with integrated site generator for Windows, Mac and Linux. Seems to be based on Electron/node.js.
- Text editors Atom and vs code have built-in markdown preview. The overall workflow is developer-centric.
- RStudio has sophisticated integration with blogdown blogs.
- NetlifyCMS is Netlify’s generic CMS client for various static site backends offering a friendly, integrated CMS workflow.
A blogging platform with no interface
Why a blogging platform with no interface? So you can blog with your favorite tools. Blot turns a folder into a blog. Drag-and-drop ﬁles inside to publish. Images, text ﬁles, Word Documents, Markdown and more become blog posts automatically.
- cactus, below, features a GUI app too.
- Hokus is one just for Hugo sites.
- As mentioned above, Caddy has a built-in automatic hugo editor.
- marked is cheap macOS markdown editor/previewer…
- … inspired by Notational Velocity – specifically the reboot nvALT which has its own noteworthy features (high tech search)
- restview is a previewer for an alternative markup called ReST
- mou is cheap and looks nice.
- and (free! open source! mou-like design): Macdown
- livereload turns any browser into a preview tool.
Experts can run a localhost dev server which will host a minature wersion of the website
Websites that edit your website for you.
- forestry seems popular?
- gitbook is a markdown website GUI and publishing toolchain.
- classeur attempts to be friendly for more than nerds.
- “Prose provides a beautifully simple content authoring environment for CMS-free websites. It’s a web-based interface for managing content on GitHub. Use it to create, edit, and delete files, and save your changes directly to GitHub. Host your website on GitHub Pages for free, or set up your own GitHub webhook server.”
- cactus is a plain website generator, that features a GUI-ish client, cactus for mac
- Draft is another popular frontend with many features of varying usefulness (“ask an editor” function?)
- Wagtail plus django-bakery is a fancy python/django CMS that can render static sites.
Gitit is a wiki backed by a git, darcs, or mercurial filestore. Pages and uploaded files can be modified either directly via the VCS’s command-line tools or through the wiki’s web interface. Pandoc is used for markup processing, so pages may be written in (extended) markdown, reStructuredText, LaTeX, HTML, or literate Haskell, and exported in ten different formats, including LaTeX, ConTeXt, DocBook, RTF, OpenOffice ODT, and MediaWiki markup.