Whenever I start I new page in elements I’m always thrown off a little in that there are no document (<body>) properties available. I keep wanting to directly set a background colour, padding, or margins (ie: margin: 0 auto; to centre the content), but the only way to begin is by first adding a layout to a page. Ideally, the document (<body>) would be the first, and top-most container in which everything else is place.
As it stands you drop elements into the viewport, but there’s little concept of what that initial ‘base’ element that you drop things into is.
An interesting dilemma. Do we want to have to build a “body” container for a WYSIWYG app? And if not, how do we address the concern. Maybe it’s just the cost of WYSIWYG? Not 100% optimized.
I’m pretty sure you could justify have a default ‘page’ element without creating any drama. Other than adding properties to a blank document, the only other area you’d see it would be in the hierarchy/node list panel.
Isn’t that in essence what the Container Component is? Yes, you could set up the document to start with an assumed Container (page properties), but is it necessary? Or does it just add unneeded work? Maybe easier to just start a new page with the Container Component already added by default?
I could see a need for the body tag, to add classes to it for setting responsive stuff. Maybe if classes could be added through project template using a variable, then that wouldn’t be necessary.
Yeah, I often used the body tag for modifier or state classes for things such as modals, overlays, menus, etc, where the class is used as a trigger for other styles and behaviours.
