3 ms·

Ask HN: What’s Your Blogging Setup?

5 points by mraza007 6y ago

shoto_io 6y ago
Super simple. For shoto.io we use - Jekyll + TailwindCSS - Github Actions
mtmail 6y ago
jekyll + neflify. Previously github pages, but we need to be able to add specific HTTP header which neflify supports.
jeremy_k 6y ago
Gatsby + Github pages. I run `yarn deploy` and it publishes the built version of the Gatsby app to the `published` branch and Github automatically updates. The `main` branch of the repo remains intact for editing content.
ixacto 6y ago
GitHub pages and GitHub. Super minimal, don’t need to install anything, and easy to export the whole repo.
krapp 6y ago
It will probably be Lektor. I haven't actually blogged anything yet, still putting things together. Getting the blog tags plugin to work on Windows seems to be an exercise in pain.
approxim8ion 6y ago
1. Very basic self-written static site generator using Python, Jinja, and Markdown. 2. Netlify free tier, pulling from a GitHub repo. I build them on my local machine and just push the static output to a public repo. My working folder with drafts etc is a private repo. No JavaScript. I have a contact form that uses Netlify's forms feature, but even that can be done away with if I move sometime later.
gkbrk 6y ago
I use Jekyll [1] to build my blog (link can be found on my profile). I have a bunch of custom plugins written in Ruby. I am currently hosting my blog with BunnyCDN [2], but for a static blog you can go with any host basically. Most of my content is written in Markdown [3] or Jupyter Notebooks [4], with some org-mode [5] sprinkled in. I am rendering the Jupyter Notebooks to HTML with a custom Jekyll plugin I wrote. For comments I am collecting them with a simple CGI script and processing them locally on my laptop. Spam filtering is done with Paul Graham's algorithm [6]. I then bake the approved comments into the HTML so that it can be viewed without Javascript. [1]: https://jekyllrb.com/ https://jekyllrb.com/ [2]: https://bunny.net/ https://bunny.net/ [3]: https://commonmark.org/ https://commonmark.org/ [4]: https://jupyter.org/ https://jupyter.org/ [5]: https://orgmode.org/ https://orgmode.org/ [6]: http://paulgraham.com/spam.html http://paulgraham.com/spam.html

5 points by mraza007 6y ago

shoto_io 6y ago

Super simple. For shoto.io we use - Jekyll + TailwindCSS - Github Actions

mtmail 6y ago

jekyll + neflify. Previously github pages, but we need to be able to add specific HTTP header which neflify supports.

jeremy_k 6y ago

Gatsby + Github pages. I run `yarn deploy` and it publishes the built version of the Gatsby app to the `published` branch and Github automatically updates. The `main` branch of the repo remains intact for editing content.

ixacto 6y ago

GitHub pages and GitHub. Super minimal, don’t need to install anything, and easy to export the whole repo.

krapp 6y ago

It will probably be Lektor. I haven't actually blogged anything yet, still putting things together. Getting the blog tags plugin to work on Windows seems to be an exercise in pain.

approxim8ion 6y ago

1. Very basic self-written static site generator using Python, Jinja, and Markdown. 2. Netlify free tier, pulling from a GitHub repo. I build them on my local machine and just push the static output to a public repo. My working folder with drafts etc is a private repo. No JavaScript. I have a contact form that uses Netlify's forms feature, but even that can be done away with if I move sometime later.

gkbrk 6y ago

I use Jekyll [1] to build my blog (link can be found on my profile). I have a bunch of custom plugins written in Ruby. I am currently hosting my blog with BunnyCDN [2], but for a static blog you can go with any host basically. Most of my content is written in Markdown [3] or Jupyter Notebooks [4], with some org-mode [5] sprinkled in. I am rendering the Jupyter Notebooks to HTML with a custom Jekyll plugin I wrote. For comments I am collecting them with a simple CGI script and processing them locally on my laptop. Spam filtering is done with Paul Graham's algorithm [6]. I then bake the approved comments into the HTML so that it can be viewed without Javascript. [1]: https://jekyllrb.com/ https://jekyllrb.com/ [2]: https://bunny.net/ https://bunny.net/ [3]: https://commonmark.org/ https://commonmark.org/ [4]: https://jupyter.org/ https://jupyter.org/ [5]: https://orgmode.org/ https://orgmode.org/ [6]: http://paulgraham.com/spam.html http://paulgraham.com/spam.html