I’m thinking about changing my blog. I’m currently using jekyll but I am going for pelican or hugo. I am also looking for minimal themes since I am not a UI guy so I would prefer if i can find a nice looking clean minimal theme that I can setup that would be great.
I am looking forward to eveyone’s blogsite hopefully I can gain some inspiration from you guys
I use Hugo, with my own theme. Also created a site with a third party Hugo theme recently. I’m less impressed than I used to be. Grumpy rant warning!
divs excessively, in my theme I used far less (with my own css instead for bootstrap). I didn’t end up saving any time with using a “ready made” solution. I’m no frontend guy, but I guess this is the kind of crap they keep pushing out (with the continuous revolution in current hip JS tech in addition), the very reason I avoid frontend work.
My 0.02$ is that if you do your own theme, then use the
absURLfunctions instead of manually concatenating strings to build urls. Internationalization is half-baked in Hugo, that adds another layer of complexity to the theme. If you want that take care of knowing the pieces to be translated from the start.
If you use a third party theme, expect to get issues even from only replacing a single image if it is not pixel-by-pixel the same size.
my blog: https://kodfodrasz.net . The theme is hand-made, with its roots in some old-forgotten third party layout. Pictures are broken, but I don’t care. :P Fixing it is not worth the effort.
the theme I struggled with: https://themes.gohugo.io/hugo-terrassa-theme/. I liked the relative (visual) simplicity, so I hanged on to make my corrections. I hope I’ll have some capacity to contribute my fixes back some time.
Oof, tell me about it. I’m stuck in the 30’s because they introduced a performance regression on pygments, so it takes 10+ seconds to build my website. They won’t fix it because we’re supposed to switch to Chroma instead, but I’m running custom lexers and really don’t want to recompile Hugo if I need to tweak something.
Also now if they can’t find an embedded tweet the entire site build fails, so I can’t work offline.
I’m thinking of moving learntla over to Sphinx, mostly for rST, but also to avoid having to deal with Hugo anymore for that.
Uhh, this sounds bad. I never used any such syntax highlighter, I use highligh.js. Not perfect, but for me it is enough. For your site it does not cut it, as it doesn’t support TLA+, but maybe there is a JS based solution that you could use. I personally prefer progressive enhancement, though it is not good if you are also preparing the content for printing.
I simply don’t plan to update the Hugo powering my blog currently. I don’t feel like writing (blog) anyways, so if I made any effort I’d concentrate it to the content, not the infra. I’ve got some topics prepared, but I don’t have the mood to compose the writeup around the code and results.
I looked into using
Staying on an old version of hugo wouldn’t be so bad except that they don’t version their help, so you have no easy of getting the documentation that matters for your version.
To be fair, I never understood the appeal of internationalization in CMSes and SSGs. If you have the kind of resources to produce versions of most pages in multiple languages, then you likely also have the resources to maintain independent websites in each language, and it’s easier to have a site per country than sort out every detail (unlike in applications, i18n for sites it far from being just about different strings).
For me the mental model of having a single site with parts in multiple languages to plan tasks, and such. I can accept that for others this may not be true. Also the possibility to navigate to the same content in different languages may help. This deep integration is hard if i18n is not integrated in the CMS.
For example a few days ago I was searching for a specific type of ink for fountain pens, and I got a hit on a Japanese language site, not on an english, for some reason. The site was of a well known manufacturer of premium inks. With a single click I was on the English translated version of the same content and I could evaluate the features of the ink.
And yes, i18n is much more than strings translated, but that is one crucial point, because having stuff hardwired in the templates at a gazillion places makes it harder to internationalize later. Regarding the above Example: I had problems with getting Hugo to support this operation for only partially translated sites, where some pages might not have their translated counterparts. The template got insanely complicated, because the list/map manipulation functions provided have only a limited abstractional power, and the complexity got out of hand and rather let the feature go.
Fair point, though this is largely a search engine algorithm failure, or webmaster’s SEO failure. It’s good that there’s a simple way to workaround it, though for a sufficiently interested reader, manually navigating to a different language version is usually not a problem. My point is mostly that, if you don’t have resources to maintain a version of each page in more than one language, you usually don’t have the resources to get i18n right either, so it’s not worth the trouble. Great i18n is a lot of effort, and technology only makes a quantitative change in the process, not qualitative.
Which manufacturer by the way? I find that Lamy’s ink provides all “bang for the buck” I want from it, especially compared to the Parker ink, so I never looked further.
Platinum. Their site is broken at some points. Typical japaneese website :) But their pens are said to be excellent, as for typical Japanese engineering products: they have dirt cheap entry and expensive premium products, each of excellent quality.
I have a Lamy Safari pen now, which is fine, but the stock Lamy ink is not waterproof, which I had to conclude when some water was spilled on my journal. Then I looked for water-resistant inks, and I found Platinum’s offerings.
Now I long for a Platinum Procyon pen, but the local dealership is closed due to the coronavirus restrictions, so I have to wait a bit now. I plan to use the Platinum Carbon Black ink, or some of the mildly water resistant inks which oxidize over time and get darker, eg. Platinum Sepia Black.
You might want to give the De Atramentis Document Ink line a look. Waterproof / lightfast, and a pleasure to write with. Does perhaps require a bit more diligence in cleaning, but I’ve mostly had good luck.
I’ll definitely check it out. Thanks!
Oh, Platinum of the Platinum Preppy fame. I see. Their site only proves my point though: many links on the english version don’t work. :)
Water resistance is a good point. I tend to just be very careful with things that aren’t knowingly waterproof, so I never noticed, but I’ve done a quick test and the results ain’t pretty.
I use Emacs to generate the site (the built in Org mode export plus a couple of short utility functions I wrote and hooked into the generation) and wrote up a few CSS rules to lay things out. It took a couple of nights to set up, and the code is so ugly that I don’t want anyone else to see it, but it has served me very well. Easily one of the most flexible systems I’ve used so far.
Result visible at https://two-wrongs.com
I must say your theme looks pretty good
I love the
footnotessidenotes and the table of contents.
Very nice! Looks like (at least inspired by) Tufte css (with different typeface choices). https://github.com/edwardtufte/tufte-css
I actually didn’t know about Tufte CSS at the time, but it is absolutely inspired by Tufte’s books, and the Tufte LaTeX theme that’s around.
I’m a definitly a fan too.
wow, thats quite pretty. As @bezdomni said, those sidenotes are so cool.
https://danluu.com is a wildly popular blog with a minimal theme. Don’t worry about the theme, worry about what you write.
Totally agree. I am just making it look nicer so when a recruiter lands on the page he likes it lol But It’s true content matters
I use Zola for my blog. I did the theme myself. I’m no designer but you can get a long way by choosing one nice font and following some typography guidelines, such as A Five-Minute Guide to Better Typography.
I like the theme you built. Very clean and easy to read.
I also just finished redoing my blog with Zola. I’m a big fan of it already.
I like it Is your theme open source
Thanks! It isn’t at the moment, but at some point in the future (when I get around to it) I’ll clean it up and make it available.
I just visited your site and didn’t have assets cached. Site was fully loaded and I waited a bit for the font to load. Didn’t dig deeper, maybe external webfont?
The font is self-hosted as well. It’s a variable font, which requires a modern browser.
Logarion written in OCaml, an archiving system for Markdown texts. Static generation is just one aspect of it. The static generator is fast.
My personal theme: https://notes.orbitalfox.eu/
Well I personally just write html myself for my website but last time I used a static blog generator, Pelican was a real good tool. It’s powered by Python and really easy to use. You also write your content in Markdown markup.
+1 - Pelican is squeaky clean. The codebase is elegant and well thought out. Very easy to read, understand, and extend.
Very strong recommend, especially for folks who want to twiddle and tweak but not because you HAVE to.
I’ve been running Blosxom since 2004, and in static mode since 2008 or so. I stopped messing with design etc a long time ago and now try to update it at least monthly - mostly book reviews.
I really like the Blosxom model and have at various times used to generate other kinds of feeds.
wow, thats a name I haven’t read in a long time. I used to be a Blosxom user as well way back when. Are they still developing it?
I don’t think there’s active development, and the plugins are scattered all over the place.
The main draw for me is the Markdown support - I’m still using Gruber’s original Perl file as a filter.
I just use a Makefile + pandoc. For my size it’s quite enough. An atom feed is generated using a AWK script.
I would probably use pandoc if I were to start again from scratch; it’s really useful without being overwhelmingly complicated.
I use zola with no theme for my blog
I came to say this as well. I’m very fond of zola.
I use Hyde (http://wiki.call-cc.org/eggref/5/hyde) for my personal website (https://avalos.me/) and Hugo for my blog (https://blog.avalos.me/), using the Etch theme, which is pretty minimal and nice. I’m starting to think on moving my blog to Hyde as well, so I can have it along my personal website.
That’s pretty cool. I am using a similar theme for hosting my notes and things I learn across the internet https://knowledge-book-six.now.sh/
I am currently loving the community responses. Everyone’s blog is awesome and unique
Why do you want to switch from Jekyll?
my bet would be that it is slow.
It takes about 2 seconds for my site, which is probably more complex than most. I mean, it could be faster, but is spending hours to save 2s really worth it?
It probably depends a bit on what you’re doing with it. I am using Liquid for some thing that would be better done in a Ruby extension so that I can retain the ability for them to work with the GitHub Pages install. As a result, I’m doing some O(N*M) things (iterating over one list for every element in another) which could be a lot more efficient. I don’t care too much, because N and M are both <10, so in the worst case it’s still pretty fast, but I can well imagine similar patterns appearing in other places because it’s the easiest way of doing things in Liquid. That could easily make Jekyll very slow. That said, I don’t think I’ve seen it take longer than 10s (and that was an old version on a slow machine).
Won’t that be an issue for every site generator with a template system? The Go template system isn’t especially fast either for example.
It’s not too hard to just wire in some Ruby code in Jekyll btw, which is actually quite powerful and a major advantage of it over e.g. Hugo IMHO. I do some ugly things with it, but, you know, it works :-)
It depends on the template system and whether it has any kind of map data structures that you can build. The problem with Jekyll’s extension mechanism really only applies if you care about GitHub compat. For most of the things I’ve built with Jekyll (other than academic pages, where jekyll-scholar is essential), I try to support the GitHub Pages version, which doesn’t allow other plugins to be loaded. It’s a shame GitHub doesn’t support plugins with some limits on RAM / CPU usage.
Oh, I didn’t know GitHub doesn’t support plugins; the plugin system is one of Jekyll’s best features IMHO, and Ruby gives you the power to change just about anything without too much effort (Go is a much more restricted language).
I use Netlify and my plugin hacks work fine there 😅 Using Netlify also isn’t much more effort than GitHub Pages (you can link it to the repo to republish on push), so perhaps something worth looking in to if you’re interested.
I found Jekyll slow back in the days, far slower than 2s.
Jekyll 4.0 and the releases leading up to it made it basically as fast as it can be given the language and architecture restrictions.
That’s main concern it’s slow I’m thinking about hugo but it’s so confusing
I’m using nanoc, which I’m finding to be quite extensible, modular and powerful while remaining extremely easy to use.
Wrote my own in Python—vite. My blog’s theme is just handwritten CSS, with a little help from @nerdypepper. :) You can find my blog at https://icyphox.sh, and its source at https://github.com/icyphox/site.
I love your theme can I use it for my own blog
Absolutely! It’s MIT.
I’m loving it man Is it similar to pelican what if i want to additional plugins to it It’s clean and simple
I’ve never used Pelican, so I can’t answer that. vite’s code is a little hacky, and somewhat tailored to my site, since I didn’t think anyone else would bother using it. Feel free to steal the CSS though.
I might just use the same css and update it with my own content
Great minds! I wrote a similar one in Python + jinja2 called tinysite, which powers alangrow.com. In short, I got tired of waiting for jekyll rebuilds. tinysite has dynamic preview, fast parallel rebuilds with
make -j, and an include mechanism for page data.
Woah! Your generator is far more sophisticated than mine. Good stuff.
Hey I like you static site generator I couldn’t find documentation on how to use it
That’s because there isn’t any! It’s a personal project so far and pretty rough around the edges. You can get a sense for how it’s used by looking at the code here: https://github.com/acg/alangrow.com
I am currently in the process of building my own website and Pollen looks very interesting to me. The markup language is implemented as a Racket DSL which makes it extendable and flexible to use. When I use Markdown, there is always something missing that I need, and in Pollen I can just create my own markup elements. And whatever I need to compute or automate, I can just do that in Racket. Here is an example of custom markup that I defined.
I wrote my own thing in bash and node.js to generate my blog. I wanted to write in markdown but also use statically-rendered LaTeX. Before this, I tried Jeckyll with a KaTeX plugin, but it was slow as hell and way too complicated for my purposes.
Now, building my blog is not extremely fast, but it takes about 5 seconds instead of 10 minutes. Plus I more or less understand each part.
I use makesite.py, it is simple Python code.
I used to work with Jekyll, before I discovered Hugo a couple of years ago, and have never looked back. Honestly, the speed factor trumps everything else. Also, the fact that in typical Go fashion, it comes as a single binary that is ready to get executed as soon as you fetch it. I have had so many issues with Jekyll before, due to different Ruby versions, gems, etc. I do not want to even look back.
So, my blog uses Hugo as mentioned, together with a modified by me version of a popular theme: hello-friend-ng.
I use a script written in the rc shell, mostly just because I wanted to play with the rc shell.
Articles are stored in subdirectories
enlinked to the root. I only write in english though, except for one practice article in Dutch which I’m never going to publish, but as I say, the whole system is so that I can use rc.
For mine I use redo with multimarkdown with a custom css file for theme.
Actually looking at the whole blog, I remember it from the post on plotting with R. Now that I look at it with a different eye, I wanted to say that it looks nice and I love the use of redo, which seems like a perfect fit for things like this.
Thanks! The style of the blog is still building up, I am in a constant fine-tuning stage.
But your comment regarding redo is spot on. It is a perfect fit for building websites. I also use it from within R to specify dependencies. You can even include redo-ifchange calls within R or R-markdown scripts and it rebuilds the dependencies for the script.
Having tried just about all kinds of static site generators under the sun—from the more mainstream ones like Jekyll and Hugo to more exotic ones like ssg, ox-hugo, org-page, Org publish, org-static-blog, Haunt, and even a custom one written in Haskell—I’m now back to hand-written HTML files + SSI rules (for simple templating), and love the simplicity. The only thing missing right now is an Atom feed. I wonder if I could use GNU M4 for that, like @technomancy does.
Result at https://bandali.eu.org, “sources” at https://git.bandali.eu.org/site.
If your page structure is more or less consistent (looks like it is), you can extract metadata from pages with an HTML parser and generate a feed from it. That approach allows some things that are impossible or unwieldy in the traditional paradigm, such as using an arbitrary paragraph for post excerpt, not the first one.
My own generator automates that process: the blog index of soupault.neocities.org/blog is produced by this config. It can dump exported metadata to JSON, which isn’t hard to produce Atom from. I’m still to complete the JSONFeed/Atom generator script good for public release.
That said, making a custom page to Atom script using an HTML parsing library that supports querying the data with CSS selectors (BeautifulSoup, lambdasoup etc.) isn’t that hard if making it work for anyone else’s site isn’t a goal.
Indeed; that’s one of the approaches I’m considering. Also, soupalt seems quite interesting, thanks for the links; I’ll check it out!
I also missed a tool to generate RSS from a tree of HTML files. This is how I generate my RSS with a very basic shell script using html-xml-utils:
Nice, thanks for sharing!
Any particular reason you switched back to handwriting html files?
Yeah, a few, actually:
I’d like my site setup to be very lightweight, both on the server and on my machine when editing, and use tools that are nearly universally available on all GNU/Linux systems. This rules out things like my custom static site generator written Haskell, since Haskell and its ecosystem are arguably quite the opposite of my two criteria above.
I’d like to have convenient complete control over the generated HTML output, and this is rather hard to come by in most existing static site generators and rules out most markup formats, since almost none are as expressive and flexible as HTML.
Aside from the repetitive pre/postamble bits in each file, I find writing plain HTML quite alright, actually. The annoyance of HTML’s lack of built-in templating and simple conditionals can be solved by using SSI directives, which are fairly widely supported across web servers. Alternatively, I’m considering using GNU M4 in place of SSI, if it results in a simpler and cleaner setup. And it fits the two criteria in my first point above too.
These are rather valid arguments. I used to write in plain html too, it’s perfectly fine, especially with an editor’s auto-completion like emmet. Nevertheless, I now mostly write in markdown and enjoy it. Whenever I need something more complex, I just embed html.
I use Hugo with my own theme that was originally based on the Mainroad theme, but I rewrote most of the code so that there is not much left from the original code. But Hugo is really awesome. Maybe also take a look at the theme gallery.
My blog: https://jlelse.blog/
Wrote my own based on
groff. People hate it being mobile-unfriendly so much that when my posts gain traction on the orange site that they copy my text and format it as Markdown instead. I’m satisfied with the results.
It’s okay to have a website which isn’t designed for phones. Phone browsers have a compatibility mode for exactly that kind of site; the phone browser will pretend to be on a big screen and let the user still interact with the site.
The problem is when sites have never been tested on phones but explicitly claim to be phone compatible. Your site does that by having a tag in the
<meta name="viewport" content="width=device-width, initial-scale=1.0">
Could you at least remove that from your HTML and let phone users read your website in compatibility mode?
Sure, tag’s gone.
Now that you’ve removed it, your site is actually pretty functional on my phone! I can just scroll the text part over to the viewport and it nearly fits my iPhone 8 screen perfectly. Now you should catch a lot less flak for it being mobile-unfriendly.
Well that’s certainly an opinionated design.
How about adding a horisontal line between “pages”? I think it would help readability.
Nice theme ! As it is very sober, I am sure it would’nt take much time to make it responsive.
Jekyll + default AsciiDoctor stylesheet + a smudge of hand-written css for overall layout.
Source at https://github.com/nhooyr/blog
That’s very interesting! Fetching all the pages ahead of time with XHR requests in small websites like this one isn’t a bad idea. It works extremely well, I love it!
Thank you, I really appreciate that :)
To be clear, pages are only fetched on hover.
I’m using Hugo with a slightly modified theme for my blog. The theme is hosted at git.sr.ht.
You may want to check out links on https://adol.pw/ CV and Contact lead to 403 forbidden pages.
Yes, I’m in the process of making those again, but I don’t know when I’m going to finish it. Thank you for noticing, though :)
I use Hyde for my blog and freelancing site, both with my own custom “theme”. Why Hyde? Because I enjoy using Scheme (also because I want to be dogfooding CHICKEN as much as possible), and because it’s relatively simple. Hyde does not have too many bells and whistles (in fact, it doesn’t even have ready-to-use themes as far as I know).
Hi, sjamaan! I use Hyde as well for my personal website, and I’m thinking on moving my blog too.
Cool! How did you find out about Hyde?
Scheme, CHICKEN Scheme, Eggs Unlimited 5. :P
A long time ago i threw together a rather ugly shell script called microblog. Due to social distancing related boredem i currently picked it up again and started to refacture it. I think it has two neat advantages:
Is it ready to be used elsewhere? Kinda. I am starting to blog again so i might refine the script further if new needs pop up.
Using Zola (GH) with a custom theme (GH). Really liking it!
I thought about using Zola I might give it a try
I wrote my own. You can see an example of its output at my blog (https://zacs.site/), and find the code on my Projects page.
My engine takes plain text files (so I can write on my phone, computer, or even at work) formatted in Markdown, and turns them in to a static site with a home page, blog and blog archive and RSS feed, and projects page. Other pages are easy to add: for example, I’ve added “Disclaimers” and “Explore” pages recently. All of this is built off a single HTML template file. My site currently contains a little over a thousand pages and takes about half a second to build. It automatically detects new or changed files, so when I’m ready to post something new, I just copy the text file over and run the script. The script takes care of rebuilding the site and deploying it from my home computer. It could just as easily be setup to run on a server, but this way I pay $0 to have a public website on Firebase’s free plan. All told, I’m pretty proud of it.
I’ve been using Hexo for a few years, primarily because it’s the first static site generator I tried and it does everything I need. My blog theme, which I just recently overhauled, is pretty bare-bones hand-written templates and CSS based on my favorite Vim color scheme, Wombat.
I use hugo. Theme is this one. Here’s the site. Despite good intentions, I mostly only manage to blog once or twice a month.
The thing I like most about my setup is the integration with hugo/gitlab/letsencrypt. The fact that all I need to do to publish a post is write a markdown file then git add/commit/push is really nice.
The only scripting required is placing this into
I use Hakyll with some minor adjustments to the default theme which is fairly minimal to begin with. The generator uses pandoc for file conversion, and if you’re familiar with Haskell it’s very configurable.
I use hugo and a theme I developed called The Horus theme my blog lives on GitHub pages at Synchronising Life & Dreams
My site is finnoleary.net
I made a program called wisp to convert S-Expressions to HTML, and I write my articles in that. It has no tracking, minimal CSS, and works fine in Lynx and other text-mode browsers.
I’ve been really annoyed back in 2012 by the time it took Jekyll and other popular contenders to generate a simple site, so I wrote my own - gostatic. It tracks changes a-la
make, so it’s pretty fast.
I use it for my blog (here is the source). I’m almost satisfied by it, since having Makefile-like configuration and go templates gives back okay results - I only wish go templates were a little bit more powerful.
I use Hexo for my blog with a theme I built from scratch. I wanted a node.js SSG, in case I needed to hack around. The dev experience is pretty cool, it’s very straightforward and I chose to use EJS as my templating language.
There is also a fair amount of plugins for the features you might need (rss/atom feed, generating a json of the content…). For instance, I generate a json of all the articles titles, excerpts and tags to have a search engine.
Pelican with a custom theme: https://shalabh.com/pages/site-tech.html. I started with svbhack and over time changed it to something very different.
I use Hugo with my own, minimal theme. I used to use Jekyll as well but migrated to Hugo in 2018.
My site: https://www.dannyguo.com
Hugo has a theme directory if that helps.
I use Jekyll, but I have this vague notion that I should make a DSL to program a static site generator, because my blog only has three types of items:
The only thing that’s stopping me is GitHub Pages having a pipeline set up to compile and deploy my site on push… which is so easy.
I’m looking forward to SourceHut supporting pages, so I can try rolling my own.
I run Hugo, with my own CSS derived from previous iterations of my website. The site is at danilafe.com, and the source is here.
I’m actually quite happy with Hugo, though I don’t use custom lexers nor i18n. My site builds fast, and I’m able to easily extend the rendering using shortcodes. The theme was very easy to port, and I managed to switch to Hugo from a custom dynamic blog in an afternoon.
I write posts for https://technomancy.us directly in HTML, so a few M4 templates and a 13-line Makefile are all it takes: https://p.hagelb.org/Makefile.html / https://p.hagelb.org/list.m4.html
I use rib (written in Haskell, and uses shake), but indirectly through a Zettelkasten tool called neuron. Here’s my website: www.srid.ca.
Disclaimer: I’m the author of both rib and neuron. :-)
I use Eleventy and made a custom theme, cobbled together over the years. Haven’t seen that one mentioned yet, so thought I’d add it.
I use org-publish + a few scripts to generate an RSS feed and optimize the size of the website by taking advantage of a full HTML+CSS minimizer. I previously used hakyll, and nanoc. I tried to have a CSS that look like a markdown in a terminal.
my blog: https://her.esy.fun
Hugo with my own theme - https://themes.gohugo.io/black-and-light/ https://www.davidhampgonsalves.com/
Would like to host it on an ESP32 and run it on solar power, maybe I will at some point.
Wrote my blog in a static-site generator that I wrote (repo). I don’t recommend you use it; it’s probably got a lot of bugs or missing features for general-purpose use, but I had a hell of a great time making the generator.
I wrote about tech choices behind blogging years ago.
Thanks for the thread, I love reading other’s choices, finding their blogs, and wish you luck on yours! 😄
I use Zola, and I’m pretty happy with it. I wrote my own theme, but since you prefer not to do that, I think Hugo might be a better choice.
The latter has a famously annoying templating syntax, but I think its many other qualities make up for it.
Here’s my repo if you want to peek at some Zola source code: https://github.com/2mol/juricho.me
I just used Zola for the first time and liked it (I built this site with it).
I have read that Hugo has an annoying template syntax (from the Zola people), but I’ve never actually used Hugo.
Can someone tell me why Hugo’s template syntax is considered annoying?
That probably depends on one’s personal taste. I like the Hugo templating syntax, because it’s the default Go template syntax, which I use for other things too.
That’s a good datapoint, thanks. In this case it might be worth putting more effort into learning it then.
I’m still on Jekyll for my blog, although at this point I’ve spent a fair bit of effort hacking on the Hyde theme to suit my [lack of] tastes. As a publishing platform it’s proved pluggable enough and while I’d be interested in discarding the Ruby ecosystem in favor of consolidating on Python that’s not motivation enough to prioritize shaving that particular yak.
On the themes front, I’ve seen these floating around in the past and some may tickle your fancy -
Right now I’m using hugo, but I’m not in love with it anymore, so I rewrote the parts I needed to create a very close copy (excluding whitespaces) and wrote about it: https://f5n.org/blog/2020/a-static-site-generator/
Site is still live on hugo because I didn’t write much since then. Still planning to switch.
I’m using Hakyll for my site because if you’re a Haskell person that’s almost obligatory.
Theme? I just hacked stuff together myself.
Hey! So I’ve used and/or tried out Jekyll and Hugo. I can confirm that Hugo is not for the feint of heart and seems to regress quite often! My set up is dead simple. It includes editing content, code, and deploying all in the same browser screen, and its free!
My site https://www.towardssoftware.com is hosted on repl.it! It’s awesome because I can make edits on https://repl.it and click run, and my site is updated instantly, in dev and “production”. The site’s theme is barebones because I don’t really care about the look, but hopefully this gives you a different perspective.
It’s great to have editing, and hosting in one GUI interface for simplicity. If you are more focused on writing, you want to make edits as frictionless as possible. If you are more focused on using a shiny site generator and running scripts to deploy it after every edit, there seems to be a tool to do that written in just about every programming language.
I forked frog for my own blog. I did it because I’m aware that the author has moved on from the project and there were things I wanted to work differently. I suspect that many people using frog are maintaining their own forks. I’m a Racket newbie so my interventions have been small, the main noticeable ones were bug fixes to:
There are more things I want to change but I’ll go for it slowly. As for the theme, I don’t even recall, my blog passed though so many different engines and themes. This one was ported from my old docpad fork. I’m not happy with it and want to change it soon.
I’m using XSLT (xsltproc), a bunch of shellscripts and pandoc. The “theme” is written by me. https://archive.yakubin.com/
I’m planning on rewriting it in Scheme, so it gets more legible, but I don’t have much of an incentive, as it just works.
I don’t update my website too frequently though. I have bunch of ideas about what to add there, but when I have some spare time, I almost always prefer to do something else.
I have used nanoc since several years for my blog. As part of my desire to move as much as possible to Emacs, I am currently working on porting it to a purely Org-based setup. When done, I will finally also have an English version of my blog (not that this is a nanoc restriction, but I never came around to implement it before I wanted to port everything to Org).
It’s not a blog per se, but in my main page I use Lektor. It was created by the same guy that created Flask and has a nice web UI for edit files, also I find it quite easy to write the files manually.
Pelican with mnmlst theme plus some css to add color. See https://frederik-braun.com
I use Pelican for my blog, using my own theme. I haven’t updated the content since having a third child, but I updated the backend to python3 and modern pelican a year ago. I like Pelican because it does just enough for what I want.
My own. I’ve bounced between a few of the more common ones, but there was always something that I didn’t quite like… so I decided to stop forcing other people’s tools to work for me and just wrote my own.
mine :) monopati
I just wanted a very simplistic static content generator.
I use Pelican with a custom theme. It’s all fairly minimal, set up a late Sunday night last year (says my git log). https://rasmuse.github.io/
I haven’t taken the effort to minify css etc, so you can easily borrow my theme from here: https://github.com/rasmuse/rasmuse.github.io
I use Jekyll and the flexible Jekyll theme at my site