Assets organize content in a document. Assets are called by the main template (e.g. default.master.tpl) which renders the content currently stored in them. Assets are managed with code via plugins or the theme hooks file.
Vanilla uses these assets by default:
Foot. You cannot rely on every theme having a
Panel, which is typically used as a sidebar. The
Content asset is required, because it is where the view is rendered. You can, however, assign it additional content.
You can create your own arbitrary assets in your templates and simply add content to them using
Gdn::controller()->addAsset('AssetName', $content, 'ContentName'). This is a great strategy for creating flexible themes that are easily customized by rearranging assets in the
A common scenario is using modules to add content to an asset. (Note: In plugin hooks, you will typically be using
$sender in place of
Gdn::controller() since the sender is the controller).
You can set the sort order in which content in an asset is displayed via the config. Use a key like
Modules.Vanilla.Content) to define an array of
ContentName values that you used when calling
We believe that online communities should be intuitive, engaging and true to your brand. Vanilla allows you to create a customized community that rewards positive participation, automatically curates content and lets members drive moderation.
Learn More …