ENHANCEMENT Ticket (pending)
Categorization Tree based on the Book
The book is an excellent resource. However it covers baseline instructions and uses. Hundreds of articles posted in blogs or on the bakery are user-submitted expansions of these scenarios.
Perhaps the bakery, in this way, can also serve to be an extended version of the book. You are adding user-revision and heavy moderation, if we are taking the time to choose the best scripts, why not take the time to list the best practices in one place too? Although hosting _alternative_ practices and listing the reasons why _not_ to use them would have been helpful too (but that is suitable for a more 'pure wiki' approach).
Have the bakery organize just like the book, each layer, issues addressing views, components, etc. And perhaps even a way to implement a cursory coverage of major blog posts. It's very annoying that we have to go free-searching for blogs. If we're not doing a pure wiki, can we look to embed this kind of referencing?
on 07.15.09
reported by: ProLoser
on 07.16.09
by alkemann
- type was changed to enhancement
on 07.19.09
by pointlessjon
I don't feel it would be helpful to me as an end user to do this. I think the bakery would benefit most from the simplified structure it has/ is going to use. In fact, I'm going to suggest a slight modification in a different ticket.
I might not be understanding your suggestion here, but the goal of the book is to cover pretty much everything (eventually) in a more literal fashion (as opposed to a more technical fashion like the API). The bakery is meant to foster the community and supply a functional source for reusable code and tools/tips/tutorials.
To that end, it would make more sense to me to move things like the blog tutorial out of the book and into the bakery - and have the book reference bakery articles (specifically a tutorial in this instance).
However, I do think your goal is good. Your other ticket regarding linkage to/from book/bakery/blogs etc. is more along the lines of what I think would better achieve connecting all these things.
Does that make sense? Or am I misunderstanding something?
on 07.20.09
by ProLoser
I may be a bit confusing on my idea of 'expanding the book'. My main intention is to provide a __navigation and organization structure__ that mirrors or is very similar to the book.
The blog example is perhaps a good idea of what may be more relevent in the bakery (under tutorials) and utliizing crosslinking is an excellent approach (for consolidation of duplicates).
The problem I want to solve is that the current organization of the bakery is quite horrible. Frankly there are only a few ways to browse, the front 'favorites' listings, a search (which seems very broken), and a huge list. I would prefer a tree-structured organization that allows me to quickly move to an area of relavence to what i'm searching for, so that I don't have to know the name or proper terminology to find solutions to my problem (a common problem). We don't always know what the name of the component/plugin/behavior is when we go searching for one. Using a stronger browse capability would be helpful.
