You are viewing a plain text version of this content. The canonical link for it is here.
Posted to docs@httpd.apache.org by André Malo <nd...@perlig.de> on 2003/07/01 02:51:39 UTC
Re: cvs commit: httpd-2.0/docs/manual/mod mod_ssl.xml quickreference.xml
* Joshua Slive wrote:
> On Sun, 22 Jun 2003, André Malo wrote:
>> Hmm. If we consider the sitemap containing references to all files, it
>> should contain that link, too. For example, in the CHM toc, I think, it
>> would be still useful.
>
> A philisophical question: is a sitemap a list of all "files" or a list of
> all "content"? I don't know, but I think I favor the latter.
philosophical - may be. Technical - we need one document that maintains a
list of all files for transformation and autogeneration purposes. The
sitemap doesn't seem to be the worst choice ;-)
>> This problem should be gone anyway, if/when we automate the FAQ category
>> entries. Then we would do something similar to the modules (a &faq; entity
>> or so) and every transformation can do with this, what it wants. What do you
>> think?
>
> Sure. I'm having a hard time imagining exactly what this will look like,
> but it sounds like the right direction.
Once I have more time, I'll take it (if nobody else does).
nd
--
Gefunden auf einer "Webdesigner"-Seite:
> Programmierung in HTML, XML, WML, CGI, FLASH <
# André Malo # http://www.perlig.de/ #
---------------------------------------------------------------------
To unsubscribe, e-mail: docs-unsubscribe@httpd.apache.org
For additional commands, e-mail: docs-help@httpd.apache.org
Re: cvs commit: httpd-2.0/docs/manual/mod mod_ssl.xml quickreference.xml
Posted by Astrid Keßler <ke...@kess-net.de>.
>> A philisophical question: is a sitemap a list of all "files" or a list of
>> all "content"? I don't know, but I think I favor the latter.
> philosophical - may be. Technical - we need one document that maintains a
> list of all files for transformation and autogeneration purposes. The
> sitemap doesn't seem to be the worst choice ;-)
I tend to tell a sitemap a table of content, not a list of all physical
files. But both needs can be fullfilled with one document, when we think
of the generated sitemap as a subset of the files list. An attribute
"hide from sitemap" would help.
For this special problem ...
>>> This problem should be gone anyway, if/when we automate the FAQ category
>>> entries. Then we would do something similar to the modules (a &faq; entity
>>> or so) and every transformation can do with this, what it wants. What do you
>>> think?
>>
>> Sure. I'm having a hard time imagining exactly what this will look like,
>> but it sounds like the right direction.
... a new faq will do it. Sounds good.
Kess
---------------------------------------------------------------------
To unsubscribe, e-mail: docs-unsubscribe@httpd.apache.org
For additional commands, e-mail: docs-help@httpd.apache.org