Board Thread:New Features/@comment-24739709-20150518230347/@comment-24473195-20150524110042

DEmersonJMFM wrote: How about a tabber that is placed within the infobox code (instead of in a single parameter on an article) and contains two or three parameters within that code like this one? All of our infobox tabbers work/look this way. Perhaps you're missing the point of the new tags. In technical terms they are meant to separate the data layer from the presentation layer. In layman's terms you keep the data in one place, and change the look in another. Generally speaking those tags shouldn't contain any UI elements, and should only represent the kind of data that is entered into the infobox.

There are many benefits to this, some already indicated by staff. But beyond simply being a standard practice in the programming world, it facilitates a lot of things. If you move your data from one place to another, there is no need to reinvent the wheel.

One can quickly glance and discover what the infobox is about by simply looking at the xml, and problems with the gui won't affect the data itself, because as indicated before if you mess up changing the tags, the whole thing won't show. So this is something that should be created once and rarely edited. But one would still be able to change the styles at will without worrying about the data at all.

The biggest benefit is that it removes the curly brackets and complex code that should never have been placed in the infobox in the first place.

Come to think of it, perhaps the documentation page should also list some recommended guidelines for building the infoboxes, e.g. separating the data, presentation, and logic/processing layers.