Tell us what are the BC missing tags!

Question

Hello BC developers,
As we're doing work on BC, especially in the rendering engine (you'll hear more about it when it's ready), we would like to also add in BC most of the missing tags that you need, including new fields in various tables (considering that those are relatively simple to implement).
We need you to tell us what's missing. Please be active and help us understand those things fast to make sure we can add them to the backlog.
We've enabled Disqus comments on the Developer Documentation site - as you can see below.Browse the Tag Reference to find layouts and their current tags. (username: alpha, password: bcdevdocs)
http://developers.businesscatalyst.com/reference/tag-reference/news/ne ws-detail-layout.html
We need three type of comments:
If tags exists today in BC that are not documented or incorrectly documented, feel free to tell us in a comment (we'll fix the documentation)
If fields exist today in the database but not in the module layout (e.g. you can edit it from AdminConsole, or is available in the detail view but not in the list view), tell us (we'll include it in the layout if it's not extremely complicated)
If a field or two could be added to a module and make your life way easier (both in the AdminConsole and in the tag) - let us know this, too.
Please visit the site, and tell us, in the comments, for as many layouts as possible, what tags are missing and we'll do our best to integrate them in the new BC engine. It would help also to describe the use case to make sure we understand why the tag is needed and are able to prioritize.
Sincerely,
Alexandru

Answer 1

Hi Alexandru,
I'll start things off...
1. Tags that exist today that are not documented in the dev docs:
- {system_visitordeviceclass} isn't documented in the docs.
3. If a field or two could be added to a module to make your life easier:
- Have a field to turn off wrapping each child element within a 'div' or 'li' or 'table' element: (For products, catalog list, webapps, etc.)
- Have a field to filter webapps from the module tag. Example: {module_webapps,,,,, filter="webapp_custom_field3 == something"}