(About the centered text: that’s not intentional. Could you open an issue on the ‘typescene.github.io’ repo on GitHub? Share a screenshot and describe your browser environment? Thanks!)
About HTML: I think this is going to be a sticking point for a lot of people who get excited about Typescene but realize that it doesn’t work with HTML/JSX. Probably worth an article by itself. This was an early design decision for me early on, and recently there are other frameworks that seem to have come to the same conclusion (mostly Flutter and SwiftUI). I think it’s mostly because we’re moving away from writing page-based interfaces (website-apps like Twitter ca. 2008) to more complex interaction models (like Twitter now). Looking at the future, we’re heading for completely new app distribution models and HTML as we know it might not even make it there.
From a practical standpoint, JSX or HTML parsing just adds unnecessary complexity to me, the framework author. Remember HTML is kind of a programming language to create a DOM/component structure. Why would we want to mix two programming languages in our projects? Writing a UI with Typescene is kind of like writing ‘mostly JSON’ with static (template) method calls mixed in, no parsing needed. I happen to like the end result, but that’s most definitely a matter of preference. Give it a try to find out if it’s your cup of tea!