Table of Contents
- Introduction
- Hierarchical "Tour"
- Introductory
- Level 01: Nested "Non-Place-able" Elements
- Level 02: "Non-Place-able" Elements
- Level 03: "Place-able" Elements
- Level 04: Module Type ('mt2col_top') Zones and Positions
- Level 05: Page Layout Zones and Positions, and Modules
- Level 06: Page Layout Zones: Header, Body, Footer; Zone-holding Zones; Module-holding Zones
- Level 07: Page Layout '05'; Page Layout <table>s; CSS Margins
- Sitemap
- Navigation
- Site Pages
- Modules (Page Components, or "Fragments")
- Buildlist
- Content Types
- "ML"s ("Markup Languages")
- DTDs (Document Type Definitions)
- Elements
- Element-Zone Assignments (EZA)
- XSLT Pipeline
The concepts addressed in this chapter are presented in a (largely) top-down sequence.
To begin, from Site, to Page, to Module:
the outermost Sitemap; the site sections (vertical) and levels (horizontal); the structure of named directories that implements the map; and the file-naming conventions derived from that;
down to the site Navigation required to move through the site and that directory structure;
then to the Pages found in the site, particularly their skeletal Page Layouts;
hence to the page fragments, or Modules which comprise each Page.
A digression to the Buildlist knits the last two topics together (which Modules go on which Page).
Then, before we can further descend hierarchically inside the Module to its fundamental building block (the "Element"), we need to learn about the nature of where these Elements come from:
the Content Type of a Module;
about the various Markup Languages used to process the Module from XML to HTML;
about the DTDs (Document Type Definitions) for each Markup Language
Next, descending to the Element level, come:
the Elements that make up the Document Type Definition, and especially the distinction between "Place-able" Elements and Non-Place-able ones.
This leads to the innovative mechanism developed for this system: the "EZA," or "Element-Zone Assignment." This is the Assignment of a particular Element (an element that can be "Placed") to a particular Zone (in essence, a particular <td> table cell in a Module). It is the "recipe" for putting a set of Module Elements into a particular presentation "rectangle" (page fragment, or component).
Finally, back at a "macro" level, the transformation processing:
a careful "Walk-Through" of the XSLT code used to process all of these artifacts, across the three transformations ("hops") from source XML through to site HTML.
Figure 3.1. A. Sitemap, Site Section, Page
A. Sitemap (and Nav One), Site Section (and Nav Two), Page
