I’m using Revo 2.0.7 to run a site for a client that features around 300 separate ’documents’ (mainly PDF and videos). These documents are currently set up as individual Resources, so they are managed in the Resource tree. I have TV’s controlling document properties. When my client wants to publish a new document, they create a new Resource and select the various TV options - e.g title, intro, publish date, document type, author, category, region and so on. The website displays the documents in sorted lists of PDFs, videos etc with the file either opening as a separate window or in a player. Website users can filter the documents using drop-downs. The drop-downs tell getResources (via AJAX) to search the 300 documents for ones that match. It works fine, but I’m concerned as the volume increases that the Manager will start to struggle and become a little cumbersome to use.
Is this the best way to run a document-focused site in Revo, or would it be better to use some kind of database table that holds the doc info and then create a Manager page that allows my client to manage the table (rather than using the Resource tree)?
I’d really welcome ideas/views on this as it will become a critical issue in the coming year.
