I need to have containers for my pages, so I guess the best option is to create area's.
But how do I create 100+ area's without needing to set all the options for every area?
I need to have containers for my pages, so I guess the best option is to create area's.
But how do I create 100+ area's without needing to set all the options for every area?
XenForo doesn't really have a similar option, but this was a regression from VW3 where you could create a new wiki forum based on an existing wiki forum: https://www.vaultwiki.org/issues/4085/
That regression is resolved in 4.0.9.
Even so, I'm not sure I would recommend creating several hundred areas. What is the design plan that results in so many?
- lead developer for VaultWiki
I need users to work on pages in one category at a time. They need to have an overview of these pages and their status. And be able to navigate through categories and pages. So the question is whether to use areas or categories. The latter seems more logical, but this lacks the organizational tools to keep a good overview of who is doing what, what has been updated and what needs to be done.
If its all in one area then it becomes one massive list of pages(stubs, unfinished, finished) and people just drown in it. We need a way to work towards completed categories.
Another problem is that only a few pages are shown and that users need to click on 'show all pages' which no one does so everyone is confused.
I might use a combination of feeds and categories.
Keep a global feed "X" that includes as entries all the pages being worked on. Organize the feed by Last Update.
Categorize everything on the feed using "X Unfinished", "X Stubs", "X finished" etc. (When you're on the List view for these categories, you can change the Sort order to show Last Update first if you need to check for new updates).
Have an extra page where you discuss and assign work, and add it to the feed. Link to it in the text of each sub-category. On the page create links back to the feed and to each sub-category.
Then you can just move the pages between sub-categories as they are updated and completed.
Have everyone working on it subscribe to the work page and to the global feed.
If individual users need to keep lists of "Pages I'm Working On" have an area called "Work Assignments". Have a unique prefix for this area like "Work". Create a global feed for each user who will be working with Prefix "Work" and title being their username. The user should subscribe to this feed too. Whenever the work manager wants to assign/unassign a page to a user, add/remove it from that user's feed in Work Assignments.
You can increase the number of pages that are shown on the front page of an area or a category via the VaultWiki: Navigation options group. If the "Previewed" setting matches the "Per Page" setting, the front page will become page 1 of the List tab.
What you are trying to do is really a great scenario of how Wiki Teams might be used when that feature is finally done. I will link to this thread in the request so there's a reference of all the different wiki features that need to work together in an automated way for a great Teams implementation.
- lead developer for VaultWiki
Bookmarks