I wish I'd known more about Drupal when I left a job a few years ago, since I think it would have been easier than most CMSes to do a conversion for their largest site.
Here's an idea for a module (maybe something along these lines exists?): * Move the old static site to a specially named folder * Hook into the menu/path system and, if there isn't a defined Drupal path for a given URL, check the static folder (perhaps allowing for derivatives (foo, foo.htm, foo.html, foo.php, etc.) and serve up the static page until it gets replaced * Log hits to static URLs to provide a handy tool for helping prioritize which things to convert sooner
Scott
On 5/17/07, Sean Effel sean@crushyou.net wrote:
On 5/17/07 9:51 PM, "Emmanuel Gandelman" makopolok@gmail.com hollered:
Hi Emmanuel,
I've got tons of experience converting small NPO sites from their traditional straight HTML to a Drupal platform. From what I can tell from a quick look at your site, I think it would be a pretty simple task and probably open your site up to a few basic features that will make your life easier. Your site is as straight forward of a conversion as they get.
Between the standard node system for publishing new articles, and maybe taking advantage of the member and profile modules, you'll cut back a lot of your administration. The addition of the standard Drupal RSS will also help you push your content further out. Posting photos to your articles would get easier as well, with the CCK or just plain Image (with image_attach) modules. Posting new content to the site will feel just like writing an email if you build it right.
But I can't comment on Hebrew text generation. I have never used Drupal to publish right-left text. I know lots of people have done so, maybe they can comment here, I would like to know as well.
Good luck,
Sean Effel http://www.drupaltherapy.com
-- [ Drupal support list | http://lists.drupal.org/ ]