Talk:Suggestion/@comment-25637142-20150910101017

I call for a review on our event handling in response to the feedbacks in this blog.

First thing first, I set up a sandbox page with the restructured event page using the tabview-subpage model. This rework attempt won't be limited to article pages or templates but will also involve the related forum threads and comment sections as well. I'm going to need a lot of feedbacks, a lot of ideas and all the helping hands to create a better physical structure to handle future events.

Second of all, a review of human resources management and communication platforms. In the last event, we rely on Chat and Teamspeak but we'll need some where non-volatile in the future. And the strategies to cope with HR shortage when a tough event hits and hogs everyone's effort into clearing/farming from wiki editing (4/6 temp mods abandoned ship last event, even seasoned editors x hardcore ttk had to put way more effort in the game).

Lastly, a review on information gathering and validation system. Until now, we have been relying heavily on datamining for enemy stats, map reviews and new equipment. We also rely on the obvious visual differences to tell one Abyssal unit from another. Summer 2015 Event changed all that.

API revamp right before event (effectively limiting datamining capabilities) and the introduction of Wo variants (whose differences can only be seen during opening airstrike CI--the planes--and the battle result screen--the kanji names) exposed how lacking we are when it comes to alternative data collection methods. Not to mention the complexity of large scale event and hidden mechanics exposed how ineffective our current data validation system is.

These are the three tasks I suggest