Thanks for all the replies! Tesla and Pyrite, you have both answered my primary quetsion pretty well. I spent quite a bit of time learning layouts in CSS a couple of years ago and am pretty confident with my ability to create "templates" with HTML and CSS. My main weak point is server side scripting like PHP and knowing how to leverage it for dynamic content like images and blogs.
I think I still need to experiment more with PHP itself and with prebuilt CMS programs to see what would best suit my needs. Currently, when putting a site together, I take one of my templates (I have about 4 or 5 decent layouts) and create a directory structure like so (using a three page example):
/ <- contains index.html
/script <- contains CSS, Javascript, etc
/images <- contains all images used
/about <- contains index.html
/contact <- contains index.html
I basically just copy the index.html from root to any other subdirectories I have created for other pages, update the relevant location of the scipt and images directories and then make changes to the title, content, etc.
It's somewhat tedious, but it's quick for me now that I've done it a bunch of times. I use the Bluefish editor in Linux, as it has cool features like tabs, auto-complete, and some other handy tools.
What I was hoping to gain from a CMS program is to have the ability to use a single set of style sheets to quickly generate multiple pages (instead of making multiple copies of index.html) with the same theme. Additionally, as the term "Content Management" suggests, I'd like to be able to manage changing content easier.
One thing I pondered was dropping in "modules" for the pages that would most likely change, such as a blog page or an image gallery page, continue using my current method for generating layouts, but at least have some minimal content management.
My main question really was intended to see what everyone else was doing to accomplish similar goals.
- Pickins