-
This checklist helps you installing the 2SexyContent module (http://sexycontent.codeplex.com) on your DotNetNuke installation.
-
This checklist helps you defining a content type for 2Sexy Content.
-
This checklist helps you create any kind of content template for 2SexyContent. It even helps you choose which template type to create (''Token'' or ''Razor'')
-
This checklist helps you creating a '''Token''' template for the 2Sexy Content DotNetNuke module.
-
This checklist helps you creating a '''Razor''' template for the 2Sexy Content DotNetNuke module.
-
This checklist helps you configuring a HTML or Razor template for 2Sexy Content. If you need help to create the template, use 4bd7px8a.
-
This checklist helps you using an existing 2Sexy Content template. To create your own template, use 4bd7px8a
-
This checklist helps you creating and assigning a demo record for a 2SexyContent template.
-
While deinstalling 2Sexy Content, a few tables in the database will not be removed. To manually remove them, this checklist will help you.
-
Use this checklist whenever a new version of 2SexyContent is published - or duplicate the checklist and adapt it to your module to keep the publication process high-quality!
-
If you upgraded DotNetNuke 6 to 7 with 2SexyContent installed, your 2SexyContent may throw a configuration error (Configuration Error: Please follow this checklist...).This checklist will help...
-
If you use DotNetNuke 7 with 2SexyContent and you have WebPages 1 installed on your Server, follow this checklist to create an assembly binding.
-
To design elements inside ''2Sexy Content'', for configuration purposes and to import pre-made templates/configurations, you need ''Designer Permissions''. Use this checklist to get them.
-
If you want to extend ''2Sexy Content'' with a template someone else prepared (called a ''Package'') then use this checklist to get it installed.
-
''2Sexy Content'' has many demos, and the ''Basic Demos'' contain very simple content types (like Title, Intro-Text and Body) as well as simple token-based templates. If you would like to...
-
To hide advanced features from the content-editor (but keep them visible to the web designer) use this checklist.