Issues

• Hard for users to make the difference between inputs that can contain velocity code and text only inputs
• Hard for users to understand what the velocity code will render
• Hard for simple users to map what they see in view mode with the velocity code in edit mode

Solution

• Have a switch attached to velocity enabled inputs that switch the content from velocity code to rendered content
• The switch acts like an inline preview of the velocity code
• It can be implemented using JS, having a css class hook (like .hasVelocity) to desired inputs
• The default state of the inputs (syntax/rendered) can be customized in the Profile
• The default state should be 'rendered' for simple user and can be 'syntax' to advanced users
• For performance issues the switch should be done at least on demand