For a very low cost (circa £20 a year for me) and low maintenance website, I can recommend Blot.im - it just syncs with a Dropbox folder, uses Markdown for posts and is basically just a bunch of text files. And you can get it decent-but-minimalist without doing much or any tweaking.
Good to know. Thank you! I was finding that Bear and Blot.im weren't working together well either. Thank you for the suggestion! Maybe Bear can be a good place where I draft my ideas.
A similar flat file blog worth exploring would be Blot.im -
It would be a good idea to group a set of features that each offer to compare functionality between each.
At a high level when measuring performance it would be an idea to define common elements within each to measure, an example would be the time it takes to load x amount of posts.
To be honest, I am not really sure. I am using a platform called blot.im. It allowed me to do it by uploading a picture. It's a really interesting blogging platform. Give it a look!
Good point bringing up Ghost. My understanding of Ghost is that one needs to use the whole suite (website + newsletter). Isn't? Or can one use the newsletter tool on its own?
I use Blot.im for my blog and I love the "platform with no interface" aspect of it. That is why I am (only) looking for a newsletter tool which allow me to (1) host archive under newsletter.mydomainname.com, (2) is open source, and (3) minimize tracking/privacy-friendly
You should check out https://blot.im. It may be the simplest solution to creating a personal website directly from iA Writer files. If you're looking for something in harmony with a minimalist philosophy, you should be happy with the available themes.
You might be interested in blot.im: https://blot.im
I’m a web developer and have built my own stack to be able to publish using iA Writer, but it isn't exactly user friendly. The main reason is that iA Writer works best with iCloud (on desktop not so much, but on iOS all the more) and — if you’ll allow my cynicism — by design iCloud does not play nice with the web. So my solution revolves around automatically rendering markdown files stored on Dropbox into web pages and uploading them to Amazon’s S3 hosting.
I am working towards support for content blocks, but there's a lot of moving parts I still have to figure out (where to store media, for instance).
The absolute best solution would be for iA to add custom publishing endpoints: Wordpress, Medium & Ghost (which you should look into also) are already supported; I would expect adding support for 'bring your own', along with a couple of pages of developer documentation would open up a world of possibilities. Unless iA are considering their own subscription blogging service, ofcourse, which wouldn’t be a bad move I suppose
There are so many blog themes to choose from but for my personal blog I use trooper by Radarthemes . This is my favorites theme for now (minimal and clean) and previously I used blot which I loved but themes were very limited. If one above does not help themeforest has a huge collection of blog themes. Hope this helps!
Thanks for the insight and recommendations! I played around with Grav a little bit but eventually decided on Blot because I liked the fact that it's made by one indie developer (I think) and how simple it is.
Will check VSC.
Thank you!
Thanks so much!
I think I'll save building my own CMS for future learnings. I ended up going for a really simple flat-file CMS called blot that looks awesome.
Thanks again for the insight, I really appreciate it!
Making the library work on the client would be straightforward and is planned. Still, it would be strictly less efficient than processing the page's content before the user requests it.
The library is designed to be idempotent, so the theoretical maintainer couldn't do much damage by passing the output through the filter again, or by mixing filtered and unfiltered content.
It is possible to leave a block out of the filter like so:
typeset(html, {ignore: ".css-selector-for-block-to-skip"});
This is how I render the 'before' section of the demo page.
You can also limit the filter to a particular css selector:
typeset(html, {only: ".only-filter-this-selector"});
This is now documented on the Github page.