it would also be nice if one could jump from 1.3 => 2.0 for the same thing often times the google results are still on 1.3 but then I have to "research" in the ajax box what I have been looking for before because there is no direct link
On 7 Dez., 18:19, mark_story <[email protected]> wrote: > I've toyed with adding an on-page TOC for the sub-sections not in the > master TOC, but haven't had the time to add it in. It shouldn't be > hard to do on longer pages with lots of subsections. Its probably > mostly a matter of updating the CSS and adding the toctree directives > where necessary. > > -Mark > > On Dec 7, 4:47 am, AD7six <[email protected]> wrote: > > > > > > > > > On Dec 6, 11:34 pm, aries <[email protected]> wrote: > > > > Hi, > > > > I'm not sure if this is the right place to post my comments, but I'm > > > unable to find a more appropriate venue. Feel free to redirect me. > > > > Unlike previous versions, the 2.0 documentation lacks heading links > > > within the TOC. It used to be that when viewing a particular topic you > > > could access subtopics easily. For example, the 2.0 page on FormHelper > > > is extremely long and finding information on, say, structuring a > > > select options array can be maddening if you don't know where in the > > > page to look. Once found you can bookmark the paragraph's permalink, > > > but that's not very useful for quick reference lookups. > > > > Also, the current topic is not highlighted in the TOC navigation. It > > > would be helpful for the user to know where they are at any given > > > point. A breadcrumb trail might help here. > > > > Lastly, I'm wondering why user comments aren't allowed. I know that a > > > lot of comments can make a page unwieldy, but I thought the pre-1.3 > > > doc pages handled it well, with comments for each section available by > > > click. I often found those comments quite helpful. > > > A comment in place of simply editing the docs is not helpful. There > > aren't any useful comments on the old book that should not be edits > > (and that's if you can find one at all). This point has already been > > discussed ad nausium (here, on the group). > > > > I greatly appreciate the amount of information contained in the book > > > as well as the time and effort it must have taken to put these docs > > > together, but it seems to me that some attention to some basic > > > navigation UI would help tremendously. > > > I'm not clear on exactly what it is you're asking for - but the source > > for the docs are herehttps://github.com/cakephp/docs > > > AD -- Our newest site for the community: CakePHP Video Tutorials http://tv.cakephp.org Check out the new CakePHP Questions site http://ask.cakephp.org and help others with their CakePHP related questions. To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/cake-php
