Documentation links

[Jim Walters]

I was mulling this over while thinking about how to use Faq-O-Matic for
the contextual help. Was leaning towards making a new table in MySQL and
populating it with a help_id, URL table. Seemed to be the most flexible
since I could point to the html docs, URLs for the Faq-O-Matic links or
even to some HTML links for help in a non-English HTML document at some
point in the future without touching the perl code. Admin code update
the links via the web interface eventually (perhaps even pointing to bmo
hosted documentation) and though the IDs would get cast in stone, new
ids are cheap.

Jim's 2 cents.

On Mon, 2003-02-24 at 13:06, Joel Peshkin wrote:

> David Miller wrote:
> 
> >
> >I don't think it's all that bad of an idea, but the question then comes to
> >be what do we link it to?
> >  
> >
> 
> How about a parameter called  documentbase with default values "docs/" 
> that can be cleared to disable the links or can be pointed to bmo's copy??
> The biggest issue I can see is making sure that the right page/anchor 
> combination gets loaded.  Should there be a cgi that serves up the right 
> document section for each link?  Othewise, the code has to know what 
> filename contains each anchor.
> 
> 
> 
> 
> 
> ----
> To view or change your list settings, click here:
> <http://bugzilla.org/cgi-bin/mj_wwwusr?user=jimw@bugopolis.com>

__________________________
Jim Walters   Director of Technology
Bugopolis, Inc.

phone: +1 206 447 8315 
email: jimw at bugopolis.com
web: http://www.bugopolis.com
_________________________
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bugzilla.org/pipermail/developers/attachments/20030224/3de78df9/attachment.html>