Lately I’ve been working less on code and assets, and more on the organization side of the project. Building a game the size of Dooms Day Delivery Service needs more than just cool ideas and sketches—it needs a system to keep everything straight. That’s where Confluence and Jira come in.
What is Confluence?
Confluence is basically the studio’s wiki and documentation hub. It’s where I can write up design notes, outline story beats, list mechanics, and keep reference material all in one place. Think of it like the game’s living design bible—a place where every idea has a home.
What is Jira?
Jira is the task tracker. It breaks the big vision into smaller, doable pieces (tasks, subtasks, and epics). For example, instead of just saying “make a demo level,” Jira lets me create subtasks for blockouts, hazards, pickups, lighting passes, and so on. That way, progress is visible and I can check things off as they get done.
Why use both?
Together, Confluence and Jira help me balance the creative chaos with actual structure. Confluence is where ideas live and grow, and Jira is where those ideas turn into action items. Since I’m basically a solo dev at the moment, this setup helps me stay focused and gives me something concrete to point at when I share progress with you all.
From here, I’ll be bouncing between polishing core systems (like the drone) and laying out the demo level, while keeping the bigger picture organized. It’s not flashy work, but it’s the foundation that makes sure all the flashy stuff has a place to land.
Status: Confluence filling up. Jira boards populated. Organization systems: ONLINE.
No comments:
Post a Comment