Structure of projects and sites in confluence

[nibeck]

I'm trying to wrap my head around the best "structure" for our numerous projects and tasks.

Say I want to manage multiple projects such as:

1 - Mobile App 1

2 - Mobile App 2

3 - Media Services (larger, complex app)

- Asset Mgmt Web App

- Player Componnet

- API

- Data Ingest

Questions:

1 - Are these "Sites" or "Pages"

2 - Should a create a single "Mobile Dev" area/site and have two projects

in it, or should we just have separate sites for each app?

3 - Media Services is the entire project but it contains distinct

development efforts beneath it (API, player, etc.) Each of those sub

projects needs a dedicated Source repository, but we would need a single

Ticket workflow under the top level definition, because the user creating

tickets may not know which sub-component is causing the issue.

4 - How will this map to Jira?

Does this make any sence?

Can you folks recommend a first approach to the overall structure given

this scenario?

[Michael Bostwick · Accepted solution]

You can create the pages however you want (you can always move a page,to where it makes sense ) . A big thing to keep in mind with spaces is how do you want to administer the spaces. Templates are also on a per space level. Its more about how the pages and spaces are going to be updated vs what content goes into them. Also, what you want people to be able to see.

Jira integrates on a per page level, so you can do what ever you want with out concern with integration (unless you write custom plug ins or scipts that does something with the the setup..).

You know your end users and your org better then anyone on here, so it will be hard for anyone to tell you whats going to work best.

Also if you haven't you should have a look at the docs about organization found here.