Thomas Crombez on his Doing Digital History site has a post on Publishing scholarly projects using Google Sites « Doing Digital History. His argument and instructions make a lot of sense. The idea is that you use something like TEI to encode your scholarly data and then you publish it on Google Sites instead of setting up something fancy at your university or lobbying for research infrastructure that doesn’t exist. Google provides stable infrastructure that you don’t have to maintain at an unbeatable price that is “off-campus” (which can have advantages) and which is as likely to survive as a university service.
Either way — running your website on a university server, a private hosting solution, or your own server — you are basically into self-publishing. Will you use an established platform aka CMS (Content Management System, e.g., WordPress or Drupal) or do you prefer to grow your own HTML/CSS? What is the most advantageous and flexible place to host it? If you run your own server, when does it need to be updated? Do you really need that latest Apache update? If you are doing a dynamic website, will the database continue to behave as it does today? When to update your database software? Is it possible that your website will one day attract a lot of traffic, necessitating more than one server? What search engine do you use for your collection of texts? Do you simply plug in a Google search box, or do you want some more searching power for your users? If so, what software do you choose?
I see more and more people moving to Google (and other commercial solutions) as a way of doing projects quickly and with modest resources. I call it Computing With The Infrastructure At Hand.