What is the recommended way for subdividing system requirements into Confluence pages?

[mickey13]

Is the Product Requirements template better suited as a comprehensive set of system requirements, or is it more effective to create a Product Requirements page per feature for a reasonable sized project?

I like the idea of breaking out major system features into their own child page as a Product Template, but we'd also need an easy way to export all system requirements into a single document, so possibly over many Confluence pages.

Thoughts? Thanks.

[BillA · Accepted solution]

I'd say do what works best for you. You can always export your pages into one PDF document by doing a space export and choosing the Custom Export option to export a subset of pages.

See docs at https://confluence.atlassian.com/display/DOC/Exporting+Confluence+Pages+and+Spaces+to+PDF

[mickey13]

Do most people just put all of their system requirements in one Product Requirments page?