Template...

Date: Sat, 10 Jun 2000 00:33:17 -0300 (ADT)
From: < @chebucto.ns.ca>
To: Susan Lilley <LilleyS@chebucto.ns.ca>
cc: editors@chebucto.ns.ca
Precedence: bulk
Return-Path: <editors-mml-owner@chebucto.ns.ca>

next message in archive
next message in thread
previous message in archive
Index of Subjects



Hi Susan,

   The learning curve is steep at first but once you do the first couple
of pages, the rest fall into place pretty easily.

   What #7 means is that there is a url that points to the homepage.  You
need to add a url for each page depth you are dropping...for example, if I
am editing an Events Calendar 3 levels down which links back to the main
Events page and then the CCN homepage so I would have 2 urls and then the
name of the page I was working (which doesn't need to be a url but simply
the page name).

   By duplicating the homepage link via cut and paste, you're simpy saving
a bit of time in typing the entire url string each time - instead just
changing the pertinent data.  My example would look like this:

Home &gt; &gt;
News, Events & Hot Topics &gt; &gt;
Upcoming Events

...which renders...

[Home] >> [News, Events & Hot Topics] >> Upcoming Events

   The first two are working links, the last one is just the name.
Instead of typing out the entire url just cut and paste the first one as
many times as you need it and just substitute whatever data needs to be
changed (such as the url name and the document it points to).

   The only reason I suggested cut and paste was to save time.  Your're
free to do it whatever way you feel comfortable as long as the final
document looks the same.  I am doing some HelpDesk documents what are 5
and 6 levels (they were further down but I raised them up a couple of
levels) and the cut and paste urls saved time.

   FTPing to your home computer and back again is okay as long as you use
the template located at:  /csuite/info/template.shtml  and _NOT_:
http://www.chebucto.ns.ca/template.shtml  which would render the full
document and defeats the purpose of the substitution template which to
allow future revamps by just changing the subsidiary templates which
exist alongside the main template and called into the documents as they
are created by 'http' visitors.

   All of the old documents on CCN are static - meaning they are 'carved
in stone' and what you see in the source code is what you get.  The new
documents based on template.shtml will be dynamically created each time
you access them so changing one of the side templates to reflect a change
in policy or design will be incorporated in all documents automatically as
they called up by a browser without going in an physically changing each
and every document on the system again.

 

------------

> From: LilleyS@chebucto.ns.ca [mailto:LilleyS@chebucto.ns.ca]

> I have received your message and will try to make the changes this evening.
> I read through  's notes and can't say that I understood much from
> here on:
> 
> > 7. Move down to the area where you see:
> > Home &gt; &gt;
> > and add the name of the page to bottom of it.  Use the cut and paste to
> > duplicate the 'Home' line and change the url and the name of the link for
> > each level you working back from.
> 

next message in archive
next message in thread
previous message in archive
Index of Subjects