while speaking of simplifying htdocs/XML ...(auto)layout

we maintain htdocs/layout.html, generate autolayout.xml and
some navigation 
headers in the HTML files from that. I guess the idea here
is to have a site 
map of htdocs or something, but I wonder if that's worth the
effort:
1) where is that site map, I've never seen it
2) the next/prev navigation links in the generated HTML
files are
    outdates, as not everything is committed on
re-generation.

I guess I'm missing something important here, but maybe
someone (Jan?) can tell 
me the deeper idea behind layout.xml, autolayout.xmk etc.?


  - Hubert

Hubert Feyrer <hubertfeyrer.de> wrote:
> 
> we maintain htdocs/layout.html, generate autolayout.xml
and some navigation 
> headers in the HTML files from that. I guess the idea
here is to have a 
> site map of htdocs or something, but I wonder if that's
worth the effort:
> 1) where is that site map, I've never seen it
> 2) the next/prev navigation links in the generated HTML
files are
>    outdates, as not everything is committed on
re-generation.
> 
> I guess I'm missing something important here, but maybe
someone (Jan?) can 
> tell me the deeper idea behind layout.xml,
autolayout.xmk etc.?

I can't.  IMO autolayout (for the website alone, not the
guide or pkgsrc
guide or the internals book) should go Away.  Yes, with a
capital 'A'.


-Jan

-- 
42

On Tue, 28 Nov 2006, Jan Schaumann wrote:
> I can't.  IMO autolayout (for the website alone, not
the guide or pkgsrc
> guide or the internals book) should go Away.  Yes, with
a capital 'A'.
> 

IIRC autolayout is not used by any of the guides anyways, is
it?
(I cannot remember having to maintain anything like that...)


  - Hubert

On Wed, Nov 29, 2006 at 12:27:25AM +0100, Hubert Feyrer
wrote:
> we maintain htdocs/layout.html, generate autolayout.xml
and some navigation 
> headers in the HTML files from that. I guess the idea
here is to have a 
> site map of htdocs or something, but I wonder if that's
worth the effort:
> 1) where is that site map, I've never seen it
> 2) the next/prev navigation links in the generated HTML
files are
>    outdates, as not everything is committed on
re-generation.
> 
> I guess I'm missing something important here, but maybe
someone (Jan?) can 
> tell me the deeper idea behind layout.xml,
autolayout.xmk etc.?

layout and autolayout.xml/xsl are used for making a
"database" of all
documents and IDs. This is necessary, because the website
consists of
a bunch of XML files (rather than just one). This is the
reason why
inter-werbsite links are often incorrect if a page is not
added to
layout.xml.

-- Daniel

On Wed, 29 Nov 2006, Daniel de Kok wrote:
> layout and autolayout.xml/xsl are used for making a
"database" of all
> documents and IDs. This is necessary, because the
website consists of
> a bunch of XML files (rather than just one). This is
the reason why
> inter-werbsite links are often incorrect if a page is
not added to
> layout.xml.

I don't understand. What of

 	<ulink
url="../../foo/bar.html#baz">glibber</ulink&
gt;

can go wrong that way?


  - Hubert