Cancer wrote:
>  http://www.turbogears.org/2.1/docs/
>
> when I click in the site via the url above.The document is same with
> document for TG2.0.
> I cann't find the 2.1 document anywhere on the official site.
>  so where can I find the 2.1 document?
A while back I followed a link to the main page of the 2.1
documentation, which I can't find anymore.  That main page linked to
http://turbogears.com/2.1/docs/gettingtoknow.html, which is not the
right place to start, but you can get to the other pages from it.  All
pages are listed here:  http://turbogears.org/2.1/docs/main/

Aha...I found it--now this is a bit tricky--you have to click on the
headings lower down on the page on
http://turbogears.org/2.1/docs/index.html to get to the 2.1 docs--the
headings named "Getting Started," "Tutorials," "Working with
TurboGears," etc.  Those headings are links to documentation pages. 
That page needs to make it more obvious that those headings are
links--maybe underline the heading on hover, or put an arrow pointing
the right of the heading inviting the user to click the heading/arrow to
go deeper into the documentation's hierarchy, or add additional text
colored orange to make it clear it's a link, or link the whole paragraph.

I read through a lot of these docs recently, and must say I think they
are excellent!  Very readable, sufficient code examples to get me
started, and graphically pleasing; overall more friendly, inviting, and
usable than the old wiki for a newbie.  However, I wish the central
column was a little wider--more like the Pylons documentation
<http://pylonshq.com/docs/en/0.9.7/gettingstarted/>--maybe by removing
the right column and making the table of contents a <div
style='float:right'>.

Tim Black


-- 
You received this message because you are subscribed to the Google Groups 
"TurboGears" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/turbogears?hl=en.

Reply via email to