Home

Welcome to the DemolitionX-Jam wiki! We will document relevant information needed by existing or new contributors here, including any knowledge transfer relevant to game development. Please try to maintain a high-level hierarchy that's easy to fully understand by every member, so that any domain-specific knowledge requiring further specialization is hidden by default. When writing pages deeper in the hierarchy, try to keep pages with a simple overview separate from more detailed beginner tutorials, so it's always easy to understand if the page should be kept as simple as possible (bullet points, steps, links, brief descriptions), or if it's correct to let your imagination run wild, while being as detailed as possible! :) Feel free to suggest any changes or additions to the structure that you feel may be useful, and we'll decide based on consensus in our team. Right now there isn't any fixed structure, but this may change in the future once our wiki grows, so if you have any feedback, try to provide it as soon as possible! :)

• Onboarding - The introduction for new team members, including all technical details of our process, along with information about project goals and motivations
• Game Design - Our current Game Design Document that should serve as a Source of Truth for all members
• Planning - Overview and guidelines related to task planning (Tasks are in the form of a Kanban board in Asana), under the responsibility as a team leader
• Development - Initiatives regarding game development, including Unity-specific tasks, programming of core modules, UI, integration, and the multiplayer aspects
• Art - Initiatives regarding visual graphics, 3D modeling, map/scene organization, and the music composition along with sound effects
• DevOps - Initiatives regarding supporting developers by CI/CD (running automated tests, building the game), hosting the server or websites, setting up environments
• Quality Assurance - Initiatives regarding testing the game, reporting bugs, preventing issues, ensuring correct dependencies
• Public Relations - Networking for purposes of collaboration or any forms of advertisement
• Business & Marketing - Details and routine steps used by our business processes, including both the investments and generating profit
• Meta - Just like this wiki organizes all current processes, the process of setting up and improving the efficiency of processes themselves has its own place here

As an experiment, I suggest to also try a use-case driven, intention-based structure under each category, so that instead of only documenting critical information, you can document your approach in the form of re-usable actions, which other members may also want to execute in the future. For example, when you start to work on something, you define it as generically as possible, and then track your steps along with any points of decision. That way you can also leave an incomplete task (intention) with a description of why and how you want to do something, and have other members look at your approach, filling in any details or pointing out a better solution to the same problem. This way our documentation will grow, collecting any knowledge found along the way :)