I want to use WordPress as a CMS for a reasonably basic site rather than a blog. I have several pages and at the moment, I don't intend to have a "news" page.

While there are ways to make this work, the focus in the wp-admin console is clearly on new posts, and creating pages with custom content like maps and galleries feels like I'm working around the system rather than with it.

Do you have any suggestions as to using WordPress as a CMS?

Specifically:

Are there any good boilerplate themes that are designed around a CMS rather than a blog?

As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
If this question can be reworded to fit the rules in the help center, please edit the question.

9 Answers
9

The killer feature that caused WordPress 3.0 to cross over from an extensible blogging tool to the CMS for 8 out of 10 needs is Custom Post Types (with the addition of Custom Taxonomies from v2.9) with an honorable mention going to the new Menu system in 3.0.

So if you want to learn WordPress as a CMS then study Custom Post Types. Here's a few articles to get you started:

As for Themes, that's a different subject. While blog themes all implemented the same use-case pattern, each person's CMS needs are likely to be different because each business is different (a restaurant needs different layouts than a yoga studio than an movie theatre than a fabric store.) At least early on I think you'll be hard-pressed to find the perfect ready-made "off-the-shelf" theme for your business; best to find one that's generally good and plan on modifying it or get a WordPress designer to build you a custom one. Having them layer on top of themes like the Genesis Framework from StudioPress can be a good option.

Best I can suggest is to look for ones that support the WordPress 3.0 menu system and then make your decisions from there. You can google for that and look for articles like this one:

P.S. If you are asking about streamlining the admin user interface so that the Posts and Pages and other blogging tools take a back seat and your specific CMS content is featured in the admin instead then that's a different subject; can I suggest you ask another question for that one?

UPDATE: Here are some screen shots from some projects I'm working on to give you an idea of what can be done:

@Mike: The screenshots are awesome! Can you share the way doing this (scripts, classes or plugins, etc.)! Thank you very much.
–
RilwisJan 17 '11 at 14:43

1

@ozke - Thanks for commenting. That's really another question and it's better to ask a new question than discuss side issues in comments. Please post it as a question so that I or others can answer it in depth potentially with links and/or source code. Be sure to include details and maybe link to my answer on this page if you like.
–
MikeSchinkelJan 21 '11 at 0:44

If custom post types are too hard to manage for you

Take a look at the famous "pods" plugin. it has a lot of Killer features and there's some "add-on" or child plugin called "pods ui". Pods itself allows you to add any sort of table(s) to your DB. It also allows linking them to existing wp DB tables. So if you want to (for ex.:) extend the data saved with an user, you just add a pod named ex. "extended userdata" and link it to existing user data. That's it. "Pods UI" then allows you to make a nice user interface with close to no effort.

Both help you to easily manage and build everything you might need. All of the developers are more than just nice, they have a perfect forum and you can meet them nearly every day in their irc-chat room. I build myself two pretty large sites for managing events plus the whole background organisation and i'm still impressed how good it is performing even when you got hundreds of visitors at the same moment. :)

Firstly, WordPress is still great for small(ish) sites whether or not they make use of a blog section. It's easy to use, easy to find help with, and of course there's the scope for easily adding a blog if it's needed in future.

Alternatively there are a lot of themes out there geared towards a certain type of site, be it portfolio or photography or whatever sort of site you're looking for. I'd recommend a look around places like Theme Forest.

As mentioned in previous answers, Custom Post Types are definitely worth checking out, especially combined with the WP Easy Post Types plugin. However, I would still recommend giving the Magic Fields plugin a look over as it offers some extra custom field options that can be quite useful. I can see WP Easy Post Types improving and making plugins like Magic Fields unnecessary though, but it's still worth checking it out. One thing to be aware with Magic Fields is that it does store images in a different location than the standard uploads folder which is a bit of a pain and definitely an area where custom post types wins.

It's definitely very usable for smaller sites that have few editors. Some of the issues you may run into with larger sites, not all of which we have resolved yet:

Customization for individual groups/users. We are using the WordPress Network feature to give individual blogs to different departments/groups, allowing some settings to be set per-group. We also developed the 9spot plugin which replaces layout via templates with layout via widgets, giving each blog the ability to set custom columns per page type, category, etc. in the dashboard.

Development vs. production instances. With our old CMS, you could edit content and push to the development server to check things before they went live. We have less ability to control content at this level in WordPress, and it's a little cumbersome to move content between the dev and prod instances. Likewise, many settings (i.e. widgets) are hard to move between servers.

Locking down content. Aside from creating a new blog, we can't lock down editing privileges to a specific subset of users. We'd like to extend editing privileges to specific pages to individual users or user groups.

I think it's all resolvable with enough development time and/or third-party plugins, but those are some things we're struggling with out of the box.

The best way for me is to set up a small site, fast and specialy for the requirements of the customer. Also i reduce the backand only for the view, how use the customer, less ist more. Also i write small plugins and use not great "click and do" plugins, maybe for custom post type, write this in a solution for the customer. For reduce the backend i use own source or the plugin Adminimize. I check hte install also for functions, she comes from the core and maybe she is not important or necessary. I deactivate this functions, as example the feed.