Their intranet sitemap may be complex because they're thinking in terms of how their organization works, its processes, and how it's divided. It's normal for organizations to want the same structure they have on the real world to be exactly the same on the intranet, but that doesn't make any sense. You need to think in terms of functionality, it's probably shared by most of their internal departments/divisions. Here's some examples of using functionality to divide:
You wouldn't make a menu section for news of each department, that would be stupid, you would just make a news section for everyone and then the news would have categories/tags so they could easily filter and see only their stuff if they wanted. Again, you wouldn't make a debate area for each department, you make just one debate area and, again, the debates would have categories and tags so people could easily filter them. You wouldn't make a documents section for each department, you would just make one and then you would automatically filter the documents you show based on what groups the user is part of. Dividing in terms of functionality not only makes the intranet simpler and easier to use, it makes the intranet a lot more useful as the main goal of an intranet should be for everyone in the company to know what the others, that aren't part of their team/department/division, are doing; so they can get a picture of the whole organization. By making them start in areas of functionality, where you have everyone in the same place, you make sure of that. -- 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 [email protected]. For more options, visit https://groups.google.com/d/optout.
