Bug#541993: Better TOC for http://www.debian.org/devel/wnpp/index.html ?
On Mon, Aug 17, 2009 at 10:43:57AM +0200, Sandro Tosi wrote:
> I've just received a complain about [1] where what it seems, at first sight, a
> TOC, infact it is not: it's a series of links to aggregated WNPP bugs but not a
> TOC fot the given web pages.
>
> [1] http://www.debian.org/devel/wnpp/index.html
>
> Since, at least in this case, it generated confusion and lead to missing the
> information about how to provide a correct WNPP bug, I'd suggest to introduce a
> simple TOC (moving also the "Using WNPP" at the top of the page):
>
> 1. importart links for WNPPbugs
> 2. report a WNPP bug with reportbug
> 3. report a WNPP bug via plain email
> 4. how to close a WNPP report
>
> and then the current content.
>
> This bug is meant to collect opinions about it (that might also direct to
> remove/rewrite [1]) and if it's a correct solution to the presented problem
> (that I recognize to exists: I know what's in that page, but a first-time
> visitor might be disoriented).
>
Sounds good :)
Also, the subpages could use some re-organizacion.
For example for packages with RFA and O we have 4 pages:
*/wnpp/rfa_bypackage - List of packages RFA alphabetically
*/wnpp/rfa_bymaint - List of packages RFA by maintainer
*/wnpp/orphaned - List of packages orphaned (qa team in maintainer)
*/wnpp/work_needing - Lists packages for adoption, then same list by
maintainer, then orphaned packages.
The fourth page shows the information of the 3 others page and is clearly
lacking a TOC.
Suggestion:
Kill the rfa_bymaint page and add a page that lists then by date. I think
seeing how old the bug is more interesting than seeing who is the current
maintainer.
Remove the */wnpp/work_needing page. It is too long and if the main page
has a clear TOC it should not be needed.
Finally, keeping the sub-menu between all the pages, in the top.
For example, when I go go the */wnpp/rfa_bypackage from the TOC in the main
page I get:
----------------------------------------------------------------------
- Go back to the "Work-Needing and Prospective Packages" main page
- See this list by date
- See orphaned packages.
<h1>Packages up for adoption</h1>
* afnix ...
* alevt ..
....
----------------------------------------------------------------------
Something similar could be done with */wnpp/prospective that contains
*/wnpp/being_packaged and */wnpp/requested
Ana
Reply to: