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 👀
=> More informations about this toot | More toots from gramynamacu@mastodon.social
@dgregor79 @tiborbodecs created a tool called Toucan that we're using on swiftonserver.com
All of our site is essentially rendering DocC and markdown pages into HTML templates. The DocC bits are done by swiftinit.org, where Dianna Ma has been extremely supportive.
=> More informations about this toot | More toots from joannis@fosstodon.org
@joannis @tiborbodecs “Rendering Markdown pages into HTML templates” is basically all I need to do. I’m check out Toucan, thanks!
=> More informations about this toot | More toots from dgregor79@sfba.social
@dgregor79 @joannis let me know if you need help with it. 😉
=> More informations about this toot | More toots from tiborbodecs@mastodon.social
@tiborbodecs @dgregor79 @joannis Will you be releasing your premium templates any time soon?
=> More informations about this toot | More toots from StewartLynch@iosdev.space
@StewartLynch @dgregor79 @joannis yes, the first will arrive in a few weeks hopefully. 🤞🏻
=> More informations about this toot | More toots from tiborbodecs@mastodon.social
@dgregor79 I'm a big fan of Paul Hudson. His Ignite static site generator is well maintained and, as you know, Paul is also very responsive to feedback.
=> More informations about this toot | More toots from mmmayer@mastodon.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
@joe @siracusa @dgregor79 I dare you drop new perl static site generator in 2025
=> More informations about this toot | More toots from krzyzanowskim@mastodon.social
@krzyzanowskim @siracusa @dgregor79 if i'm going to code something for "fun" then letting anyone else use it would only ruin that
=> More informations about this toot | More toots from joe@f.duriansoftware.com
@joe @siracusa @dgregor79 My own static site is built by a fork of Jekyll from ten years ago because I modified a thing and then never got around to merging in upstream. Where do I rank in this?
=> More informations about this toot | More toots from jrose@belkadan.com
@siracusa I’m a weird nerd, because I have zero interest in writing or maintaining the static site generator itself. It’s not the kind of coding I find joy in doing, and would only detract from what little time I have to write.
=> More informations about this toot | More toots from dgregor79@sfba.social
@dgregor79 @siracusa nothing worse than having to use your senior engineer "do it myself, or delegate" brain on your time off
=> More informations about this toot | More toots from joe@f.duriansoftware.com
@dgregor79 what’s the issue with Publish? Is there anything missing or bugs?
I’m using it myself and haven’t had any issues yet.
=> More informations about this toot | More toots from jandamm@iosdev.space
@jandamm I have hit occasional bugs, and there’s some features I’d like to add (easier linking among posts, automatic Table of Contents generation, etc) that I could add… but it feels like investing in a dead end.
=> More informations about this toot | More toots from dgregor79@sfba.social
@dgregor79 I had written a Vapor app that iterates through the routes and renders them all to a directory. I used swift-markdown library.
It was easy enough. And it let me preview realtime on the local Vapor before doing the render pass to speed things up.
=> More informations about this toot | More toots from pixelscience@mastodon.social
@dgregor79 I do not have personal experience with this suggestion, but you should know about it nevertheless. It might be the answer you’re seeking. Paul Hudson has a Swift static site generator. https://github.com/twostraws/Ignite. He has a video somewhere as well that explains it. Not sure if that video is behind a paywall or not. I’ll find if you ask.
=> More informations about this toot | More toots from bobdel@mastodon.social
@dgregor79 author straight into html by hand 👌
=> More informations about this toot | More toots from jfbastien@mastodon.social This content has been proxied by September (3851b).Proxy Information
text/gemini