How can I organize and manage a full Plants vs. Zombies tips & tricks guide using Confluence or Jira

[Henry Roy]

Hi everyone!

I’m working on creating a detailed Plants vs. Zombies guide that includes breakthroughs, tips, and strategies, and I’d like to structure it in an efficient, collaborative way. I was thinking of using Confluence or Jira to organise the content, track progress, and manage updates as new versions of the game come out.

Has anyone here used Atlassian tools for gaming-related projects, fan guides, or similar content management before? I’d love to hear your suggestions on the best setup, templates, or features that could make the process smoother.

Thanks in advance for any insights!

[gents peak]

I’d probably split the guide into sections for plant combinations, level strategies, useful tips, and changes between versions. Confluence would be handy for keeping everything organized, while Jira could help track which parts still need testing or updating.

That approach makes a lot of sense for fan projects like PvZ Fusion, where new versions can change things over time. I’ve also been looking through Spanish PvZ Fusion resources and came across this website while checking different versions and game information. Having a small changelog for each section would make it much easier for readers to know which tips are still relevant.

[PVz fusion android]

I've actually done something similar for game notes, and Confluence worked much better than Jira for the actual guide. I created separate pages for plants, zombies, game modes, boss strategies, and version changes, then used labels so everything stayed easy to find. Jira was more useful for tracking what still needed to be updated whenever a new release came out. 
One thing I'd recommend is keeping a changelog page. PvZ Fusion updates, for example, can introduce new mechanics or balance changes, so having one place to track what's changed saves a lot of time. I usually compare new versions using this PvZ Fusion resource before updating my notes. It makes maintaining the guide much easier over time.

[jovanda higgs]

That’s a solid idea—Confluence works really well for structured guides, especially if you break things into sections like plants, zombies, and strategies. Jira can help track updates, but it might feel heavy unless you're managing a team. Keeping templates simple is key.

At https://pvzfusionfree.com/ organize content by versions, features, and gameplay mechanics, which makes navigation easy. They separate updates, plant guides, and modes clearly. You could mirror that structure in Confluence spaces and use labels for quick filtering.

[Mike - Dreamsuite Consulting]

Hi @Henry Roy 

I want to always suggest the Best Fit solution for people based on the information provided and being completely honest, unless you are already entrenched in the Atlassian ecosystem already or you really want to be in the future, it may not be the best option.  

That's not to say it isn't an option.  Here are my top 3 options assuming you aren't in the Atlassian Ecosystem already:

1. Notion - Perfect for Guide Content & Knowledge Base type docs and you can couple it with management of projects
2. Google Docs - Often the best tools are the ones you and everyone uses and Google Docs could work just fine
3. Confluence - Confluence rivals Notion for sure, it is certainly a bit more formal and corporate feeling.    
   Bonus: A combination of Confluence and Trello would work really well

If you are in the Atlassian Ecosystem already, I would still say that the combination of Trello and Confluence may be the best fit. Jira seems like an over-engineered option for this.  Unless you are wanting to learn Jira, I wouldn't recommend it for this use

[Nikola Perisic]

Hello @Henry Roy 

Confluence would be great for patch notes of the game which will be connected to a Slack channel that will notify all users in that channel for new releases. For new released versions you can use Jira to track them and also to create release notes. 

Are you following Agile methodology? If not, you can use business projects instead. If yes and you want to keep everything simple, you can use team-managed project for this.For Jira, I would recommend keeping workflows simple to use, lots of statuses can cause confusion, keep it simple.