the long and short of it, we've shifted to using the list block... for ease of cms use there may be some configuration/additional dev required, but it's what we've moved to since releasing our tabset module
we've found that each approach adds complexities:
separate elemental areas create a tightly coupled frontend to cms setup, while the elemental lists can have quite a bit of learning curve for cms users
@Julius we've utilized the list block with a dropdown to set width based on the bootstrap grid... can't recall if that's in our in-house tools or something we picked up elsewhere but could check
I see, makes sense to me.
but how did you solve adding 2 blocks in one column?
^ same "list block", but the content tab
so for this particular site, I have a "left" and "right" list for this page: https://www.lakeshoreproductions.org/past-shows/shrek-the-musical/
so one list is one column?
I like the approach of the TabSet
the Tabs block represents the column
correct, I have the "left" list to 3/4 and the right to 1/4... I can add any number of elements to each "list"... I could add a normal block below the "list" blocks at the page level which would be 100% width
and you can add multiple blocks in one tab
when you say "tabs block" what do you mean?
separate elemental areas?
you know the TabSet ?
yes, the native tabset in SS
oh, that... ya, that's ours lol
yeah so each tabset has multiple tabs.
each tab can contain multiple blocks
I'd have to check back on that as I can't recall if we currently use that in it's capacity at this point
let me do a quick install and I might be able to give some context
thanks for helping @muskie9
no prob, flexible layouts is a hot topic and there's quite a few ways these days to do it
this'll be a good test for our readme too 😉
so out of the box it appears you can nest the tabsets, however, I'm not sure how those are rendered honestly... would you mind opening a ticket requesting additional documentation... I can't promise the module will suddenly become more defined, however it'll bring it back on our radar from a planning perspective
I'll have to check with our FE team to gather any current implementations to shed light on usage at this point
totally missed that lol
when did the docs get a facelift? feel like I looked at them earlier in the week and didn't notice the new styles
I'll give that a try, will have the request filter as a fallback
any benefit of one over the other?
I see how you're doing that now
I have it in the PageController currently, so just a matter of getting it on all requests
thns @wmk, I'll have a peak... my use case is adding the HSTS header to all requests, CMS and non-CMS...