Embed Size (px)
Citation preview
XHTMLPresenters :
Jarkko Lunnas
Sakari Laaksonen
Contents
INTRODUCTION
XHTML 1.0
•Why XHTML?•XHTML vs. HTML •Declarations•Differencies in declarations•Validating XHTML
XHTML - Introduction
What are CMSs ideal for?•CMSs are for managing larger scale publications which are hard to control and manage
•Used for publishing same content in different publications
CMSs (in web) – What are CMSs
Categorizing CMSs
Enterprise Management Systems / EMSs: Stores and manages organization’s e-publications, documentation and Web content so that the employee of the company can reuse the information across different applications.Web Content Management Systems / WCM systems: •The main focus of the system is to publish content in the Internet environment•The system repositories lie on web server•Managed with browser-based tools
CMSs (in web) – What are CMSs
Categorizing CMSs
Open source (free):
Ez Publish http://ez.no/PHP-Nuke http://www.phpnuke.org/Mambo server http://www.mamboserver.com/
Commercial CMSs:Crasmanager http://www.crasmanager.fiNavigo CMS http://www.ch5finland.com
CMSs (in web) – What are CMSs
What CMS provides?• Main purpose; to provide solid control over the content and publications, to be able to publish same content in different publications
• Role of CMS for clients; makes possible to maintain the sites without knowing actual code-languages
• For developers; To provide a structured and easy to use framework for further development
CMSs (in web) – What are CMSs
Main principles• Rendering format needs to be separated from the actual content and metadata
• Content needs to be separated to components and stored in a hierarchial structure
Content managing is all about relating components to each other
CMSs (in web) – Principles and logical design
<PRODUCTS> <PRODUCT> <ID>11007</ID> <NAME>Cardboard Cup Sleeve</NAME> <PRICE>$00.02</PRICE> <DESCRIPTION>
Available in brown, white, and green. </DESCRIPTION> <PICTURE>/images/cupsleeve.jpg</PICTURE> </PRODUCT> <PRODUCT> <ID>11008</ID> <NAME>Cardboard Elvis</NAME> . . </PRODUCT></PRODUCTS>
Components
Information content componentsAll the content needs to be separated into smaller chunks of information.
CMSs (in web) – Principles and logical design
StructuringHierarchies (TOC)IndexesCross referencesSequences
CMSs (in web) – Principles and logical design
Structuring“Control the structure and you control the content and its publications”
CMS access structure• Inside the CMS; for management• Outside; for navigation
Publication access structure• Set of access structures that relate the parts inside the publication and let’s you know what’s inside the publication
CMSs (in web) – Principles and logical design
Templates• Basic templates shouldn’t require
any programming skills
Template process:1. create a standard page, that all the other pages
follow2. replace all the particulars (that will differ
between pages) with placeholders3. template processor replaces the placeholders
with the particulars they address per page
- own syntax can be added as well
CMSs (in web) – Principles and logical design
<HTML> <HEAD>[Insert Title]</HEAD> <BODY>[Insert Body]</BODY></HTML>
Templates
Main template types• Page templates • Navigation templates • Component templates
CMSs (in web) – Principles and logical design
Programming, use of mark-up languages and databases
Open programming standards: Object-oriented programming
Programmed components use from and stores the data (the given attributes) to a relational database or to an XML file
CMSs (in web) – Principles and logical design
Repository “the heart of the management system”
Storage for components from where they can be continually managed to increase the quality of their metadata or content
Content databasesContent databases such as relational databases and XML Object databases, not necessarily mutually exclusive
Content media filesApart from a database as separate files
Control and configuration filesTemplates, metadata lists & indexes, scripts, workflow rules etc.
CMSs (in web) – CMS areas and workflow principles
Main workphases
• Collect• Manage• Publish
CMSs (in web) – CMS areas and workflow principles
Workflow system
Goal is to make complex tasks as easy as possible for the user to carry out
• layered functionality• triggering• archiving• backup processes• connection management processes
CMSs (in web) – CMS areas and workflow principles
The publishing system
Repository -> Content -> Templates -> Publications
Web publication process1. Loads a template. 2. Pass any parameters that came along
the request3. Execute code in template to produce
the finished page4. Pass finished page to web server for
display to user’s browser
CMSs (in web) – CMS areas and workflow principles
Administration system
• sets parameters and takes care of the structure of CMS
• includes staff configuration, metatorial and system configuration
CMSs (in web) – CMS areas and workflow principles
CMS Demonstration
CMSs (in web) – CMS demonstration
• Crasmanager 4.1
Additional business values through CMSs• Hosting deals
• Efficient re-use of resources• More focused component and
system development
• Savings in providing correct up-to-date info
• …
CMSs (in web) – Additional business values
Future scopes• The content management market is huge
and growing day by day
• CMS features are expected to become more standardized
• CMS field is maturing all the time to have higher level of consistency, repeatability and professionalism
• Content managing will extend its scope more and more to hypermedia, software engineering, marketing and business process design and such
CMSs (in web) – Future scopes
Sources
• BooksContent Management Bible, by Bob Boiko
• CompaniesCrasman Company Ltd.
• InternetContent Management Tutorial @ http://chalaki.com
CMSs (in web) – Sources
