Whenever I see review CMS-features I always ask myself: Is this something my customer is capable of using - without messing everything up? So I ask you: when should the UI allow the content-editor to do something, and when should it not allow Mr. Marketing or Mrs. Secretary to do something?
Let's start with an obvious one: Almost all of us agree that a normal content-editor should neither install modules nor skins. They don't understand the security issues, it could kill the system and they may never know when they break something.
So let's look at the more controversial issues. Image-Handling, Module-Configuration or Installing Apps without Security risks.
One of my favorite is image-handling
Here's the HISTORICAL DNN-Way
The default DNN-way gives the content-editor a lot of power and responsibilities:
- The content-editor uploads images. The DNN-way requires that you must train your customer in
- image-formats (no, BMP shouldn't be uploaded and PDF is not an image...)
- CSS-classes (please use this class to float, and that for the border)
- compression and sizes (no! don't upload a 3MB picture, and bigger than 100x100)
- that dpi has nothing to do with the pixels on the screen
- The content-editor fiddles with the images after uploading - again you must train your customer to
- use the crop/resize tools
- file naming and placement
- understand difference between thumbnailing and "resizing"
- The content-editor places the image within some HTML - again requiring training for...
- what HTML is
- table and CSS-placements
- image-pixels (make it 200x300 for that page, and if you want to float, then...)
- basics of responsive design
- why squishing the image is really easy, and why you shouldn't do it
- If the design is retina / high-res optimized - you need more training for...
- tricks on retina-optimizations
- training to provide images larger than needed - again with the compression to consider
the way I recommend it
We (2sic) have seen so many web sites destroyed by customers filling in content. And even though they messed it up, it wasn't their mistake: the tool made them do it. So after may years we choose to change it. Our recommendations:
- The content-editor should NOT worry about file-size, image-size, placement on the page. Retina, CSS and cropping should also not be part of his repertoire. The content-editor is usually not very good at this and should not need training in these topics - the CMS should do this automatically based on the Web-Designers pre-configuration
- The content-editor should just upload the image way too big - the system will take care of the rest
- The content-editor MUST choose which layout he wants (image right, left, slider etc.) but not how to do this.
How can we do this?
- Disable almost all functionality of the WYSIWYG - especially inserting images.
- Provide pre-designed, intelligent templates which take care of image-placement, image-proportions, retina-optimizations, resizing/thumbnailing, etc.
Want to see some examples? Just install the module 2sxc - the default templates will do all this (except for the retina-optimizations). You can achieve similar results with many other modules - assuming they provide a templating system.
Agree/disagree? Got a better suggestion?
With love from Switzerland,
Daniel Mettler grew up in the jungles of Indonesia and is founder and CEO of 2sic internet solutions in Switzerland and Liechtenstein, an 20-head web specialist with over 600 DNN projects since 1999. He is also chief architect of 2sxc (2SexyContent - see forge), an open source module for creating attractive content and DNN Apps.