120 likes | 230 Views
A Unified Content Strategy for ACM SIGGRAPH Chapters. Presented by Juan Pablo Di Lelle Vice Chairman Montreal Chapter. But… it’s not just about building a better web site. Improve the way we manage our content: Authoring Review Submission Translation Publication Repurposing.
E N D
A Unified Content Strategy forACM SIGGRAPH Chapters Presented by Juan Pablo Di Lelle Vice Chairman Montreal Chapter
But… it’s not just about building a better web site • Improve the way we manage our content: • Authoring • Review • Submission • Translation • Publication • Repurposing.
Why change this process? • Focus more on the information, less on the formatting • Efficiently maintain the look and feel of the content • Publish consistent content • Avoid doing the same work many times • Simplify the content authoring, submission, approval, publishing and maintenance process • We need a shorter publishing cycle
A unified content strategy • Separating content from format: • Authors are not required to spend hours formatting the content • The focus goes on information, meaning, and structure: the input (content) is independent of the output (media) • Structured content yields to: • Content unification regardless of the author • Content consistency • Content reuse.
A unified content strategy • Collaborating among authors • Sharing the content among authors makes the content consistent and reusable wherever it’s required • Authoring can be handled by more people if an easy content creation process is in place • I don’t want to do all the job by myself!
A unified content strategy • Avoid doing the same work several times. Better use of resources with: • Workflows • Automatic notification mechanism • A friendly authoring and publishing process • A faster time to publication • Increased quality and consistency.
What is a CMS? • There are hundreds of Open Source CMS • Different types of CMS: • Transactional CMS (e-commerce transactions, money exchange, e-catalogs, etc.) • Integrated Document CMS • Publication CMS • Learning CMS • Web CMS • Enterprise CMS (a web CMS + management of other type of content).
CMS vs. Databases • CMS use a database but provides much more: • Predefined repository • Content relationship • Built-in reports • Simplified creation of metadata • Pre-configured system triggers • Version control • Access control • Integration with authoring tools • Workflow
And the winner is… • Plone • Emphasis on a flexible and robust foundation • Emphasis on workflows and security • Very easy to install • Very easy to use • Very easy to manage • Very easy to customize • Huge community support.