My team and I are running into similar challenges.
Some ideas/solution to mitigate, but not solve the situation:
1) In an external lifecycle management tool (e.g. Jura, Rally, etc.), each User Story (US) would have a link to the relevant page in the AxShare repository.
2) Take feedback and approvals from clients on the AxShare platform. Once clients put an "APPROVED" comment on a page, we regard it as approved. To mark it, we add the string [APPROVED] to the beginning of the name of the page. Once a page is approved, we do not make any further changes to it.
3) Each iteration or spring would have it's own folder, with just the pages that were updated. The great con of course is not being able to find older pages. It also makes it hard to understand what the latest and greatest version of each page looks like.
4) We are considering creating a fresh copy of the entire system for each release. That would solve the concerns above, but would create new difficulties, such as enormous project files, and also hard to see what was updates in this release or iteration.
Any thoughts or ideas how to overcome this?