[CentOS-devel] Website Version 2, next steps

Tue Mar 1 20:29:40 UTC 2011
Andreas Rogge <a.rogge at solvention.de>

Am 01.03.2011 21:09, schrieb Steve Meyers:
> I guess that's why I don't like to use CMSes. I like to have more
> control over layout and such, and I find I spend less time doing my own
> CSS and HTML than I would trying to get my CSS to work within the CMS
> CSS. The more customizing you do with the CMS, the more problems you
> potentially have when you do upgrades in the future.

That's still the "wrong tool" problem i was talking about. Don't use a 
CMS that puts its own CSS onto your page. Its job is to manage content 
not design.
It is absolutely ok if you write the page template from scratch. But 
design, code and content should be separated so you can replace each of 
them without having to think too much about the other two. Using a 
ready-made solution makes sure that:
- the code/content/design-separation is there
- the libraries used are known to work together
- you don't need to hack around getting RSS import or whatever to work
- you have an upgradable vendor-provided codebase (which you should 
never touch)


Solvention Ltd. & Co. KG
Egermannstr. 6-8
53359 Rheinbach

Tel: +49 2226 158179-0
Fax: +49 2226 158179-9

mailto:info at solvention.de