cms advice for a designer
Out of context: Reply #8
- Started
- Last post
- 22 Responses
- vaxorcist0
surrealcms looks interesting... better approach than most.... probably good for a designer.... I'll actually try it....
Most agencies have a workflow that makes using a pre-existing CMS hard. Why? Agencies like to approve designers photoshop screenshots, then figure out how to make the content editable. But most pre-existing CMS's work better the other way around, where you see what the CMS can do, then design around that subset of what you may really want. Most pre-existing CMS's also have lots of stuff you don't need or want.
So, being a developer/designer, I tended to roll my own CMS, based on a bunch of code I'd tested in the past, and using xinha for editing.
I'm looking at Concrete5 now though... it seems most easily redesignable, I dislike Drupal, as you have to retrain your brain according to Drupalism's mindset....
The central problem of CMS's seems:
1. if very simple, then maybe not quite what you want
2. if very customizable, then lots of irritating exessive layers of stuff to configure, as it's so generalized that it's full of extra-ism and you have to learn the CMS's idioms....WP is good, very good for what you can do with it, and often the best solution, as especially for low-budget jobs, you can make a pretty good site by taking a pre-existing template and tweek it so it looks completely different but works nicely.