Does your historical collection need a database-driven website?
There are plenty of good reasons for building a website for your collection, including learning a new skill, protecting fragile resources from constant handling in the archives, adding interactive functionality that is only possible on the web, and opening access to users who cannot visit in person. But often there are better ways to share your collection. Websites are expensive and a lot of work. Committing to building a website is like committing to build and maintain a library for the foreseeable future. If you're reading this, you must already be enthusiastic and have a great idea. This flowchart is not meant to dampen that enthusiasm. Instead, it is written to make sure you ask yourself some of the tough questions too, to make sure your project is viable before you make a big commitment.
Published inDigital Humanities Quarterly