Requirements Document. Where should I start?

[Ben Butler]

I am looking for a clean place to put requirements document for an application. The team is new to confluence, but I want confluence organized, intuitive, and scalable so I do not end up with a mess as we expand on its usage.

Help would be appreciated, thank you.

[Damian]

Hi Ben,

I agree with Jack. It's a pretty broad question. For the requirements documentation itself (once you've designed a Space structure), you could look into creating your own template based on an existing format that you use (or want to use) or you could use one of the provided ones like this: Product Requirements 

If you start off using templates, then you'll have some basic level of consistency for your pages. Templates may change (especially custom ones) but at least you can build their usage into your documentation process.

[Jack Brickey]

Hi Ben, that is a pretty broad question to be honest. I don't know if you're looking for some introductory training on Confluence that might result in better decision-making about creating an effective space for your team or maybe something different. I guess that I would suggest starting with the documentation and then also I would refer you to Atlassian university for some good training some of which is free. Finally, at least for me, I wouldn't overthink it because you can easily change things within the Confluence world.

if there are some more specific questions feel free to chime in here and I'll do my best to provide my thoughts.