So this was nothing to do with โBarsโ, great.
the settings description describes the options.
Basically anything on the Discovery page is โdiscoveryโ except for โcategoriesโ, โtagโ and a specific โcategoryโ which are covered by those terms.
My sincere apologies if I am being slow on this 
I can see in the README.md this lineโฆ
- Supports setups for each of: discovery, topic, tag, category OR categories.
In case it is helpful to others, a search on the term discovery provides this helpful reference about โdiscoveryโ:
Yes, this is a good point you raise. And I can see how this might create confusion.
This nomenclature, whilst itโs talked about every so often on Meta, especially by developers (as its referenced a lot in code), is missing from Understanding Discourse for new users and something that is only picked up upon by new people if they engage in discussions specifically related to that functionality.
@JammyDodger do we need to think about addressing that in that guide? Where does someone learn about โDiscoveryโ routes?
Iโm not sure itโs used very often as a โfront endโ term for users. I think I only ever see it in theme components/dev. Iโm not sure where the best place to put it would be? It feels more like an โadminโ word, though Iโm not sure if thereโs a guide for that.
For now Iโve added footnotes to the OP of this Topic, thanks
https://github.com/merefield/discourse-tc-bars/commit/65d0d90c743c6c3303cfa1bfcd90584f7672a16e
(still needs a bit of work on Topic page!)
Topic behaviour has been improved with collapse and dismiss.
New release:
bars-custom-html which now provides the default example settings and allows you to create widgets that are just custom html.https://github.com/merefield/discourse-tc-bars/pull/1/files
@ckshen you were looking for Custom HTML support?
Hello! Please tell me how to add a frame from Twitch to โDโ, for example
This is aimed at developers. If you need help with creating a specific widget:
Thanks for the feature! We used to use the layout plugin to put the map on topic lists. Having the option definitely gives us the possibilities to implement something similar. We will have to think through how to implement it.
Feel free to PR to Locations to add support and I will review. Or you can fund me to do it.
Fix for route transitions.
https://github.com/merefield/discourse-tc-bars/commit/74627b5da67b5ff03696244bdc5e814c6c112e30
Small feature, you can now selectively minimise a bar by default (though it currently has global impact to all routes)
https://github.com/merefield/discourse-tc-bars/commit/ca5272ecb6b35d1e403e6f8176caec584e768445
This now works with Bars:
(you are recommended to use the top bar!!)
Updated last post, the plugin is now a theme component 
Currently this Theme Component is incompatible with โPowered by Discourseโ, so if you want to use it, be sure to turn off:
Iโm incredibly busy atm so fix may take a little time or PR welcome โฆ
From what I see, you only need a small CSS change
From:
grid-template-areas: "leftsidebar sidebar content rightsidebar"
To
grid-template-areas:
"leftsidebar sidebar content rightsidebar"
"leftsidebar sidebar below-content rightsidebar";
Is there actually another issue Iโm not aware of? 
(I can PR, but you emphasize the word incompatible, I wonder If I miss something)
Yes, itโs just the grid css.
thanks for looking at this 
but does that take care of both scenarios (On or Off?) - that was my main fear โฆ and Iโm knee deep elsewhere so didnโt want to get embroiled in this right now โฆ 
I made a PR:
https://github.com/merefield/discourse-tc-bars/pull/2
Let me know what you think.
