guidod - mksite - you need... a site.htm sitefile.

mksite.sh

project
- summary
- tutorial (2) (3)
(4) (5) (6) (7) (8) (9)
- usage (2)

technical
- reasoning
- two passes
- still tiny
- sitemaps
- variables
- accessibility
WAI SubSects

examples
- horizontal
- vertical
- tabbed (2)
- multi section
- printer style

links
- some hints
- faq&issues
- all features #
- about me
- our sitemap
- download

You need... a site.htm sitefile.

The sitefile is two things: (a) it provides the html envelope for you webpages (b) it lists the webpages that mksite.sh should look at.

(a) - simply think of the sitefile as being the "header" text added before the content of your "content" pages. The last line containing "<body>" is cut out and added after the "content" block. You can add everything to the sitefile that is common to your webpages - including any common title tag, some additional CSS "<style>" block, or a navigation bar for the webpages. The "mksite.sh" script will be modifying the sitefile text slightly for each output page - e.g. it will highlight the current page entry on the navigation bar. Also you can add some variables like "" or "" that will be expanded by the mksite web generator.

<html><head><title> my website  </title> <style> H4 { text-align : right ; } </style> </head><body> ... </body></html>

(b) - Above we show just the three lines of the html envelope but nothing of the navigation items. To do navigation in html one adds href entries, i.e. "<a href="pagename.html">page name</a>". That can be done here in the sitefile as well and just like in normal html. However the mksite.sh script will care for some hrefs more closer than for others: if you make a href start leftmost on the text border than these files shall be generated. Whatever filename is included in the href ("pagename.html") will be a target file and mksite.sh will look for corresponding source file to be around - in this case let's assumke a file named "pagename.htm" might be found and mksite.sh will think that it is the content page for the target.

As the bottom line: for each html page you want to have, make a href starting leftmost.

<html><head><title> my website  </title> <style> H4 { text-align : right ; } </style> </head><body> <a href="index.html">Overview</a> <a href="loremipsum.html">Lorem Ipsum</a> <a href="pagename.html">more pages...</a> <br> </body></html>

If you do not want mksite.sh to touch a target "html" file then simply add some spaces before the "href" on the line. Remember that each target page specification must be fit onto one line but that is usually no problem for a href that should be on a navigation bar. - We will show later that you may add some markup around the "href" and mksite.sh will still recognize it as a target href but the sitefile above is actually complete: it will show up as a top line with your navigation items and the content text added below (plus the current page will be highlighted in "b"old on the "navigation bar").