1. In BLOX itself, there isn't a way to select a section that doesn't exist, so that shouldn't be an issue for sites creating content inside the BLOX hosted system, or our front-end editorial system, BLOX Total CMS. Since they are essentially the same system, they work in unison in this way.

2. For other front-end editorial systems, you'd have to talk to that vendor about not allowing invalid sections to be chosen for an article. It sounds like the sections should be a choice out of a selection of sections rather than something the user is asked to type in, anyway.

3. As far as auto-creating sections when a new one is found, I would think that it could lead to a lot of accidental sections that are misspellings or incorrect variations of existing sections. They would then not have ads assigned or could mess up page statistics. In BLOX, we like to think of the sections as more well-defined. Keywords, on the other than, are more organic and could vary in this way.

4. As far as searching for "invalid" sections, that is very difficult for us to do. We would have to perform an inverse search on every section tag that is possible from the database, and our developers felt there was no reasonable way to do that.

Hope this helps! Thanks!

Thanks Troy! =)

We aren't using SASS or LESS right now with Flex, but we do have some really interesting tricks we've employed. For one, we have some sections of CSS which are now included in page - which means that you can run UTL in that CSS.

This allows you to do things like conditionals which check the section and then implement CSS if it matches. Or, using a variable color defined in your page customization as the background for a custom block or custom design.

This should be used sparingly, of course, because you don't want 10,000 lines of CSS on your front page.

But it does allow for some programmatic changes, and it gets rid of a separate site CSS http call.