> Personally, I think it would be better to link them to the appropriate > developers section, with pages like: docs.barn.functions.boltfinclude, > etc. The reason is these pages already have the php code pulled in > dynamically so you have the advantage of being able to see the very > latest code side by side with any help information. That was the idea
I think it's not useful to mix both information levels: The PHP code is useful for advanced users, but the average user needs only a clear description of the parameters and some examples. I suggest to reserve the developers section for code and code related information. For me it's no problem to have all information in the same page, but I think it will be a bit confussing for a new user to be redirected from the markup index into the developers section. Maybe an easier approach is to have pages like docs.index.functions.xxx to collect all user-level information about the function (usage and examples) and links to the related developer page, tutorials, and solutions for people who need to learn more. > behind this section. It will keep us from having information in > multiple places. And it's already nicely organized. In fact it's impossible not to have information in multiple places: tutorials, solutions, snippets... Some of them can relate to one function, but they are in distinct sections, like the developers section too. Anyway we'll see what's more practical when there is some content. Regards, Marcos --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "BoltWire" 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/boltwire?hl=en -~----------~----~----~----~------~----~------~--~---
