Board Thread:Support Requests - Designing Your Wikia/@comment-15636815-20151104205648/@comment-4731443-20151106022405

I can't add much to TableWiz's excellent advice, but since you are overwhelmed with the amount of tasks and the amount of work each requires, I would say: prioritize. Make a list of every little thing you need changed. Style guides and policies, categorization, templates, infoboxes, community interactions, all of it. You can note how much work you think each will require (even in loose terms such as "huge" or "a couple days") if you want.

Then establish dependency. Since you have a lot of work to do on interconnected things, you want to make sure not to duplicate work. For each thing you change, what else will it affect? Will you need to review your categories after you've changed the way you present content? Will you need to change your templates once your style guide is final? Ideally, you'll want to work first on things that have a lot of dependent tasks rather than those that depend on several others.

I don't know what your community looks like and how many are involved, but it also sounds like you would benefit from splitting up the work into more digestible tasks. Since your subject matter has frequent updates, it would be great if you can set one person to monitor and implement updates so the rest of your team can focus on the overhaul and nothing else.

One person could look at your content and design the style guide and best practices. Another will look at your categories versus your content and build a treeview of what your categories should look like and what should be in each. Another will start building new infoboxes in a sandbox and keep in mind to be flexible for upcoming changes. And each person who is assigned a large task should also consider splitting their own mission into subtasks they can complete in order so they can keep track of their progress and hand some of it over to someone else if needed (e.g. lack of time, or missing expertise for one particular aspect).

The way I see it, there are two opposing sides to this sharing of work: on one hand, it allows each person to focus on one thing and complete it faster; on the other, you want to keep in mind that everything is changing, so they should all keep an eye on the other people's work and consult each other when needed. It would be great if the person who works on categories is taking notes on a page you all can view and comment on as they go. The infobox person can ask the categories and best practices persons if they have any special requirements. And so on. You don't want to end up with a bunch of brand new pillars and realize at the end that the roof doesn't fit on them ;)

Lastly, don't be afraid to ask for advice and help here for specific tasks. Sure we can't jump in and do everything for you, but if you make a thread about redesigning your Infobox_wagon template with all the relevant info, you'll get a bunch of people making suggestions and willing to write some of the code for you. A few days later you can tackle another infobox or ask everyone to take a look at your new category tree draft and suggest improvements. As long as you don't post a hundred threads in a single day to cover everything at once, I think you'll find enough help to lighten your burden =)

P. S. About the stress, take it easy and set your own pace. At the end of the day, it's just a Facebook game and nobody's in danger if you get a little behind on your updates =) If the playerbase is really dependent on the wiki, maybe you could even ask the game's developers to lend a hand - who knows?