Does anyone have any good examples of using Wordpress as a CMS? I've found a few here and there, but was wondering what can be done by someone without a budget for webdesign. What have my fellow DPers done with Wordpress as CMS. Anyone care to share?
Wordpress is a CMS. So asking to see sites using wp as a cms would include all of them... What specifically are you looking for? The best example that I run is www.stablewoodfarmshoa.com That's not saying it's great though. Here's a list of large corporation sites... http://forums.digitalpoint.com/showpost.php?p=3357316&postcount=22
I think he's referring to the fact that Wordpress as it started out was a blog system, and even now it's still called a "personal publication platform" on the homepage to emphasis these roots I'd think =) Plus with a default install it's a just a blog and requires knowing what you are doing + your way around the system to get it functioning like an actual content management system without looking like a blog. Your own site is a re-skinned version of wordpress in it's blog form i.e. news posted on specific date, categorized by month archives and comments on said news posts. In this format, it's not a traditional style website I'd say personally - it's a blog. But yeah check out the link to the other forum post, those are some great ideas to work from if you have the time.
Well, I'm thinking of a CMS in the traditional sense like Joomla and Mamba. I'm thinking of creating a new site, but want more of a news site than a blog. Looking for examples so I can decide on whether to use Wordpress on the backend or look for something else.
You could try Website Baker out as it's my personal favourite. But you can view many CMSs at http://www.opensourcecms.com/ which has demos of everything too!
Can you tell me exactly how this differs from any other CMS? Just for a few for instances: Geeklog - Standard install - Stories function nearly exactly the same way. Joomla - Standard install -Add New Content functions nearly exactly the same way. Drupal - Create Content - Story - function nearly exactly the same way. For each of these: news items - time dated. Think about what the CMS stands for. Tell me any other "CONTENT MANAGEMENT" feature that any other CMS has that WP doesn't.
while I don't think that we can argue whether Wordpress is actually a CMS or not (because it is) I do think that there is a traditional difference in how people see the two. A wordpress cms is a blog cms. Something like Joomla has a defined front page with seperate pages/sections. Fundamentally, there is no difference. Functionally, there is no difference. But there is a difference in how they are traditionally used. When you ask most people what Wordpress is, they say it's a Blog software not a CMS. Ask people what Joomla is and they tell you it's a CMS. Technicalities aside, SpringCypress, and there really is a perceived difference and a real difference in use.
Hi all, I think it is easier to discuss differences in CMS product by dividing up the products into three architectural layers: 1) The presentation layer (how the screen is defined) 2) The application layer (the scripts that present data on the screen) 3) The database layer For the presentation layer, it is nice to have flexibility/malleability so that a page can be easily divided up into different sections with different types of data presented in each section. For the application layer, it would be nice to have built-in functions (e.g. blog, comments, categories, user security and access, spam protection etc.) built into the products and maintained and tested as a whole, in order to ensure high performing, reliable, secure, and backward compatible releases. Plug-in capabilities are nice for extending the system, but should not be considered as replacements for a well built core system. The application layer should be extensible so that it can easily take advantage of data being delivered by the application layer. The database layer should be easily modified to include new types of datatypes so that data does not have to stored outside of the database engine. It should be easily accessible (preferably via SQL) by the application layer. I have not had the time to really investigate all of the CMSs, but so far, I am most impressed by ExpressionEngine for its extensibility, built-in core functions, and clear layering of these different architectural layers. However, to get this flexibility, it is necessary to untie the different layers together and tie them via programming code (i.e. CSS, HTML, tags, PHP code). This is more experience than I have or willing to pay for at this time. I have not looked at MovableType, but my guess is, based upon the sites that I have looked at that use it, that it too has a very flexible architectural structure. As for Wordpress, Joomla, and Drupal, they are all trying their best to blend ease of installation and use with architectural flexibility, and I think Wordpress does the best when it comes to ease of use and reliability (because the structure is very closely bound together) while Joomla and Drupal are more at the other end of the spectrum. However, Joomla and Drupal platforms scare me a bit, because the core development has to be very closely monitored and controlled in order to create stable platforms. It doesn't appear to me that this is happening right now. The downside of "opensource". Rich