Welcome!

[brad_langdon]

Ok,

When I create a site I open a basic template that I have created that consists of a css file an index page and a few php inserts for the header, nav and footer.

It works fine and I am happy with it but I keep seeing posts / comments on the net saying that all websites should be dynamically loaded etc and all content on pages should be database driven, so on and so on.

How does everyone else setup a basic site. I dont want to use a CMS like wordpress or joomla. I looked into CakePHP but apparently you should not use it unless you are creating a blog, forum etc. Here I was thinking CakePHP was a basic sort of framework that you can add features to.

I need help deciding the best way to do things, I have created sites that pull info from databases before but it was still all hand coded.

Help from anyone expereinced in this topic is very much needed

[sydneycraig]

dynamically load from a database and use some CMS if thats what is needed.

people automatically assume a CMS is the way to go but often its really not justified.

[jock]

If you/your clients don't need 'dynamic' content then a CMS its quite pointless unless you want to oversell something. I've got my own CMS build off Zend Framework, I use that as a skeleton for each site. Its not like an out of the box solution like Joomla, it requires a fair bit of manual configuration but it works for me. Even if they don't use it to update their website it certainly makes it easier for me to update.

[Zim]

I do whats needed for each client, simple realy.

[Parallax]

/agree

If it's quicker/easier/simpler/better to do it old school, then do it old school. Time is money, friend!

[Andy]

I agree with the posts above.

However, one reason I could see for you tot consider placing your posts in a database is if you intend your site to change in the future. If you intend to support dynamic interaction in the future then it would definitely help if the data is already in the database.

[Herbert]

It all depends on the client and what works for one may not work (make sense) for others.

[Ruge]

I tend to list what my client wants and just perform what is required to appease them. If static pages are required then thats all I will design. I would not engage in designing something that requires a longer time frame to complete as my clients are requiring their sites to be done with minimal cost (So I guess I'm being honest in that way )

Designing static pages has its benefits however. If you are working with a client with zero expertise on design you can be assured they will pay you to modify/add pages if required