Using one Confluence Space by Artefact Version or one per Artefact

[Dirk Bromberg]

Hi,

we plan to use Confluence for Software Documentation.

Is it better to use it like Atlassian Style: One Space per Artefact Version.

Or is it better to use a Space per Artefact and then add all Versions to this Space?

Creating a new Version by copying an old subtree...

Is there a good documenten way for beginner? Video? Tuturial? Book?

Thanks!

Dirk

Next Step after Documentation an Requirements in Confluence is Setup of JIRA....

[David at David Simpson Apps · Accepted solution]

The answer is likely "it depends". Whatever works best for you.

Having said that, Atlassian's usage, where they copy the space for the next version does seem to be a good example.

One space per version means that any search within a single space (if you're using the space specific search box in the Documentation theme) is guaranteed to be specific to that version (assuming the documentation is correct).

Also, if you have all versions in a single space, you can't have multiple pages with the same title. This may prove to be a problem.

[Dirk Bromberg]

I'think we will start with one space per version. Thanks.

[Dirk Bromberg]

Hi David,

thanks for this answer.

Is there a simple way to search over all spaces?

Thanks.

[David at David Simpson Apps]

@Dirk Bromberg: Do you mean all spaces, or all spaces for your product's versions?

The former is easy (try the search in the breadcrumb/header bar).

The latter, is also achievable -- try this search for "Upgrade" in 2 Confluence spaces. You'd like need to make your own user macro to get a decent form displayed.