#421 Guidelines front pages are confusing


I initially raised this issue during the Council telco in December, and was tasked with asking for feedback on TEI-L. I've now done that, and I'm raising a ticket to summarize the responses. First, the problem:

If you go to the P5 Guidelines right now, you'll initially hit this page:


from which you can navigate to the online version here:


This index.html page has links to all the prefatory material, some links
to other related sites such as the SourceForge repository, and "Some
Popular Sections", a list of a few chapters in the main Guidelines. It
also links to the full Table of Contents:


which is what it says it is.

I've noticed in workshops that this three-stage entry process confuses
people, and in particular, the intermediate page with its "popular
sections" is not very useful. Even more confusingly, if you click on the
main menu "Guidelines / P5 Guidelines / -Table of Contents", you go to a
completely different page:


I received five responses, summarized here:

a) (2 votes): merge <http://www.tei-c.org/release/doc/tei-p5-doc/en/html/index.html> and <http://www.tei-c.org/Guidelines/P5/> into one single page (and leave the ToC as it is).

b) (1 vote): merge <http://www.tei-c.org/release/doc/tei-p5-doc/en/html/index.html> with the ToC putting "Versions of the Guidelines", "Some Popular
Sections" and the language section on a separate column on the right.

c) (1 vote): The extra index.html page is confusing, so get rid of it.

Comment from Lou:

One thing I like about the "short" index page is that it puts the language switches up top, so people realise the Guidelines are available
in multiple languags. If we change things, I hope that will continue to be the case for whatever replaces it.

Nobody wrote to defend the multiple pages. I would go for b) myself, and b) also satisfies c). Many people say they just bookmark the ToC page once they've found it, and go directly there from their bookmark.


<< < 1 2 (Page 2 of 2)
  • James Cummings

    James Cummings - 2013-11-09

    Should this ticket not be closed?

  • Sebastian Rahtz

    Sebastian Rahtz - 2013-11-09
    • status: open --> closed
    • Priority: 5 --> 1(low)
  • Sebastian Rahtz

    Sebastian Rahtz - 2013-11-09

    yes, done

  • Martin Holmes

    Martin Holmes - 2013-11-09

    Closing this -- it's been implemented and is in the last release.

  • Martin Holmes

    Martin Holmes - 2013-11-09
    • status: closed --> closed-fixed
<< < 1 2 (Page 2 of 2)