This topic is for the interoperability of the layouts plugin with any other customisation. Please post any interoperability questions here. Unless otherwise noted, interoperability is handled via adding CSS to your theme or a seperate theme component.
This is such an elegant solution. Thank you! My question is, is it possible for the CSS to still allow the Kanban Board to extend all the way to the right of the screen? See the difference between the Light theme (where I added the CSS) and the Dark theme (where I didn’t).
My other thought was, perhaps another solution is to have Layouts start next to the Topic list as opposed to just under the banner. See where the red arrow is pointing below.
UPDATE: I found a temporary solution. I changed the settings on the Discourse Kanban component to show 4 columns instead of 3 and that helps because now we can still see more columns when adding the CSS that you provided without sacrificing the overlap that happens with Layouts.
Thanks @angus! What I haven’t been able to figure out yet is the Blog Post Styling Interoperability question. How can I disable Layouts for one specific category in which we use the Blog Post Styling Interoperability component? I know that there’s the ability to choose which categories to display Layouts in, but I’m looking for the opposite functionality.
hm, I’m not seeing any issues with the plugin on try.thepavilion.io, which is running the latest version of the plugin and discourse. I’ve set the “Custom Wizard” category on that site to be both included and excluded and that’s working as expected (i.e. it’s excluded)
Could you link me to your site? I’ll take a closer look.
@debryc Technically, this is an incompatibility issue between the plugin and the DiscoTOC theme component, not a bug. I understand that that kind of distinction is almost impossible to know if you’re not familiar with the software, so I definitely don’t begrudge these great reports!
I am going to file this one slightly differently though, so I hope you won’t mind that I’ve updated your post. I’ve also addressed it, so when you update the plugin it should be resolved.
Hmm, nothing I can think of off the top of my head. The width when collapsed is set to max-content so theres no defined width in pixels nor is there any set in a variable like there with the expanded state…