LazyWeb: I've been using Publish for my website/blog, but the tool isn't exactly being actively maintained, and I'm loathe to put much coding effort into improving it by myself. Should I make the hop over to Ignite? Is there another Swift static site generator that's also Markdown-centric, so I can focus on the writing rather than the infrastructure?
=> More informations about this toot | More toots from dgregor79@sfba.social
@dgregor79 As you know, we nerds all write our own static site generators, which is a terrible decision that most of us would make again, if given the chance.
=> More informations about this toot | More toots from siracusa@mastodon.social
@siracusa @dgregor79 it took less startup time to throw together a horrible static site generator in Perl two decades ago than read the docs for jekyll back then. not sure about the ongoing maintenance time balance though
=> More informations about this toot | More toots from joe@f.duriansoftware.com
@joe Mine's written in Perl too (obviously, for people who know me) and the maintenance has been a breeze—definitely easier than keeping up with updates and major-version changes to a third-party service or system. Of course, it is pretty terrible…but it's mine!
=> More informations about this toot | More toots from siracusa@mastodon.social
@siracusa yeah Perl 5 is pretty much Latin at this point, so it doesn't need much bitrot maintenance per se. but i do have a twang of regret when i think "i should support preview cards" or "this RSS reader didn't like the way i escaped the article HTML" or some other small compatibility/social media standards thing that would probably be handled routinely by a proper static site generator project
=> More informations about this toot | More toots from joe@f.duriansoftware.com
text/geminiThis content has been proxied by September (3851b).