Here's another idea to improve Hype — more elements!
HTML has a lot to do with semantical meaning. A div tag should only be used if there isn't a more appropriate tag. As an example, if I'm creating a toolbar menu group, it should go in a <menu> tag. If I'm creating a navigation menu, there should be a <nav> tag.
There are lots of HTML elements. It would be cumbersome to add all standard HTML tags to the Hype interface. So instead, perhaps that “div” could have a field to change the div to a user specified element. That could be fairly useful with groups, which are basically div tags.
That's a minimal improvement. What if Hype went further?
Well, this line of thinking started today because I wanted to make a table. What if Hype had a “table” element and a graphical interface for managing that?
I suppose this goes back to the earlier conversation of data management in Hype. Do people still make HTML tables anymore? I was using emmet abbreviation in Visual Studio Code and I was thinking, this is way too complicated for 2025. 
So, probably more common, what about a <nav> element? What if Hype made it easier to make a navigation menu? It could be a persistent symbol and use scene named for menu items.
What would be the point? I suppose if use of HTML tags improved, wouldn't it help Hype with Accessibility and Search Engine Optimization? 