Testing Leaflet

Well, with WhiteWind seemingly becoming one that software development stagnation has caught onto, I have decided to look elsewhere. Many others think the same way too, so I'm not alone here.

Leaflet is an entriguing concept. It has a lot more of a playful and fleshed-out feel than WhiteWind. This is coupled, annoyingly as it is very early in its AT Protocol integration, with some inconvieniant aspects.

My Current Gripes

Publishing

As I have observed, if I were to actually want to publish these Leaflet documents, I'd have to dedicate a subdomain solely to it. This does not work with how my website is structured, and is somewhat distressing as I do not want to do a major overhaul with it. I just want a more extendable version of what I already have .

Lexical differences

WhiteWind's blog entries are essentially plain Markdown wrapped in minor HTML. Leaflet's documents seem to be more like Tumblr's, with a block style approach. This means, to migrate over, I'd potentially have to wait for the Leaflet team to either build a migration tool or try my hand at one myself. For something that I write to pretty infrequently, I feel a bit demoralised seeing that.

Post Scriptum

I do understand that Leaflet is a young project, and will as such have a lot of changes. This does give me hope, but I feel like until it matures to a v1 release, I will likely still use WhiteWind, no matter how infuriating it can be.