My standard pages are organized as a list of sections with containers underneath them then everything else. I’d like to create components from the section so that they can easily be placed on new pages. But it seems that that option is not available. Weweb allows the creation of components but only one level lower at the container level. What are some workarounds?
Right now each time I have to use a component I have to first create a section to embed it - very redundant.
Also on the question of resuability, if I create a css style called h1 how can I aply to any text element with tag h1? Right now I’m finding myself having to both apply the h1 tag and the css style that goes along with it. Also redundant.
For components that need to be reused on multiple pages, such as footers, navbars, etc, then I’d recommend leveraging multi-page sections.
For other components, my preferred workaround is to create a section template in my project library with the padding and max-width I like and add my components inside that section template. It’s definitely redundant but a technical limitation we have for now.
Regarding the styling of headings with classes, we don’t link the html tag of a text element to a CSS class. It might seem redundant to apply a class to all your text elements with an H1 tag but it gives you more flexibility if you want to style H1s in different ways depending on the type of page. For example, maybe your H1s on landing pages are not styled like the H1s on blog posts.
For the H1 issue, I agree with you that it’s good to have classes and am trying to mimick the h1{} css behaviour as opposed to the h1.header-1{} behaviour if that’s possible.
For the multi-page section, I just tried it and it does the job for me. Great feature and appreciate the easy-to-understand video.
