Fundamentally, the PageSeeder architecture is that members create, and then edit, documents, fragments, URLs, comments, and tasks. All current and historical content is connected by groups. Every interaction, even editing a single letter, represents a number of connections.
In PageSeeder, no information is free from dependencies on other information.
The archive folder gives PageSeeder a location that it can use to both store obsolete information and filter it out of search results and other aspects of the interface. The reason it is important to store the information is so the integrity of the connections are maintained. For example, even though part of a document might no longer be required, it might be the target of references from other documents. In conventional publishing systems, if a document was removed those references would break. With the PageSeeder archive, it is possible to still recover the archived information so the authors can decide to remove or redirect the references.
The integrity of the connections is why the “delete” feature requires special configuration to access.
The PageSeeder user manual
© Allette Systems (Australia)