![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png)
The A.S.S. (the company behind the recent production of A Midsummer Night's Dream in which I played, about which I really will do a longer post asap) is talking about putting together a website, and I've volunteered to help.
My instinct is to design and code the thing from scratch, like I did for the Second Shift site, but I'm beginning to think that that's old fashioned (or is it?). For a site that doesn't need to do anything special, just text, photos, and videos, should I just deploy a CMS and be done with it? If so, which one? I kind of like the Stranger Ways site, which
natbudin put seemed to put together practically overnight with WordPress, though my ideal would be extensible using Python instead of PHP (though that's just a preference-- can do PHP fine).
Anyway, suggestions?
My instinct is to design and code the thing from scratch, like I did for the Second Shift site, but I'm beginning to think that that's old fashioned (or is it?). For a site that doesn't need to do anything special, just text, photos, and videos, should I just deploy a CMS and be done with it? If so, which one? I kind of like the Stranger Ways site, which
![[livejournal.com profile]](https://www.dreamwidth.org/img/external/lj-userinfo.gif)
Anyway, suggestions?
no subject
Date: 2011-06-21 01:51 pm (UTC)no subject
Date: 2011-06-21 01:57 pm (UTC)no subject
Date: 2011-06-21 03:36 pm (UTC)1) Saves time
2) easier to hand off when you eventually do.
3) Reinventing the wheel means reinventing all the bugs other things have already solved, which is a big security nightmare.
Third party open source products are sufficiently capable and attractive and usable that there is almost no good reason to build by hand, no matter how satisfying that might feel as a project.
no subject
Date: 2011-06-21 02:17 pm (UTC)I've also heard good things about Drupal, but I know pretty much nothing about it. I think