Book uses the following script code as an example of how to draw a line.

page = PAGE
page.typenum = 0
page.20 = HRULER
page.20 {
   lineThickness = 10
   lineColor = #e6e6e6
   space:eft = 100
   spaceRight = 100
}

Starting to feel the symptoms of a panic attack.

Changed the Setup for the root template to the following.

	page = PAGE
	page {
	  10 = TEXT
	  10 {
	    value = NMPDR!
	  }
	}

This creates a page called page and puts a text object called 10 on it. The value of the text is NMPDR!. Still no clue how to get the real content onto the page. I believe the significance of 10 is that the page elements are ordered by name. The first element would be 10 and the second would be 20, and then if you need to put something in between it goes in position 15. I think the idea is to bring back memories of the line-numbering schemes used back in the days of punch cards. Expecting to have nightmares about this.

While looking for information in the book about the static templates, I accidentally find the on displaying content. Well, actually, it's not a section, it's a paragraph buried in the middle of a list of object types. The following code fragment displays content on the page. The colPos value of 0 indicates we want the content for the normal column. The other columns are left, right, and border, but I don't know which numbers they are.

    page = PAGE 
    page {
      stylesheet = fileadmin/NMPDR.css
      20 = CONTENT
      20.table = tt_content
      20.select {
        pidInList = this
        orderby = sorting
        where = colPos=0
     }
   }
   

Here is the code in the master template. In this case NMPDR.Version is a constant defined in the Constants section and contains the NMPDR version number. The following code replaces every occurrence of ###VERSION### in the content with the current version number as defined in the constants.

	constants.VERSION = {$NMPDR.Version}
	page = PAGE 
	page {
	  stylesheet = fileadmin/NMPDR.css
	  20 = CONTENT
	  20.table = tt_content
	  20.select {
	    pidInList = this
	     orderby = sorting
        where = colPos=0
	 }
	 20.parsefunc {
	    constants = 1
	 }
	}

The first line tells the script that VERSION will be used as a marker in the text. The next two lines state that we're building a page. We then define the style sheet to be fileadmin/NMPDR.css. The next three lines tell us that we want to use page content entered by the authors. The select block (four lines) states that we want the content from this page (pidInList = this), in the proper order (orderby = sorting), for the normal column (colPos = 0).

The parsefunc tells the script to parse all the text we've stuffed into element 20, and to use the defined constants (constants = 1).

Okay, a CARRAY is actually a COA object. Here is the code that inserts the stylesheet link into each page.

	  headerData = COA
	  headerData {
	     10 = HTML
	     10.value = <link rel="stylesheet" type="text/css" href="{$NMPDR.URL}/fileadmin/{$NMPDR.Style}" />
	  }

This occurs inside the page block. The COA type defines an array. The array has a single element named 10 that is the raw HTML for the stylesheet link. I used constants for both the name of the style sheet and the base URL. If I have a lower-level template, all it needs in order to use a different style sheet is change NMPDR.style in the constants section to the name of the new sheet. This is an excellent example of how powerful Typo3 can be if you have a great deal of time and luck at your disposal. Along the way, I discovered this page which I believe will prove useful.

We have ignition! The following fragment puts the banner at the top.

	constants.VERSION = {$NMPDR.Version}
	constants.SITE = {$NMPDR.URL}
	constants.SPROUT = {$NMPDR.Sprout}
	page = PAGE 
	page {
	  headerData = COA
	  headerData {
	    10 = HTML
	    10.value = <link rel="stylesheet" type="text/css" href="{$NMPDR.URL}/fileadmin/{$NMPDR.Style}" />
	  }
	  20 = CONTENT
	  20.table = tt_content
	  20.select {
	    pidInList = this,3
	    orderBy = sorting
	    colPos = 0
	  }
	  20.parsefunc {
	    constants = 1
	  }
	}

In order to make this work, I had to manually edit the database to set the sorting value for the banner element to 0. There has got to be a better way to do that. In any case, the pidInList tells the script to take all content elements from page 3 (the banner page) plus the current page. The next step is to create the image map used for the banner on the main site.