I built a quick and dirty user-created documentation system where for each topic, there is 1:M stakeholder-perspective content.
Am asking the group if there might be a little less-dirty, less quick method. Here is what currently exists: Example, for inventory system documentation there is for each topic, documentation for these stakeholders: 1. business side documentation 2. programmer documentation 3. database administration documentation 4. architecture documentation It works okay with text fields containing the documentation. E.g., TOPIC_TABLE 1. title (how to enter inventory data) STAKEHOLDER_TABLE 1. topic_ID (1) 2. stakeholder_type_ID (database administrator) 3. content (text field, displayed with "pre" tag) The goal is to promote collaboration between business side, tech side by having the content for a topic laid out by stakeholder perspective, side-by side. Just wondering if there are any ideas to improve this without requiring users to learn Sphinx or more complicated methods. thanks, Alex Glaros -- Resources: - http://web2py.com - http://web2py.com/book (Documentation) - http://github.com/web2py/web2py (Source code) - https://code.google.com/p/web2py/issues/list (Report Issues) --- You received this message because you are subscribed to the Google Groups "web2py-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to web2py+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
