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

Ohmyn0 wrote:

Dessamator wrote: I justed tested out the potboxconverter recently enabled here, and though it seems good, but there are a couple of things that seemed to have been overlooked.

[...] Great suggestions, thanks! There's definitely room for improvement in regards of previewing the templates. We erred on the side of preserving too many parameters over losing any (we found it's easier to remove unneeded params then add them.

We also want to improve the intelligence of knowing what's an infobox and what's not – the right rail module and in-editor alert are over-aggressive and the Insights list is under-aggressive. We have some improvements in the works for this at the moment. Yes, I noticed that generally speaking the insights is more accurate than the right rail, or edit-note. But it is great that you're still iterating and improving.

Anyway, I was looking at these tags again, and I think that there is a way to further simplify the coding. Rather than adding a lot of tags, you could simply take the "source" attribute as the label making this:

Equivalent to this:

Producing this html:

Basically, it uses the attribute in the "source" as the label, this is kind of a short-hand that will reduce the coding and complexity required, and reduce the need to use tag. It could also replace underscore "_" with a space for longer and descriptive labels.

If someone types out the whole thing it would work as normally.

Edit to add:

In the event that some users don't want the "label" shown, it could simply have an attribute 'showlabel="true"', or simply add a prefix, e.g. "source = "$Items", which would automatically make it show/hide the label.