Well, the reason I posted on Solid is in the first post i.e. ‘making it more user-friendly to self-host’ a solution / a POD, etc. In general the small technology approach is about lowering the barriers as much as possible and create technology that can be used by normal people with them in full control.
As a developer you have broad choice in frameworks. You are not the target audience. But in a way the above is what Aral built: a single executable that has a simple CLI to publish a full-blown, secure static or dynamic website. It is accessible to those people that only know some basic html or even just markdown (via Hugo integration). It will be most interesting for those who just want to launch a personal website without all the fuss, but also for e.g. SMB owners to set up their own websites (in contrast to services such as Wix where suddenly your static site weighs 16MB and is full of trackers).
So taking it to Solid: The procedure for self-hosting a POD server is still quite involved. What if this was as simple as downloading a file and typing
solid init to spin up a localhost for experimenting with all the right tools and docs within reach?
It is the concept of the simplicity that imho is most appealing to me. There is an elegance in it that is missing in most software projects. And this dedication to simplicity can be very beneficial to Solid. It should be way easier for someone to Just-use-something-Solid, even in this early stage of the project. Solid is not accessible, even to developers, unless they either already deeply invested in the technology or are willing to do so.
Other than that overall attention to all of the small technology tenets to some extent is worthwhile. On some - like zero-knowledge and private-by-default - Solid is already closely aligned.
(PS. as an example re: accessibility I couldn’t figure out what the Visualization Lab PoC does, by just looking there. I know you probably created it for your own use and some others in-the-know, but you may be missing out on contributors)