I have a need to take the email list archives from a membership organization and make them available in a searchable form to the membership only. Obviously, OpenACS is ideal for the controlled access requirement, paired with HyperMail, which can take the thousands of messages and structure them. Hypermail is especially useful in that the historical emails are still being searched out from members, and its capability to incrementally add material and reindex is ideal.
My first cut at this was to divide the archive into years, process a test year with Hypermail, create hundreds of individual HTML files plus index files, and upload a zip archive of the resulting directory into the File Storage module. However, this approach produced extremely slow index file (~125 Mb) retrieval times, whether the files were stored in the database or the file system. This could be addressed by dividing the archive into quarters or months, but this increases the complexity of performing incremental updates and of maintaining a set of user-friendly links into the File Storage area directories. Another drawback of using File Storage is that is it cumbersome to delete hundreds of individual files.
A better approach would seem to be taking the files generated by Hypermail, copying them to the web server filesystem, and registering them with OpenACS so they can be indexed by OpenFTS. In OpenACS 3, I would have accomplished this with the Static Pages application. In OpenACS 5, though, I am confused by the various alternatives: Basic Content Delivery System, Basic Content Management System, BCMS UI, BCMS UI Wizard, and so on. I've searched the Q&A and CMS forums for advice, but most seems targeted toward package developers rather than to those trying to use a vanilla system and avoid customization whenever possible.
Can anyone point out documentation or provide advice that would more directly address my problem, give me a better understanding of the content management options, or otherwise help me crack this nut? TIA