1. 1 Copyright(c) 1997-2001. Dave Krupinski. All rights reserved. Webgenz and Content Management An introduction to using Webgenz to develop and maintain web sites

2. 2 Copyright(c) 1997-2001. Dave Krupinski. All rights reserved. Introduction to Content Management Goals of Content Management –Content Reuse No duplication of content –Abstraction of page design from content Maintain page design independently from content –Workflow automation Support for content production process

3. 3 Copyright(c) 1997-2001. Dave Krupinski. All rights reserved. What is Content Reuse? No duplication of content –The same content may appear in multiple places on the site, but it should be managed in one place. No duplication of HTML code or JavaScript –Frequently used HTML code, JavaScript, ASP, etc. should be maintained in a single place.

4. 4 Copyright(c) 1997-2001. Dave Krupinski. All rights reserved. Why Abstract Page Design From Content? Web site designs change often –Global design changes should be possible by making a change in one place, not every page. Consistency –Centralized maintenance of page design enforces consistency.

5. 5 Copyright(c) 1997-2001. Dave Krupinski. All rights reserved. What is Workflow Automation? Content production is collaborative and inter-departmental –Writers, editors, product managers, legal departments, etc. are all involved in the content production process. –Content Management solutions automate the workflow process.

6. 6 Copyright(c) 1997-2001. Dave Krupinski. All rights reserved. Webgenz is a object-oriented content management system that generates web pages from reusable templates and content macros. Introducing Webgenz

7. 7 Copyright(c) 1997-2001. Dave Krupinski. All rights reserved. How Webgenz Supports Content Management Content Reuse –Any content (HTML, JavaScript, ASP, etc.) can be defined as a Webgenz Macro and reused throughout a web site. Abstraction of Page Design from Content –Page design and layout are defined in Webgenz Templates. Templates are used to apply a design to one or more pages in a web site. Changes to a Template automatically appear in all web pages that use the Template. Workflow Automation –Basic workflow support is provided by the use of Webgenz Filters.

8. 8 Copyright(c) 1997-2001. Dave Krupinski. All rights reserved. Webgenz Macros Macros define reusable content Macros are defined in Webgenz Content Files Example Macro definitions in a Content File:

9. 9 Copyright(c) 1997-2001. Dave Krupinski. All rights reserved. Webgenz Templates Templates define page design and layout Example of a Template file:

10. 10 Copyright(c) 1997-2001. Dave Krupinski. All rights reserved. The Webgenz Generation Process Webgenz merges Templates and Macros to create web pages Generation is an off-line, “compile-time” process –Independent from the web server

11. 11 Copyright(c) 1997-2001. Dave Krupinski. All rights reserved. Webgenz and Object-Oriented Concepts Inheritance –Each web page is generated from a Template and one or more Content Files. The Content Files are organized into a hierarchy so that Macros can be inherited or shared between a specific group of web page or across all web pages. Subclassing –Inherited Macros can be redefined or extended by Macros further down the inheritance hierarchy.

12. 12 Copyright(c) 1997-2001. Dave Krupinski. All rights reserved. Putting It All Together: The Webgenz Project Webgenz Project Folders Web Page Content Files with Macros Template Web Page A Webgenz Project organizes the Templates and Content Files used in a web site.