Content Management systems
Upcoming SlideShare
Loading in...5
×

Like this? Share it with your network

Share
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
    Be the first to like this
No Downloads

Views

Total Views
2,009
On Slideshare
2,008
From Embeds
1
Number of Embeds
1

Actions

Shares
Downloads
52
Comments
0
Likes
0

Embeds 1

http://www.slideshare.net 1

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
    No notes for slide

Transcript

  • 1. Content Management Systems
      • Module 1: Main Concepts on Content Management
      • < [email_address] >
  • 2. CMS – Module 1 Main concepts on Content Management
    • Session index:
      • CMS main characteristics
      • Model – View – Controller ( MVC )
      • The Content Tree and Information Systems
      • Different architectural basis
      • Free Software CMS Platforms
      • Phases in development with CMS
  • 3. CMS – Module 1 Main concepts on Content Management
    • 1. CMS main characteristics
      • Needs of complex projects of providing solutions to typical problems in web scenarios.
      • Standard bundled features:
        • Contents access control, user management.
        • URL management and navigation tools.
        • Publication and revision tools, etc ...
      • Differences between Content Management Systems (CMS) and Content Management Frameworks (CMF).
      • Characteristics to be considered for comparing basic functionalities offered by the different CMSes:
        • Features, Extensibility, Support and Community system.
  • 4. CMS – Module 1 Main concepts on Content Management
    • 2. Model-View-Controller structure.
      • Web approach to MVC design pattern.
      • Separation between contents and presentation layers allows the exportation of data to several interfaces:
        • Web sites with different data access requirements (corporative sites, Intranet , shareholders, etc )
        • Information repositories with documentary storage purposes
        • Exportation or printed version of contents
      • Ease of reutilization and graphical redesign of contents
      • Separation of templates and sub templates in HTML presentation layers of implied lists
  • 5. CMS – Module 1 Main concepts on Content Management
    • 3. The Content Tree and Information Systems.
      • We understand as content every single information unit in the system:
        • Standard contents: Articles, Images, Files, News, Newsletters, Forum posts
        • Access components or Services
      • All these tools have a common orientation: The Content Tree or Information System.
      • The development of a Content Management System should cover a more ambitious goal than the single project being developed.
      • Hierarchical template systems for the implementation of look and feel for the contents.
        • Orientation of interface structures or layouts .
  • 6. CMS – Module 1 Main concepts on Content Management
    • 4. Different architectural proposals:
      • LAMP environments ( Linux – Apache – MySQL – PHP )
        • Variations about database servers: Postgress SQL, Oracle.
        • Multi platform related to the operating system ( WAMP )
      • Java-based environments ( J2EE – Tomcat / IIS )
      • Other Alternatives ( Phython, Ruby on Rails, AJAX + XLS, .NET, PERL, ... )
  • 7. CMS – Module 1 Main concepts on Content Management
    • 5. Free Software CMS
      • Huge set of interesting different alternatives in continuous evolution. Very expensive to keep updated.
      • Quite reliable information based on comparison webs.
        • http://www.cmsmatrix.com
        • http:// www.opensourcecms.com
      • Anyway, the only secure way of evaluating CMS is the development of real projects.
      • Different learning curves and possibilities of future evolution of developed web sites.
      • Several organizational structures within the community
  • 8. CMS – Module 1 Main concepts on Content Management
      • Several remarkable LAMP alternatives ( among other ) :
        • Typo3 http://typo3.org
        • Joomla! http://joomla.org
        • eZPublish http://ez.no
        • Drupal http://drupal.org
        • Xoops http://www.xoops.org
        • Mambo http://mambo-foundation.org
  • 9. CMS – Module 1 Main concepts on Content Management
      • Java alternatives:
        • OpenCMS http://www.opencms.org
        • Apache Lenya http://lenya.apache.org
      • Python alternative:
        • Plone CMS http://plone.org
      • Other interesting variations oriented to specific purposes would be tools like Sherpa CMS ( XML + XSL ) or wordpress ( PHP )
        • http://sherpacms.com
        • http://wordpress.com
  • 10. CMS – Module 1 Main concepts on Content Management
    • Other complementary tools in CMS web projects:
      • Integration and/or component adaptation with specific functionalities:
        • E-learning platforms: Moodle
          • http://moodle.org
        • Tools with collaborative components: Egroupware
          • http://www.egroupware.org
      • Several authentication systems:
        • Weak integration: Authentication through Single Sign On and services access by IFRAMES or controller extensions
        • Strong integration: Adapted developments using internal interfaces of tools or adapting their own code
  • 11. CMS – Module 1 Main concepts on Content Management
    • 6. Phases on web development using CMS tools
      • Scope specification and strategic proposal of the project
      • Requirement elaboration and Information System definition
      • Analysis of services to be developed and content architecture
      • Web site graphical prototype design
      • Graphical structure deploy in the Content Tree
      • Specified Use Cases development.
      • Graphical structure deploy to developed Use Cases
  • 12. CMS – Module 1 A practical example: ByGalicia
    • A practical example: ByGalicia project
      • Scope specification and strategic proposal of the project
        • ByGalicia project target and medium, long and short term goals.
      • Requirement elaboration and Information System definition
        • User profiles, shared information channels, accessibility requirements, communication needs.
      • Analysis of services to be developed and content architecture
        • Service stack generation and an initial Content Tree. Entity labeling of contents to be used in the project
  • 13. CMS – Module 1 A practical example: ByGalicia
      • Web site graphical prototype design:
        • Static prototypes from images provided by design partner
      • Graphical structure deploy in the Content Tree:
        • Development and integration environments installation
        • HTML translation of static proposals and Page Structure construction
      • Specified Use Cases development:
        • Implementation of needed functionalities as new extensions, evolution of existing components or integration with other services
  • 14. CMS – Module 1 A practical example: ByGalicia
      • Graphical structure deploy to developed Use Cases:
        • Modification of subtemplates or stylesheets of web site components
      • Graphical structure deploy to developed Use Cases:
        • Tests, validation and publication.
  • 15. CMS – Module 1 A practical example: ByGalicia
    • Focusing on design integration phase, from HTML static files, we will do the next tasks:
      • Divide the layout in dynamic components for each content.
      • Move all presentation features to CSS to keep structure independent.
      • Each identified block is set to the controller to the content area defined.
      • Successive build of standard templates or layouts
  • 16. CMS – Module 1 A practical example: ByGalicia
  • 17. CMS – Module 1 A practical example: ByGalicia
      • We will probably need several templates for the web site, depending on the content presentation structure in each case:
        • Section specific frontpages
        • Content sections with different structures
        • Special areas for contents with a particular presentation
        • Authentication areas and error messages
        • Floating windows
        • etc
  • 18. CMS – Module 1 A practical example: ByGalicia