I've just released Dagger 1.3.0, which adds two new notable features: the "when" and "for" compiler attributes! 🚢🗡️

I've been dog-fooding these for a few months, and am very happy with how they feel to use 🥳

If you'd like to learn more, you can check out the project's GitHub page:

https://github.com/Stillat/dagger

Antlers Components v2.3.0 was released yesterday and brings support for #fluxui to #statamic Antlers 🥳

https://github.com/Stillat/antlers-components

After a ton of refactoring today, the first version of Tidal (a starter kit for Statamic) will ship with

* Support for multiple projects
* Each project can have multiple versions
* Multi-site support

Tidal Multi-site now runs on the same core as the regular starter kit 🥳

Just some final testing & validation, a few more help/documentation materials left, but I should be looking to ship within 1-2 weeks!

This has felt like an absolute marathon, but most of the development on my Statamic documentation starter kit is complete, and the initial writeup for all the documentation is done.

I have some minor tweaks to make, a few extra passes to make on the documentation, and may split some of the features into their own addons... but things are getting close!

Just wrapped up some major refactors to the social media image generator that will ship with my Statamic documentation starter kit:

* Images are now stored in an asset container (instead of a hardcoded location)
* Images can be queued (with edit spam prevention)
* Customized templates per collection/blueprint combination (or a default if you want to keep things simple)
* Override images on a per-entry basis, if desired
* Lots more!

Wondering: should I extract this to its own separate thing? 🤔

Added Feedamic to the documentation starter kit (still WIP) and wanted to reuse the auto-generated social media images as the feed's image. I didn't want to add a new field for this and remembered: oh yeah - computed values!

Now, it uses the configured social media image 🥳