Re: website problems

Hi Markus,

Markus Hoenicka wrote:

>2) I don't quite see how the addons-debian.html page should be
>   officially linked to. I think it is confusing if users end up there
>   by following an obscure .deb link, but can't figure out a way to
>   find back to that page from the main page. I'm open to suggestions
>   how to handle this. I've mentioned previously that I want to extend
>   the section about refdb-mode once it works with an official RefDB
>   release. This might require a second-level menu containing entries
>   like PHP web interface, Emacs helpers, vim helpers, Perl stuff and
>   so on.
>

Frankly, I'm not happy with it either.  It's a site design problem I 
haven't resolved to my satisfaction.  The issue is that there are 
specific instructions that must be given to debian users as to how they 
make the repositories (refdb [cvs], refdb [release] and addons) 
available to debian's package management system -- essentially this 
boils down to adding an appropriate line to '/etc/apt/source.list'.  
What I don't want, however, is for debian management issues to take up 
any sizeable amount of the addons page since the majority of users will 
not be debian users.

There is also some information regarding the source files -- mainly 
about dependencies and how users should examine the output of 
'./configure --help' when building from source (untar + read 
README|INSTALL + ./configure + make + make install).

Upon reflection, what I'd like is a page devoted to the various modes of 
package installation.  There would be a section for installing from 
source (autotools-style foo.tar.gz files) and one for installing debs.  
The section on installing debs would not have all the crap that's 
currently in 'addons-debian.html'.  It should be trimmed down to the 
bare minimum and assume the reader is knowledgeable about debian package 
management.  For new/inexperienced debianites there would be a link to a 
relevant (external) debian package management tutorial.

Since one of my packages (vim-docbk-xml-refdb) has significant external 
dependencies (e.g., fop, xmllint, xpdf, etc.) that are only available 
from outside the refdb site there could also be a section on external 
dependencies.

Such a page would be a central site for information on installing refdb 
and refdb-related software.  If you do later split the addons page into 
a multi-tiered structure, each page could link to the install 
instructions page.  It could also be included on the site map.  If any 
refdb software is later made available via another installation method 
(rpm, slackware archives, etc.) then you have a single page to update 
with install instructions.

I guess what I'm proposing is a separation between download instructions 
and install instructions, with debian instructions going into the 
install page.

What do you think?  If I'm not totally off base here, I'd be happy to 
design the relevant pages.

Regards,
David.


-------------------------------------------------------
SF.Net email is sponsored by:
Tame your development challenges with Apache's Geronimo App Server. Download
it for free - -and be entered to win a 42" plasma tv or your very own
Sony(tm)PSP.  Click here to play: http://sourceforge.net/geronimo.php