Bad Practices when working with the Text / HTML module
| Introduction and pasting content from Word | Using font tags | Adding tables | Recommendations and Conclusion |  | Other recommendations: Change the Text Editor
I personally always change the default text editor that comes as standard with DotNetNuke® from the FreeTextBox to the FCKEditor.
The FCKEditor produces valid XHTML code. I also find the FCKEditor to be more reliable, stable, and it also has some good extra functionality over the FreeTextBox.
Here you can find out further information and watch a video on installing the FCKEditor to DotNetNuke.
Conclusion
If you follow the methods outlined here for adding content to the Text/HTML module it will:
- Reduce the size of your pages
- Improve page load time for the visitors to your website
- Reduce your bandwidth costs
- Forward Compatibility – any future style alterations or browser compatibility tweaks can easily be made from your skin.css file which will affect all of your pages, rather than manually editing all of your pages one at a time.
- Accessibility – Only adding content into the Text/HTML module will allow the content to be more easily accessible to screen readers, search engines etc.
To learn how to create classes in your skin.css file for styling the text and images within the Text/HTML module as we have outlined here, view this tutorial:
Styling text and images within the Text/HTML module using the skin.css file and the FCKEditor.
The tutorial in particular demonstrates how you can programme the FCKEditor to display a list of the classes you have created within your skin.css file. This enables you to easily select from a drop down list the class style that should be applied to your content. |
|
|