Well for starters, your makajs.org domain doesn't resolve here.
This site can’t be reached makajs.org’s server IP address could not be found.
Your DNS is only propagating for about a third of the world.
I do like the idea of using JSON to declare element structure, that part is much akin to my own DOM-JON concept, which uses CSS-like "selector" syntax to declare the elements.
Difference being this is server-side not client-side, and I don't like the concept of inlining the view hooks as variables printf style, the cornerstone of how stuff like react works. It encourages rewriting the entire element or element tree and/or swapping all of it on the client side, instead of just changing the one part that needs changing.
It's too much like react and vue, two things I absolutely abhor finding them painfully agonizingly hard to use compared to just using html, css, client-side JS, and whatever server-side language I'm using without the frameworks.
But I have that problem with pretty much all front-end frameworks. There's this line that divides a library of helpful functions from a framework, and when you cross that line I've universally found them to be utter and complete junk.
I wouldn't use it. What it does is conceptually incompatible with the good practices of using HTML, CSS, or JavaScript. Just like React, just like Vue, and just like every other "framework" out there.
BUT from where I sit, it does look like an improvement over react's "lets have people use markup for something that shouldn't even be markup" approach.
-- edit -- Oh, also being JSON you could pass it as JSON client side for CSR enhancement whilst still having SSR fallback -- that's a good thing. Write once, use many times.