This comes in at perfect timing. Was fiddling around with this exact layout for hours. Really appreciate the work. Is there any eta when we can expect a video about the modal menu? Or even a Kevin style approach of a mega menu with brick’s popups? Badly waiting for a nice menu video that does not use default bricks sidebar which just looks so basic and boring….
This is amazing, would you simply introduce a -ve multiplication in the CSS if you wanted the text to overflow onto the image a bit? Watching this on my way to work so won't have time to play around till later but super stuff!
Astounding work as always. Interested in why these feature cards start with the image on the left? As we generally read left to right, wouldn't the image on the right be the preferred starting point?
Awesome section. I can see where that’s super handy, but, question - what’s the issue having both sides full width and having padding on the content container? That’s how I’ve always done it as aesthetically and space wise that’s usually what I want to achieve for a full width section. I think it’s obvious you’re breaking your site container with full width areas no?
@@AutomaticCSS understood. But if your site has a width set and you want some sections full width such as portfolio pages, on a design website, I don’t see a problem with having the content centred in a full width section within each 50% container? It looks kinda odd when the text is still within a site container, but the image appears to be in a full width container, to me anyway. Totally get why you’d want to keep a site width consistent though.
On Feature Section Delta , you use Grid -1 on the parent container to control the alternating sections .. but on Sierra, you use Flex, .. why was that decision made? .. I'm still learning the CSS slowly but surely.
Kevin this might be obvious but here goes. So to not be a chump I deleted all but the first feature grid CSS section, so I was left with one. I then edited this to add my custom fields. I then duplicated that to create five posts. That all works, EXCEPT it's NOT alternating down the page. What did I do wrong?
This is one of the most beautiful things I’ve ever seen in web design.
You're the GOAT, Kevin. You don't know how much you've impacted my life and made it better
Love to hear it!
Used the frame while i listened to the video, was done within 15mn thanks a lot !
Frames is the best investment I have ever done. It’s always getting better !!
Fantastic addition to the ACSS & Frames ecosystem.
This is just fucking awesome!!! ACSS and Frames is the best website building duo.
Frames is becoming more and more powerful. Well done ! We really need you to developp it for Oxygen !
I like the many easy options and the growing images according to content size is a great thing. Another nice addition to frames.
Really useful Kevin - awesome stuff
Nice and useful section!!
This comes in at perfect timing. Was fiddling around with this exact layout for hours. Really appreciate the work. Is there any eta when we can expect a video about the modal menu? Or even a Kevin style approach of a mega menu with brick’s popups? Badly waiting for a nice menu video that does not use default bricks sidebar which just looks so basic and boring….
Modal menu overview soon
I can't wait for it, for most of my Woo projects I need to use mega menu 🙏
Kevin, this is a great addition. I'm wondering if this frame can be used with a query loop? Great job.
Yes, absolutely
@@AutomaticCSS Wonderful! Frames & ACSS gets better and better. What a great investment.
Very handy, thanks mate.
This is amazing, would you simply introduce a -ve multiplication in the CSS if you wanted the text to overflow onto the image a bit? Watching this on my way to work so won't have time to play around till later but super stuff!
I would have to play around with it but it’s probably doable with a few adjustments to the cards grid structure
Astounding work as always. Interested in why these feature cards start with the image on the left? As we generally read left to right, wouldn't the image on the right be the preferred starting point?
Because you can make the grid go either way. Check the FAQ here: getframes.io/frames/feature-section-sierra/
Awesome section. I can see where that’s super handy, but, question - what’s the issue having both sides full width and having padding on the content container? That’s how I’ve always done it as aesthetically and space wise that’s usually what I want to achieve for a full width section. I think it’s obvious you’re breaking your site container with full width areas no?
Because then you lose proper page width content alignment.
@@AutomaticCSS understood.
But if your site has a width set and you want some sections full width such as portfolio pages, on a design website, I don’t see a problem with having the content centred in a full width section within each 50% container?
It looks kinda odd when the text is still within a site container, but the image appears to be in a full width container, to me anyway.
Totally get why you’d want to keep a site width consistent though.
Brilliant
When is the update dropping?
These frames are already available. We are releasing new frames all the time.
On Feature Section Delta , you use Grid -1 on the parent container to control the alternating sections .. but on Sierra, you use Flex, .. why was that decision made? .. I'm still learning the CSS slowly but surely.
There’s really nothing special about a 1 column grid versus flex column.
Is it possible to do a query loop on this?
Yes
Hi, Kevin! Why Feature Section Heading is H2 and not H1? Is there an H1 on the page that can't be seen? Thank you!
Only our hero sections have h1s
Kevin this might be obvious but here goes. So to not be a chump I deleted all but the first feature grid CSS section, so I was left with one. I then edited this to add my custom fields. I then duplicated that to create five posts. That all works, EXCEPT it's NOT alternating down the page. What did I do wrong?
I’d need a link. Ask in the group and people will answer in minutes usually.
That JS use is some real gold .. that's not how you do debounce functionality btw .. you're just stacking the event loop with mung for no reason.