created ... ago
updated ... ago
#resource
#archive

(used to be a fleeting note)

maybe switch to sveltekit or astro for snlx.net

what's the problem now

what will get worse after the switch

astro or sveltekit

TODO

see also loose-sidebar

Why I've decided not to do it

Most of the tools I make can work with just a few buttons and inputs, which perfectly fit into the 21x9 card format, so

This kind of thing

That also means that the docs / devlog can co-exist in the same note as the tool itself. The cards themselves are going to be quite a bit different, so there's no sense in trying to unify their components. The logic for them is not complex enough to bring in a framework, and if they grow, js now natively supports modules.

Then, moving the rendering into mk-bridge with drop-eleventy

  1. guarantees that what I see in Obsidian is what you see on the site
  2. makes it so any obsidian plugins I have are also plugins for my site, no need to re-implement them