Neighborhood website
"No matter how cold the winter,
there's a springtime ahead"
I've been elected to build the website for my neighborhood association. For those keeping count that's 2 fully developed websites completed, and 4 websites in the works. The one's that are in the works are 2 neighborhood organization sites, 1 company site, and 1 "super-secret" site that's for a writer.
All this, and I still refuse to call myself a web designer. A buddy of mine is helping me with the PHP and SQL work, and I am probably going to go with his recommendation and pick up a couple of PHP books. The main thing I'm concerned with is that my community site needs to have a back end for others to go in and update. The other's are wanting it that way. If it were up to me, I'd keep it with static HTML pages. It's been my experience that using a template to generate pages isn't always aesthtically pleasing. Most of the time the pages end up looking like shit because there's only so much you can do. A great example is MySpace. Design-wise they look like shit. That's mainly because they are based on stock templates. Oh well. I think I'm only going to have two pages on the community site that are PHP driven. The rest will just be info that will remain the same at all times [history, links, etc].
Hold on a sec, the tape holding my glasses together is coming undone. *snort* ;)
Until next time:
"They say a year in the Internet business is like a dog year.. equivalent to seven years in a regular person's life. In other words, it's evolving fast and faster." - Vinton Cerf
there's a springtime ahead"
I've been elected to build the website for my neighborhood association. For those keeping count that's 2 fully developed websites completed, and 4 websites in the works. The one's that are in the works are 2 neighborhood organization sites, 1 company site, and 1 "super-secret" site that's for a writer.
All this, and I still refuse to call myself a web designer. A buddy of mine is helping me with the PHP and SQL work, and I am probably going to go with his recommendation and pick up a couple of PHP books. The main thing I'm concerned with is that my community site needs to have a back end for others to go in and update. The other's are wanting it that way. If it were up to me, I'd keep it with static HTML pages. It's been my experience that using a template to generate pages isn't always aesthtically pleasing. Most of the time the pages end up looking like shit because there's only so much you can do. A great example is MySpace. Design-wise they look like shit. That's mainly because they are based on stock templates. Oh well. I think I'm only going to have two pages on the community site that are PHP driven. The rest will just be info that will remain the same at all times [history, links, etc].
Hold on a sec, the tape holding my glasses together is coming undone. *snort* ;)
Until next time:
"They say a year in the Internet business is like a dog year.. equivalent to seven years in a regular person's life. In other words, it's evolving fast and faster." - Vinton Cerf
0 Comments:
Post a Comment
<< Home