>>Ideally, all of these roles work together in order to get things done, >>but they only have to worry about their specific role. >> > > I have come to believe this is a fairy tale. No individual in a > development group, in my opinion, can *ever* worry about just their > role. They can specialize on their role, but you can't make a rigid > wall here. Maybe as Cocoon (and more specifically, Cocoon's best > practices) matures, this may get better.
Ahh, but that's the beauty of role based documentation: you're not forcing people into a particular role. You're just saying "when performing this role, here's where you find the information about how to do it". If people switch roles or don't fit into a particular role they still have a clue where to look in the docs... <snip/> > I think this is a bad idea for the reasons stated above. > Since it's Super Bowl season here in the U.S., I'll use a (American) > football analogy. Before Cocoon, in the heady days of just JSP, ASP, > and PHP, it was a pickup game at the park. The role of quarterback is > constantly changing who it applies to and everyone's scrambling in all > different directions. People generally enjoy themselves and are hostile > to the idea that people should be assigned roles and stick with them. So, who is assigning roles? No one, it's just the docs tell you how to perform a given role... --------------------------------------------------------------------- Please check that your question has not already been answered in the FAQ before posting. <http://xml.apache.org/cocoon/faq/index.html> To unsubscribe, e-mail: <[EMAIL PROTECTED]> For additional commands, e-mail: <[EMAIL PROTECTED]>
