All codes that work on proboards

[Adira]

Hello, I like to make templates! I know there is a plugin that allows for more codes to work. But I was curious if there was a documentation or a post somewhere that lists all codes that actually work on proboards, I LOVE, the preview feature so much, so I like to design my templates with as much preview-ability, as possible.

[Scott]

Adira -

The layout templates accept HTML, JavaScript, and CSS (via inline or style tag - however it's best practice to use the corresponding CSS Style Sheet). And fyi, a plugin is nothing more than packaged HTML, CSS, and JavaScript.

The layout templates also offer our own built-in template variables which are predefined code represented in an abbreviated form depicted as $[text]. (Note: the use of brackets [ ] should not be confused with BBCode tags). Template variables may not work on all templates.  On the right-hand side of a template window is the list of variables that are available for that particular template.

[Chris]

If you were instead referring to posting templates then the Supported BBCodes topic would be the resource you were asking about. It is not, however, an exhaustive list with BBCodes such as [ol], [h1], [h2], [br], etc. not listed there.

The posting preview will give you immediate feedback on which BBCode, attributes, and inline styling are accepted when you flip between Preview and BBCode. If the BBCode tab retains the BBCode you wrote after flipping to Preview and then back again, you can be certain it is accepted code. With that simple tip, you can test actual HTML (replacing angle brackets with square brackets) to discover other BBCodes that may have gone unlisted.

The real fun comes with the inline styles, where you can use actual CSS to style an element within the post with certain limitations. You can see a list of CSS that was tested in the All Supported Inline CSS Properties topic, but that as well is not an exhaustive list and you can discover more via that flipping technique described above. If a discrete property is not supported you may find it is supported if included in a shorthand^[1] version.