react-hands VS statux

Oh man I have checked out your library and loved it, and I had also made a similar library: https://github.com/javaScriptKampala/react-hands a last month or so, but now all this time I plan to rewrite all of it to better after digging more into the state management land and learning about what other big players are doing and why, one thing I still don't like about existing solutions though, they don't seem react-ish to a react developer, they seem very abstract and follow wired patterns, so now am like what if we make a library that is doing all the crazy things to manage state efficiently under the hood, but on surface behaves and has a similar pattern to useState or react hooks that to a react dev it feels so natural? And checking out your library, it seems it is what I wanted to create just with a few differences, I got some even interesting ideas on this, so how can we team up?

Does anyone think react can handle most state management issues? As today's apps are usually server data or server cache intensive than app state and hat has given more rise to libs like react query? Anyways I think react can really handle app state of 99% of the time, hence am building some state management library based on react hooks instead, the end result is a simpler and familiar thing than most of these wiredo state managers that need the dev to learn a ton of concepts, check it here: https://github.com/javaScriptKampala/react-hands and give honest feedback, first release for now by the way, don't expect too much, but much coming in next release!

https://statux.dev/ (1.06kb) state management

Has no data management, I don't want my data mixed in my routers 🤷‍♂️ (for that I use https://statux.dev/)

I have an unfinished side project called Documentation Page:

https://documentation.page/

It's "unfinished" because I'd need to integrate payments and do all the accounting on my side (non-trivial as an individual living in Japan), but otherwise it's worked pretty well for my own projects.

It parses your Github Repo (according to https://documentation.page/documentation#getting-started) to generate the website. It can be a single readme.md file (for smaller projects), a folder called "documentation", or you can configure it otherwise. Some examples hosted by Documentation Page:

- statux.dev: simple single-page docs and website, menu config in https://github.com/franciscop/statux/blob/master/documentati.... Similar to form-mate.dev & vector-graph.com

- react-test.dev: split into multiple pages, you specify the folder and it'll automatically merge the markdown files. See config https://github.com/franciscop/react-test/blob/master/documen...

- crossroad.page: has an landing page, but that is not officially supported (yet). See the configs in https://github.com/franciscop/crossroad/blob/master/document...