Content Management Systems

1
Content Management Systems
2
Agenda

• Week overview
• Web-page basics
• The why and what of CMS
• Typo3

3
This week

• Monday 9-12 Introduction to CMS, Typo3 basics
  and portfolio
• Tuesday 9-12 Typo3 basics
• Wednesday Portfolio implementation continued and
  reflection (without teacher).
• Thursday Portfolio implementation continued and
  reflection (without teacher).
• Friday 9-11 Presentation of portfolio, database
  and reflections week 36-37

4
Web-page basics
5
(No Transcript)
6
From server to browser
Browser interprets HTML files
Web server -Repository for files that can be
accessed by a web broser
Designer and programmer
7
Web-page basics

• XHTML extensible hypertext mark-up language
• Formatting text and screen layout
• References to other pages (links) and places
  non-text context fx pictures in a page
• XHTML only stores text (not pictures)
• Browsers interpret XHTML and renders the page we
  see
• No sharp distinction between form and content (or
  at least it used to be so for a long time)

8
From single pages to large(-r) web-sites

• Challenges
• Very large web-sites
• Many people contributing
• The ones with knowledge of the content lack
  technical insight and/or time deal with technical
  issues
• Need to serve many different platforms
• Need for a consistent design across large sites
• Need for different versions and different
  languages
• (interactivity)

9
From single pages to large web-sites

• Technological and organisational solutions
• Splitting form and content on the programming
  level (XHTML, CSS)
• Editors with template and reusable content
• The rise of the information architect
• (added interactivity through server-side
  programming asp, php, java, ...)

10
From single pages to large web-sites

• CMS a technical solution that provides new
  conditions for the organisation
• Decentralized maintenanceDesigned with
  non-technical content editors in mind
• Configurable access restrictions
• Consistency of design is preserved Navigation is
  automatically generatedContent is stored in a
  databaseDynamic content
• Daily updates (easy)
• Cooperation
• Content scheduling (produce today and set a later
  release day)
• Source www.typo3.org

11
CMS in principle

• CMS frontend
• Output for webbrowser
• User input

• CMS backend
• Content input
• Formatting
• Templates
• Search engine
• Core

Database
12
But what is content?

• Texts
• Pictures/photos
• Tables
• Menus
• Forms

13
CM Systems and reasons for not teaching them here

• Commercial (more or less closed systems very
  little continuous or community development,
  expensive)
• Sitecore
• Synkron Via
• Odeum
• Open source
• Typo3 complex, Typo3 specific programming
  language for templates
• Joomla a bit on the simple side, a fork of
  Mambo (continued development by other developers)
• Mambo a bit on the simple side, did the best
  developers leave with Joomla?

14
CM Systems and reasons for not teaching them here

• Commercial (more or less closed systems very
  little continuous or community development,
  expensive)
• Sitecore
• Synkron Via
• Odeum
• Open source
• Typo3 complex, Typo3 specific programming
  language for templates
• Joomla a bit on the simple side, a fork of
  Mambo (continued development by other developers)
• Mambo a bit on the simple side, did the best
  developers leave with Joomla?

15
Why Typo3?

• Build on general CMS principles what you learn
  transfers easily to other systems
• Open source you can go into an organization and
  if needed bring the entire package for free
• Handles small medium large web-sites
• Many free templates available
• Plugs in extra components
• Developed by a large and stable community (at the
  moment)

16

• Source Typo3.org

17
Lets have a closer look at it
18
Task today

• Play with Typo3
• Set up a new site
• Add pages and content
• Suggestion Play today and start all over tomorrow