Mastodawn

Hoping to do some project work tonight. So much I want to do but don't know where to start this time. Between Baseline, my website and template work and the dad life, there's not enough time in the day today! 😅

Show thread

Cris.3d ago

Found a gap in the afternoon, and am continuing now with baseline work. Somewhat unusual for me but decided to branch out for a focused `assets-*` refactor.

Also after some internal debate I decided to take a much more opinionated stance on site config. The reasons are:
- the plugin is mainly supporting my workflow atm.
- it is more in line with the educational side of the project.
- supporting "esoteric" configs is a headache I can do without.

#11ty #eleventy-plugin #apleasantview

Show thread

Cris.

The first phase was published some time ago on GitHub. Tidying up phase 2 and 3 before pushing. Not planned the NPM release just yet .

The `assets-*` refactor essentially makes the core module the orchestrator for assets processing. The current esbuild and postcss modules will simply be a processing function.

I feel like this will make a possible for future assets processing if there's ever a need.

The branch is here:
https://github.com/apleasantview/eleventy-plugin-baseline/tree/assets-work

GitHub - apleasantview/eleventy-plugin-baseline at assets-work

An Eleveny Swiss army knife. Contribute to apleasantview/eleventy-plugin-baseline development by creating an account on GitHub.

GitHub

Show thread

Cris.3d ago

Refactoring done for this module. There are three or four open loops ("tasks") I decided to park for later.

Have a peep at the changes in the branch shared previously.

Onwards with the module docs after a short break!

Show thread

Cris.3d ago

Eurm... Insert meme "X hours later...". Once again lost in time and no chocolate.

Huge effort on the `assets-*` module though. Very happy, but hoped to be a bit further on before being this late.

No npm release yet, there's a few things that still need to go in.

To be continued...