Managing resources
Resources are snippets of content reused across a Web site. Manage these bits of text as custom resources that you can edited and translate in the Content Manager.
About this task
An example of a resource is the More Info button text written on the Special Offer View. The example view has hard coded text which means you cannot use it in a multi-language context or be edited by non-technical people. The recommended approach is to manage resources as content in special resource Components. The Component can use the General Configuration Schema, or you can create a custom Schema:
- Advantages of Custom Schema
- The main advantage of using a custom Schema are: Users cannot edit the configuration 'key' - its the XML field name of the field in the schema, only the 'value', which is simply the field value. You ensure key uniqueness within your component, as you cannot have 2 fields with the same XML name When you add a new config setting (field in the schema), it is available for editing in all localizations of the resource component (although will be empty) You have some control over the data type used for the configuration field (in theory you could use date/number/categories for the resource values as well as plain text, although the web application Config method will always return a string)
- Advantages of General Configuration Schema
- The main advantages of using the General Configuration schema are: Creating a component based on an existing schema is more straightforward than creating a new schema You do not have schema bloat - having lots of configuration schemas can lead to confusion when creating new content