Prioritizing simple & maintainable is perhaps most in contrast to enterprise systems, or any system that requires a separate IT person. Minimum viable ops.
#indieweb features & systems should be as easy (easier!) to setup & maintain than smartphones (which have sadly regressed in simplicity & maintainability over the years).
@doriantaylor sounds like a good minimization of tech dependencies, I think we align on principles there.
I have found XSLT hard to “come back to”, e.g. maintaining @H2VX, compared to PHP. #microformats2 is a good alternative to RDFa. v2 syntax has vocabulary independence (and a well defined and tested parsing specification) with the ability to create & use your own custom terms, but simpler, prefixing like HTML5’s "data-*" attributes without worrying about explicit URL based namespaces and fragile qnames.
We can likely do even better. Good to see multiple approaches to the principles of simpler setup & maintenance, plenty of learning opportunities I’m sure.
Under the hood I wanted theming that is simple & maintainable. Perhaps implicit #indieweb pragmatic design principles, since we are creating features & systems that individuals can understand & maintain, likely those with less time (e.g. future selves).
Goals for my theme switcher:
* switch-off the Matrix 20th anniversary (re)inspired theme I hacked in March (similar to 2003 April & May: https://tantek.com/log/2003/04.html https://tantek.com/log/2003/05.html) while keeping the option
* minimal system to add more for fun
Next steps: more themes, and possibly dark/light modes of each theme that auto-switched based on media queries from an OS-level dark mode preference if any.
t