Board Thread:Support Requests - Getting Started/@comment-26939652-20160106115352/@comment-26939652-20160107142659

In the case of the Crafted Item template, the visual editor actually pulls all variables - including the infobox ones - and presents it's input form. It is exactly why I chose this route, because I'm still hopeful the input form will grown some brains and have different form elements hinted at by template developers.

As you many notice, this piece also does not include any narrative. It is all static information and we can do this, because all crafting stations work the same way. I've specifically took the ingredient and result information into the main page content, cause otherwise we'd have one more layout with a lengthy infobox and no narrative in the main section.

Given these considerations, what's your view on the approach?

With the page template you may be right. A quest has a lot of narrative and some have twists, extra steps, side quests etc. To hint all this to an editor would not make it easier at all. One would need a wizard with full visual editor support for content or take the Confluence approach where hint-text is clearly marked as such, selectable in one click and disappears at the first keystroke, leaving surrounding formatting in tact.

I do value your input!