Maintaining Design Integrity in a CMSSmart Implementation Techniques (10/2/2010 @1:30pm)

Patrick Renner, Engage

Ego Trip

Patrick RennerProject Manager @ EngageBook Author

prenner@engagesoftware.com314-884-2435

A Practical Approach to DNNTopics: content strategy | designing content management and not just installing a system | extensibility isn’t just features | approach and practical implementation | avoiding features glut

Design Complexity / FlexibilityTopics: a balancing act | designs aren’t limited by a CMS | everything isn’t managed content

Content GardeningTopics: trees, shrubs, perennials, annuals, fresh-cut flowers | how much TLC does each require?

Content as Task (not a feature)Topics: evaluating pane layouts | approach content as a task and the install in ways to alleviate this burden

Be PrescriptiveTopics: Provide legends throughout your pages | provide content templates | name modules for what they should do

Cut the ClutterTopics: modules list | usability settings | clearing out the Rich Text Editor’s Toolbar

WYSIWYGTopics: Providing code snippets and a tailored set of paragraph blocks

Meaningful OrganizationTopics: Naming conventions for the file system | Name of your panes meaningfully

Writing for the WebTopics: Training and handoff |

Contributors need Tour GuidesTopics: Provide a style guide

SkinningTopics: Default panes, administrative menus

Ego Trip

Patrick RennerProject Manager @ EngageBook Author

prenner@engagesoftware.com314-884-2435