UNYwiki.com

Introduction

The team members in our Alliance have an enormous amount of knowledge and experience in this complex game, and continue to do research and experiments every week to learn more.

We share large number of tips and guidance in chat. Most of this content is lost, hard to find in the future, maybe sometimes incomplete guidance, maybe sometimes only relevant to players at higher or lower levels, maybe even sometimes mistakes or bad guidance :)
Since I joined UNY, I think I’ve seen ~500 different topics discussed with valuable insights brought to each topic from our team members. I think there are probably >1000 topics worthy of documenting, and on many of these topics, different guidance needed for different level players, more details needed, in some cases even more experiments needed.

A wiki would be a place for us to organize all our tips and guidance to produce a browseable, organized, searchable, private, and easily linkable reference.

The most widely known wiki is wikipedia.com
If we decide it worthwhile to explore producing our own wiki, I can assist by getting the software installed (the same software used to run wikipedia.com) and helping get things organized with some examples. If we proceed, participation from other members will be needed.
Our wiki can be set up to be private to members (no one outside of approved members can access the content, content would also be hidden from search engines), with administrative roles provided to UNY leadership or approved volunteers (to approve new content, manage members, lock content, add special comments, etc.)

Collaborative editing and contribution of new content
"Talk pages” / "Discussion pages" where the details behind a page can be discussed, revised, debated, and approved before updates are made to a published page
Advanced support for multiple languages (wikimedia uses a combination of different language engines, and this is claimed to be better than google translate / language tools). See, for example, the Wikimedia language committee.

If we proceed, the wiki would not be a place for chat. We have those already. The wiki would be a place to record and organize our collective knowledge.

When questions come up in the game chat, we could point people to relevant wiki pages (or create new pages for new questions, or edit current pages when we have new details or improved understanding of the topic).
If providing web links in the game chat is blocked, I believe we can create small URLs, which would be relatively simple to use (but not perfect). The wiki could be easily searched or browsed for a specific topic, and the URL / web address for that topic could be based on a short number.
For instance, the topic page “optimizing the conversion of officer fragments” might have the web address “www.unywiki.com/004540” and might be communicated in chat as “look at wiki page 004550”.
Lots more details, of course, but I would be cautious that none of us undertake a project like this without validating our assumptions and proceeding incrementally to make certain we don’t invest time in something that won’t work well in the end.

In casual chat, IW pointed out that this type of resource might best be used as a reference. That is, to do research and preparation for an event, upgrade, next push to level up, etc. That sounds right.
What could go right?

This serves as an improved reference, a place for us to come to consensus on complex topics, and more.
Our collective time in doing research and communicating to the team becomes more efficient.
Game chat might have less repeat discussion or questions and answers. Maybe.
We might be able to retain and advance members, or even attract new members by having the best reference resource.

We spend a lot of time on this, but it doesn't get used. (This is usually the #1 risk.)
This takes time and effort away from regular gameplay.
This creates an unexpected conflict among team members or different alliances. (We can try to keep this private, and can add features that make it hard to copy the content, but keeping this 100% private might not even be a good goal [I don't have a personal opinion on this topic.])
Lots more can go wrong, happy for feedback and ideas (but usually lack of use is the biggest risk).

UNY Leadership and any experienced members selected by leadership first consider if this is a good idea, would it be practical, what might go wrong. Maybe one of the R4s can volunteer to lead a private discussion with the other leaders about this? (Is there a volunteer or someone already appointed for this type of stuff? If so, contact me directly in the game mail or chat or viber.)
If there is positive consensus from UNY Leadership to explore this, I can install the wiki software and think we should test out the multi-language capabilities before anything else.
We have important participants with many different languages. If they all can’t contribute in native language or if the translation is poor, I don’t think we should proceed. We can test this without too much effort. If the multi-language support is good, this great diverse team could probably do a great job to refine the wording of our content so that it is clearly understandable in all languages (that is, suggest an edit to page or flag content when the translation isn’t 100% clear).
If the language support is good, then I think we would need a few committed volunteers to help get this started successfully. Even then, we should start small, and see how it goes. I can help with a lot, but it would be a risk to the future success of this project if there were only one person running it.