Press Releases

Press Releases
Prev	Chapter 2. Task-Oriented	Next

Add New Press Release

Obtain final press release (MS-Word .DOC).

Q. Appears on Home Page (y/n)? (/index.asp) (ct14)

Need "HPHShort" element ("Home Page Highlight Short Language")

	Note
	The "Short Language" needs to be quite brief indeed (see home page of live site http://www.millennium.com). In particular, of two HPHs (Home Page Highlights), only one may be permitted to word-wrap. See screenshot of them both word-wrapping (not permitted).

Q. Appears on "Recent Press Releases" page (y/n)? (/media/news/index.asp) (ct11)
Appears on Year (2002) Page (YES). (ct12)
Appears on Full Press Release Page (YES). (ct10)

Table 2.1. Press Release Links

Home Page "Highlights"	"Recent Press Releases" Page

Word-2-BML (Manual Edits)
- Edit Word .DOC into BusinessML for Content Type "Press Release" (ct10)
  Note
  This step is not part of the overall "XML-2-HTML" system.
  Tip
  Use a plain text editor to paste into from copying out of MS-Word, prior to pasting into the BusinessML file.
  Figure 2.1. MS-Word .DOC for Press Release
  Figure 2.2. CT10 BusinessML (in XML Spy)
- As an example to work from and edit (File | Save As...) you can use either a recent press release (e.g. ct10_pr-2002-12-16-0.xml), or a ct10 "skeleton" template you might create for the purpose.
/BusinessML/ct10_pr-2002-12-09-1.xml
Naming Convention
- ct10 = Content Type 10
- pr = Press Release
- 2002-12-09 = Year (yyyy) - Month - Date
- -0 = first press release that date; -1 = second; -2 = third (zero-based)

	Note
This step is not part of the overall "XML-2-HTML" system.

	Tip
Use a plain text editor to paste into from copying out of MS-Word, prior to pasting into the BusinessML file.

Add To BuildList

Lookup: get URL (path) to recent Press Release
Figure 2.3. Path to recent Press Release, for use in BuildList lookup
Copy the relative path of a recent press release, to use as the Lookup in the Buildlist.
Lookup: find in /util/buildlist.xml
Figure 2.4. Location in buildlist.xml of recent press release
Use editor's find command to locate the buildlist.xml entry for a recent press release.

Create New BuildList Entry

Copy the entire buildlist entry (from <page> to </page> inclusive), and paste in; then edit as described below:

									OLDER PRESS RELEASE 
	<page>
		<path>/media/news/2002/2002-12-11-0.asp</path> 
			<layout>pl05.html</layout> 
			<title>Millennium | Media | Press Releases | 2002 | 2002-12-11</title>   
	... 
	<mza position="b_ma_co_co1_a">
		<moduleinstance> 
			<instancename>ct10_pr-2002-12-11-0.html</instancename>   
		</moduleinstance> 
	</mza>

	Older, existing press release `path`.
	Older, existing press release `title`.
	Older, existing press release `instancename` for this module (assigned to zone position `b_ma_co_co1_a`).

									NEWER PRESS RELEASE 
	<page>
		<path>/media/news/2002/2002-12-16-0.asp</path>  
		<layout>pl05.html</layout> 
		<title>Millennium | Media | Press Releases | 2002 | 2002-12-16</title>   
		... 
		<mza position="b_ma_co_co1_a">
			<moduleinstance> 
				<instancename>ct10_pr-2002-12-16-0.html</instancename>   
			</moduleinstance> 
		</mza>

	NEW press release `path` - edit the `11` to `16`.
	NEW press release `title` - edit the `11` to `16`.
	NEW press release `instancename` for this module (also assigned to zone position `b_ma_co_co1_a`).

Add "Recent Press Releases" Buildlist Entry (if applicable)

Lookup (in buildlist.xml): find the appropriate page (/media/news/index.asp)

									RECENT PRESS RELEASES - ORIGINAL (prior to editing) 
	<page> 
		<path>/media/news/index.asp</path>
		<layout>pl05.html</layout> 
		<title>Millennium | Media | Press Releases</title> 
		... 
		<mza position="b_ma_co_co1_a">  
			<moduleinstance>
				<instancename>ct01_1med_press-releases_headline.html</instancename>
			</moduleinstance> 
		</mza> 
		<mza position="b_ma_co_co1_b">  
			<moduleinstance>
				<instancename>ct11_pr-2002-12-11-0.html</instancename> 
			</moduleinstance> 
		</mza> 
		<mza position="b_ma_co_co1_c"> 
			<moduleinstance>
				<instancename>ct11_pr-2002-12-09-1.html</instancename>
			</moduleinstance> 
		</mza> 
		<mza position="b_ma_co_co1_d"> 
			<moduleinstance>
				<instancename>ct11_pr-2002-12-09-0.html</instancename> 
			</moduleinstance> 
		</mza> 
		<mza position="b_ma_co_co1_e"> 
			<moduleinstance>
				<instancename>ct01_1med_press-releases_bottomline.html</instancename>
			</moduleinstance> 
		</mza>

	Note ordered positioning of stacked modules ('a', 'b', etc.). The first stacked module is the "headline"; the last is the "bottomline". In between can be as many or as few as you like of "Recent Press Releases" (manually controlled reverse chronological order).
	Position 'b'
	Copy and paste or otherwise edit this most recent entry to become the NEW most recent entry (see below for revised code for this section).
	You will usually want to prune off the oldest press release. Be sure to re-letter the "bottomline" if applicable (making 'e' to 'd' for example, or, depending, making 'e' to 'f', if you are keeping more press releases on the page). See edited version of this code below.

									RECENT PRESS RELEASES - REVISED (after editing) 
	<page> 
		<path>/media/news/index.asp</path>
		<layout>pl05.html</layout> 
		<title>Millennium | Media | Press Releases</title> 
		... 
		<mza position="b_ma_co_co1_a">  
			<moduleinstance>
				<instancename>ct01_1med_press-releases_headline.html</instancename>
			</moduleinstance> 
		</mza> 
		<mza position="b_ma_co_co1_b">  
			<moduleinstance>
				<instancename>ct11_pr-2002-12-18-0.html</instancename>   
			</moduleinstance> 
		</mza> 
		<mza position="b_ma_co_co1_c">   
			<moduleinstance>
				<instancename>ct11_pr-2002-12-11-0.html</instancename>   
			</moduleinstance> 
		</mza> 
		<mza position="b_ma_co_co1_d">
			<moduleinstance> 
				<instancename>ct11_pr-2002-12-09-1.html</instancename> 
			lt;/moduleinstance>
		</mza> 
		<mza position="b_ma_co_co1_e"> 
			<moduleinstance>
				<instancename>ct11_pr-2002-12-09-0.html</instancename>
			</moduleinstance> 
		</mza> 
		<mza position="b_ma_co_co1_f"> 
			<moduleinstance>
				<instancename>ct01_1med_press-releases_bottomline.html</instancename> 
			</moduleinstance> 
		</mza>

	The first stacked module ("headline") is unchanged - always 'a'.
	Position 'b'
	This "first" entry (for actual press release modules) has been edited to become our NEW press release (2002-12-18-0).
	Position 'c'
	This entry has effectively been moved down.
	Usually, you will want to prune off the oldest press release. In this example, we decided to keep all the original press releases, so our "bottom" became 'f' (from 'e'). See original version of this code above.

Add "Home Page Highlights" Buildlist Entry (if applicable)

Lookup (in buildlist.xml): find the appropriate page (>/index.asp)

Figure 2.5. "Root" index page Path, for use in BuildList lookup

Browser URL "Address" showing "root" index.asp
path.

Search for the /index.asp page.

	Tip
	Search on the string '`>/index.asp`', to be led to the correct ("root") index.asp. [There are many other index.asp pages (e.g. `/media/index.asp`, etc.) that would match a `find` on simply '`/index.asp`'.]

									HOME PAGE HIGHLIGHTS - ORIGINAL (prior to editing) 
		<mza position="b_ma_co_co1_a">  
			<moduleinstance>
				<instancename>ct01_home-pghdr.html</instancename>   
			</moduleinstance> 
		</mza> 
		<mza position="b_ma_co_co1_b">
			<moduleinstance> 
				<instancename>ct01_home-body.html</instancename> 
			</moduleinstance> 
		</mza> 
		<mza position="b_ma_co_co1_c">  
			<moduleinstance>
				<instancename>ct14_pr-2002-12-09-1.html</instancename>   
			</moduleinstance> 
		</mza> 
		<mza position="b_ma_co_co1_d">   
			<moduleinstance>
				<instancename>ct14_pr-2002-12-09-0.html</instancename>   
			</moduleinstance> 
		</mza> 
	</mzas>
</page>

	The first (and second) stacked modules ("pghdr" and "body") are unchanged - always 'a' and 'b'.
	The unchanging "Page Header" goes here, 'a' - (next position down ('b') is the also unchanging "Page Body").
	The second module ("body") is always at 'b'.
	Position 'c' always for the first entry.
	The first entry (for actual "home page highlights") goes here .
	Position 'd' always for the second entry.
	This second entry (of two) goes here .

									HOME PAGE HIGHLIGHTS - REVISED (after editing) 
		<mza position="b_ma_co_co1_a"> 
			<moduleinstance> <instancename>ct01_home-pghdr.html</instancename>   
			</moduleinstance> 
		</mza> 
		<mza position="b_ma_co_co1_b">
			<moduleinstance> 
				<instancename>ct01_home-body.html</instancename>   
			</moduleinstance> 
		</mza> 
		<mza position="b_ma_co_co1_c">   
			<moduleinstance>
				<instancename>ct14_pr-2002-12-18-0.html</instancename>   
			</moduleinstance> 
		</mza> 
		<mza position="b_ma_co_co1_d">   
			<moduleinstance>
				<instancename>ct14_pr-2002-12-09-1.html</instancename>   
			</moduleinstance> 
		</mza>
	</mzas> 
</page>

	As before, the first (and second) stacked modules ("pghdr" and "body") are (still) unchanged - always 'a' and 'b'.
	As before, the unchanging "Page Header" goes here, 'a' - (next position down ('b') is the also unchanging "Page Body").
	The second module ("body") is always at 'b'.
	Position 'c' always for the first entry.
	NEW: The first entry has now been edited to our NEW Home Page Highlight, for 2002-12-18-0 .
	Position 'd' always for the second entry.
	MODIFIED: The second entry (2002-12-9-1) has effectively been moved down from position one to position two (the one that was in position two has been effectively removed).

Table 2.2. Press Release Links - Revisited, After Edits

Home Page "Highlights"	"Recent Press Releases" Page
Successful edit of adding a new "Home Page Highlight," with one Highlight having word-wrap, but not both.	Successful edit of adding a new "Recent Press Releases" page entry. Earlier press releases were moved down, or off this page.
Unsuccessful edit of adding a new "Home Page Highlight," as both Highlights are long enough to require word-wrap, which is too much for the space available, and overruns the graphic.

Add New Year for Press Releases

Edit NAV2.xml, by adding new Nav3 level for new year (e.g. 2003, or 2004). (Simply uncomment Nav3 level code already in buildlist.xml.)
- find the location in /BusinessML/NAV2.xml for Press Releases:
  Figure 2.6. Press Releases location in NAV2.xml
  Using find command to locate N2 MEDIA in NAV2.xml
- Add (by "uncomment-ing") New Year for Press Releases
  To get the new year to appear, add (or simply uncomment an existing year entry (from <NavItem> to </NavItem> inclusive), that may be already in the NAV2.xml file; edit as described below:
  Figure 2.7. Press Releases Year 2002 (2003 commented out) (in NAV2.xml)
  Press Releases Year 2002 (Year 2003 commented out) in NAV2.xml
  Figure 2.8. Press Releases Years 2002 and 2003 (in NAV2.xml)
  Press Releases Years 2002 and 2003 in NAV2.xml. Be sure the entries appear in reverse chronological order.

Additionally, remove (comment out) Nav3 level for old year(s), as applicable.

	Note
Current policy is to maintain press releases for a "rolling" two years, which means as few as 13 months up to 24 months' worth. Dec. 31, 2002: Only 2002 is displayed in left nav (Initial year of this new scheme.). Jan. 1, 2003: Years 2002 (all 12 months) and 2003 (year to date) are displayed in left nav. Dec. 31, 2003: Same as above: Years 2002 (all 12 months) and 2003 (year to date) are displayed in left nav. Jan. 1, 2004: Years 2003 (all 12 months) and 2004 (year to date) are displayed in left nav. Note: 2002 is removed. Dec. 31, 2004: As above: Years 2003 (all 12 months) and 2004 (year to date) are displayed in left nav. Jan. 1, 2005: Years 2004 (all 12 months) and 2005 (year to date) are displayed in left nav. Note: 2003 is removed.

Note

Current policy is to maintain press releases for a "rolling" two years, which means as few as 13 months up to 24 months' worth.

Dec. 31, 2002: Only 2002 is displayed in left nav (Initial year of this new scheme.).
Jan. 1, 2003: Years 2002 (all 12 months) and 2003 (year to date) are displayed in left nav.
Dec. 31, 2003: Same as above: Years 2002 (all 12 months) and 2003 (year to date) are displayed in left nav.
Jan. 1, 2004: Years 2003 (all 12 months) and 2004 (year to date) are displayed in left nav. Note: 2002 is removed.
Dec. 31, 2004: As above: Years 2003 (all 12 months) and 2004 (year to date) are displayed in left nav.
Jan. 1, 2005: Years 2004 (all 12 months) and 2005 (year to date) are displayed in left nav. Note: 2003 is removed.

Make new directory for new year.
Under /mlnmdev/htdocs/media/news/ create a new sibling subdirectory for the new year (e.g. /mlnmdev/htdocs/media/news/2003/).
You will need to do the same for your website directory structures: currently /Inetpub/devroot/media/news/2003/ and /Inetpub/stageroot/media/news/2003/
Create your BusinessML "ct10" press release files for the new year (e.g. for 2003: ct10_pr-2003-01-02-0.xml, or for 2004: ct10_pr-2004-01-03-0.xml).
Note
These source data files all go in one subdirectory (no breakout by year, etc.): /mlnmdev/BusinessML/.

Tip
You may want to archive out the ct10 files for years that are no longer published to the website (i.e. 2002 press releases, come Jan. 1, 2004).

	Note
These source data files all go in one subdirectory (no breakout by year, etc.): `/mlnmdev/BusinessML/.`

	Tip
You may want to archive out the ct10 files for years that are no longer published to the website (i.e. 2002 press releases, come Jan. 1, 2004).

Modify the module near the bottom of the page on the "Recent Press Releases" page (/media/news/index.asp) that has the link "Click here to see additional 2002 press releases."

Tip

	Tip
If you don't know the filename for a module, you can always find it out by going to the source HTML on the live site's page: http://www.millennium.com/media/news/index.asp. Then do a `find` on a unique term or two from the page's text (e.g. "see additional 2002 press releases") to be led directly to the HTML "comment" that names this module: ct01_1med_press-releases_bottomline. This is the name of the `/BusinessML` file you will want to go edit: `/BusinessML/ct01_1med_press-releases_bottomline.xml`.

If you don't know the filename for a module, you can always find it out by going to the source HTML on the live site's page: http://www.millennium.com/media/news/index.asp. Then do a find on a unique term or two from the page's text (e.g. "see additional 2002 press releases") to be led directly to the HTML "comment" that names this module: ct01_1med_press-releases_bottomline.

This is the name of the /BusinessML file you will want to go edit: /BusinessML/ct01_1med_press-releases_bottomline.xml.

Modify the source XML for the new year.

	Tip
	You may want to maintain the "click here" link to the previous year's press releases for perhaps the first month of the new year, then remove it. (Navigation to the previous year's press releases is always available in the Nav2, of course.)

							ORIGINAL MODULE (prior to editing) 
	<contentBody> 
		<main> 
			<p>Click <a href="/media/news/2002/index.asp">here</a> to see additional 2002 press releases.</p> 
		</main> 
	</contentBody>

							REVISED MODULE (after editing) 
	<contentBody> 
		<main> 
			<p>Click <a href="/media/news/2003/index.asp">here</a> to see additional 2003 press releases.</p> 
			<p>Click <a href="/media/news/2002/index.asp">here</a> to see additional 2002 press releases.</p> 
		</main> 
	</contentBody>

							RE-REVISED MODULE (after, say, Jan. 31 of new year) 
	<contentBody> 
		<main> 
			<p>Click <a href="/media/news/2003/index.asp">here</a> to see additional 2003 press releases.</p> 
		</main> 
	</contentBody>

Prev	Up	Next
Chapter 2. Task-Oriented	Home	Add a New Page