In this figure, moving "up" from Level 03 to Level 04, we see that the same objects that were noted as Place-able Elements above have now been used here to indicate where the "Positions" are located (within "Zones"). Thus we encounter the first "transition" as it were, from looking at Elements (Levels 03, 02, and 01), to now looking at where those Elements go in the parent "Module Type" (Level 04). In particular, where within a Zone within that Module Type (or "layout"), and where down within that Zone: what Position.

As can be seen from this snippet of code from an "EZA Recipe" (Element-Zone Assignment), the information for these assignments is recorded like so:

<elementZoneAssignments>
	<eza zone="A" position="1" elementName="date"/>
	<eza zone="A" position="2" elementName="header"/>
	<eza zone="B" position="1" elementName="subHeader"/>
	<eza zone="B" position="2" elementName="mentionedOrgs"/>
	<eza zone="C" position="1" elementName="summary"/>
</elementZoneAssignments>

Please note that the concept is to create a single recipe "treatment" per Content Type, for any given website build design. That is, here we have the "Press Release Summary: CT11," which, for this particular project, gets this kind of look, re: the placement of its significant elements. This one EZA Recipe is then used against all CT11 content instances on the website. On another, future website build, of a new design (but with the same content), you might choose a different recipe; you'd simply alter some of these "A," "B," and "C," and "1" and "2" choices, etc., to achieve a new look.

Tip

Just to address the question: Is it possible to have more than one Recipe for a Content Type on one website? Yes, without question, but you would then need to set up more ad hoc processing requirements to indicate which "special case" CT11 Modules were to get a different recipe. With the essentially recommended approach of a single recipe per content type, you can take advantage of simple wildcard processing: "All ct11*.xml get a particular EZA Recipe." The intent is to foster consistency as a "good thing" in terms of content display. But if you wanted one particular Press Release Summary (most recent, perhaps) to appear differently (say, on the /media/index.asp page), you'd have to set up a special single " <styler>" entry in the processing file (the Ant /mlnmdev/util/build.xml file). This would have to be updated each time (manually, until some automation might get introduced here) with the particular BusinessML filename to be processed that way. It would not be especially efficient, but you could certainly do it.

Module Type: 'mt2col_top'. The name given to the example Module Type is nearly self-describing: 'M'odule 'T'ype with '2' 'col'umns and a colspan on 'top.' See the Module Types section of this documentation for a graphical depiction of this and other Module Types.

You might also note that this figure (Level 04) does contain two further Modules here in the main body content part of the page, in addition to the highlighted three instances of 'mt2col_top.' These other Modules are both simple Module Type 'mt01' (one column), and they house (as will be seen highlighted in the figure below (Level 05) the plain text contents: "Recent Press Releases" and "Click here to see additional 2002 press releases."