New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

The Community Blog is a personal opinion of community members and by no means the official standpoint of DNN Corp or DNN Platform. This is a place to express personal thoughts about DNNPlatform, the community and its ecosystem. Do you have useful information that you would like to share with the DNN Community in a featured article or blog? If so, please contact .

The use of the Community Blog is covered by our Community Blog Guidelines - please read before commenting or posting.

Designed Content 1.1 - Understanding Beautiful Content

A lot of web sites have terrible looking, non-responsive, non-retina content. This is very common when non-designers (including programmers) manage the content - which is the core goal of a CMS. Let's change this once and for all!

This is the intro of my first series about beautiful content, in which I define what it's all about, the goals and ensure we're all on the same page. 

What is it about?

So when we talk about beautiful content, it's important that we're using the same terms and ideas before we start. So the goal is…

The web designer can empower the content editor, to easily and faultlessly manage content on a live web site, in as many languages as necessary, targeting current devices with minimal time and cost for both designer and editor. And both web designer and content-editors must easily re-use the content and apply changes when the future hits us with new devices, new requirements and new visualizations.

What does this mean?

  1. Web Designer: This is a person with HTML/CSS and maybe Razor know-how who is in charge of preparing the web site for the layman editor. The web designer knows image formats and sizes, understands mobile-design and retina-resolution images and can usually copy something existing and customize it to the customers needs.
  2. Empower: The web designer should not be required to add/edit images, texts, image galleries or any other normal content. So it's very important to work in such a way, that the content editor can work on his own.
  3. Content Editor: This role/person is in charge of content. They are under time pressure but have an idea of the text and pictures they want to add. They are usually neither web nor graphics designers and "just want to get the job done" as effortlessly as possible. They don't understand design, so if they f***-up, they won't know that they did and will save it anyhow. Their needs are simplicity and automatic-beauty.
    Even though the content-editor is not good at design, he still has some needs for trying different layouts.
  4. Content: Content is a wide assortment of text and media which only becomes meaningful in a specific arrangement on screen. Content is NOT data, so it should never feel like you have to edit a data-table when managing it. Content has very specific - constantly changing - needs to manage it - like handling file references and similar.
  5. Live Web Site: Most web sites are live, and changes are on the same system as almost nobody has time or resources to manage a separate staging system. We must always keep this in mind when we (the web pros) give the content-editors tools to work with.
  6. Many Languages: I used to think the Americans never need multilanguage because they didn't seem to care - while we Swiss always ask that when we evaluate a module. I was wrong. All web agencies I met in the states have ML web sites and fight with the same i18n (internationalization) issues like we do. And i18n is very complex - especially when you want to simplify content-lifecycle, so not just the first-time entry, but also future changes across languages.
  7. Minimal time and cost: Both web designers and content editors have a constant time pressure. And IT should help us get our jobs done ASAP.
  8. Re-use Content: Content is alive - and has a content-lifecycle. Because of this, it's often evil to copy content - because the copies won't get updated when the original content is modified. Because so product-summaries, addresses and must be re-usable in various displays and still be the same entity.
  9. The future hits us: Websites are moving targets - common changes in the future:
    1. new user devices require corrections in the HTML of EVERY link in the site
    2. changes in Google/SEO require corrections everywhere
    3. changes in the customer's needs (like a new customer-field linked to his customers in gallery images) require data and visualization changes

There is only one way to achieve this

 We must fully separate Content from the Presentation (the Template+ settings)! 

To do that, we need strategies and tools. This will be discussed in the next part.

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.


There are currently no comments, be the first to post one.

Comment Form

Only registered users may post comments.


Aderson Oliveira (22)
Alec Whittington (11)
Alessandra Davies (3)
Alex Shirley (10)
Andrew Hoefling (3)
Andrew Nurse (30)
Andy Tryba (1)
Anthony Glenwright (5)
Antonio Chagoury (28)
Ash Prasad (37)
Ben Schmidt (1)
Benjamin Hermann (25)
Benoit Sarton (9)
Beth Firebaugh (12)
Bill Walker (36)
Bob Kruger (5)
Bogdan Litescu (1)
Brian Dukes (2)
Brice Snow (1)
Bruce Chapman (20)
Bryan Andrews (1)
cathal connolly (55)
Charles Nurse (163)
Chris Hammond (213)
Chris Paterra (55)
Clint Patterson (108)
Cuong Dang (21)
Daniel Bartholomew (2)
Daniel Mettler (181)
Daniel Valadas (48)
Dave Buckner (2)
David Poindexter (12)
David Rodriguez (3)
Dennis Shiao (1)
Doug Howell (11)
Erik van Ballegoij (30)
Ernst Peter Tamminga (80)
Francisco Perez Andres (17)
Geoff Barlow (12)
George Alatrash (12)
Gifford Watkins (3)
Gilles Le Pigocher (3)
Ian Robinson (7)
Israel Martinez (17)
Jan Blomquist (2)
Jan Jonas (3)
Jaspreet Bhatia (1)
Jenni Merrifield (6)
Joe Brinkman (274)
John Mitchell (1)
Jon Henning (14)
Jonathan Sheely (4)
Jordan Coopersmith (1)
Joseph Craig (2)
Kan Ma (1)
Keivan Beigi (3)
Kelly Ford (4)
Ken Grierson (10)
Kevin Schreiner (6)
Leigh Pointer (31)
Lorraine Young (60)
Malik Khan (1)
Matt Rutledge (2)
Matthias Schlomann (16)
Mauricio Márquez (5)
Michael Doxsey (7)
Michael Tobisch (3)
Michael Washington (202)
Miguel Gatmaytan (3)
Mike Horton (19)
Mitchel Sellers (40)
Nathan Rover (3)
Navin V Nagiah (14)
Néstor Sánchez (31)
Nik Kalyani (14)
Oliver Hine (1)
Patricio F. Salinas (1)
Patrick Ryan (1)
Peter Donker (54)
Philip Beadle (135)
Philipp Becker (4)
Richard Dumas (22)
Robert J Collins (5)
Roger Selwyn (8)
Ruben Lopez (1)
Ryan Martinez (1)
Sacha Trauwaen (1)
Salar Golestanian (4)
Sanjay Mehrotra (9)
Scott McCulloch (1)
Scott Schlesier (11)
Scott Wilkinson (3)
Scott Willhite (97)
Sebastian Leupold (80)
Shaun Walker (237)
Shawn Mehaffie (17)
Stefan Cullmann (12)
Stefan Kamphuis (12)
Steve Fabian (31)
Steven Fisher (1)
Tony Henrich (3)
Torsten Weggen (3)
Tycho de Waard (4)
Vicenç Masanas (27)
Vincent Nguyen (3)
Vitaly Kozadayev (6)
Will Morgenweck (40)
Will Strohl (180)
William Severance (5)
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out