Hello,
I’ve been working for Modx (Revo) for a few weeks now, trying to get a feel for things, and honestly I’m a bit overwhelmed. I’ve figured out most of the basics - ie templates, snippets, chunks, TVs. But now I need to tackle some more specific projects and am not really sure how to proceed. For instance, I would like to create a document library for our site with well over 100 documents (mostly PDFs, but not all), organized into categories. Now I realize I can create a static resource for each document, but is that really the best way to proceed? Is there already something available for this purpose that I haven’t found yet?
Any direction would be greatly appreciated.
Thank-you!
LadyHLG
You could certainly do them all with static resources and use Wayfinder to create a menu for them. If you need to restrict access to various groups of them, that would probably be the way to go.
Another way would be to organize them in directories on the disk matching the categories (with filenames that would serve as link text) and write a custom snippet that would read the directories and create links to them.
BobRay,
Thank-you for the reply! Unfortunately the snippet build from the files wont work as I will need more direct control over the how the documents are listed. So the static resources is probably the way I will go.
There is a part of me that is really fighting this approach. I keep thinking I should be setting up a separate database table to organize them. At what point does that become necessary? ie - using the built in ModX functionality such as the static resources vs a custom table with database interaction? At some point will I have to watch out for performance or usability issues? Keeping in mind that this is going to be a fairly large site, aside from the document library we will be setting up a video library, news section, probably 100 or so pages of content and other dynamic areas that will require custom database tables.
Thank-You again for your insight.
LadyHLG
I don’t think you’ll see significant performance issues until you get to at least 500 documents (though I could be wrong).
It *is* wasteful to carry the overhead for a resource along for each file, but the convenience is probably worth it if there are less than 200 of them and you need to use ACLs to control access to them.
