| 7:40 pm on Jul 20, 2005 (gmt 0)|
The approach you've outlined is the approach I take. In effect using PHP itself as my CMS. It gives you ultimate flexibility but you have to exercise self-discipline and not let your setup get too complex.
| 8:00 pm on Jul 20, 2005 (gmt 0)|
|have just spent a couple of hours teaching myself css and am coming to the conclusion that I may be better off using css for the look and feel |
Whatever you do with the CMS, your time learning css was a good investment. That is a big help build and maintaining a site.
| 3:27 pm on Jul 24, 2005 (gmt 0)|
In my world (the Java/Servelet/JSP one), you have hit on something that everyone of us should be following. We know it as MVC... however the theory is the same and applicable to most websites:
Separate your web app into:
Data (data structure... DB/flat files/CMS)
Business logic (rendering engine, the actual application)
Presentation (rendered by the browser & CSS)
This kind of architecture is superb. For example, I have all of my data in a database, in XML. Depending upon who visits, determines how it is rendered. For example, I might chuck out XML if the user agent supports it, or HTML, or XHTML. I can also provide good fucntionality like exporting any bit of content to PDF (XML->PDF).
The 3 layered approach means that if I need to change presentation (in CSS) then I can just do that and not worry about data or logic. Also it's very useful for trying to comply with W3C guidelines. The last thing I wanted to do was start going through a few thousand JSPs trying to work out where horrible bits of code comes from.
In *theory* if I wanted to go from say... MySQL db to say Oracle, I can simply by mirroring the data structure and changing the common connection. Another great prospect - separation of your code can mean flexibility and scalability.
So in summary: I know this as MVC, however its theory can be (and should be) applied to all web apps.
| 4:23 pm on Aug 1, 2005 (gmt 0)|
Using CSS properly can replace one of the things that people use a CMS for. But visual appearance isn't the only thing that you can do with a CMS. I use mine to autimatically generate submenus and will shortly have it automatically writing my sitemap along with a few other handy features.
Use your CSS to handle the visual component of your site and use (I mean really use) the CMS to deal with the content structure of your site.
| 5:20 pm on Aug 11, 2005 (gmt 0)|
I'm curious what MVC is or stands for?
| 9:39 pm on Aug 11, 2005 (gmt 0)|
MVC stands for Model View Controller and it is a design pattern for separating an application in to its separate components. It has been applied to many areas.
For a much better description, look up mvc on wikipedia.
| 4:18 pm on Aug 12, 2005 (gmt 0)|
As I said previously I have just spent a couple of hours teaching myself css and am coming to the conclusion that I may be better off using css for the look and feel and just using a good file system to organize seo'd static html pages. I can always add in the forums, emailing list managers, etc on an as needed basis and for the most part without a CMS. Am I wrong in this thinking?
Basically I can add in all the bells and whistles php / programming items to run in the background after I set up my site appearance up with css. If I have the look and feel controlled by css and add in functionality as I go it gives me a lot more control over seo as I see it because I tell it from the get go what it shows the engines and the users. I see no need for a packaged CMS as I am essentially creating my own simple CMS.
I can easily create scripts to manage those funtions you mentioned. The only time I see it being a problem is if I bring in other people who don't know what they are doing code-wise to add content etc.
Again if I am wrong anyone who can tell me why would be appreciated.
| 4:24 pm on Aug 12, 2005 (gmt 0)|
You are correct in your thinking.
A custom "mini" CMS is the best option by a margin, if you have the time and ability to create it (and keep it secured and up to date).
Many webmasters don't have that time or ability, hence CMS's can be very useful.
|The only time I see it being a problem is if I bring in other people who don't know what they are doing code-wise to add content etc. |
If/when you reach that point you'll probably just build another little script/page that lets users add content in plain text in a form-filling exercise. It's very easy.