Your organisation is unique, and as such, has a unique set of content management system (CMS) requirements. There is also no single 'perfect for everyone' content management system. Each product has its own set of strengths and weaknesses, and distinctive design principles. Unfortunately, the selection process followed by many organisations doesn't recognise this, leading to the purchase of a CMS which does not match business needs. Selecting a CMS does not have to be a lottery. By following a requirements-focused methodology, instead of a features-driven approach, the right CMS can be identified, and the business risks minimised.
A triple-barreled question facing many enterprises today is whether to use an application-building tool or 'framework' to build a content management system (CMS); to buy one of the many out-of-the-box finished products in use by major Web sites; or to simply rent a CMS from an application service provider (ASP) and avoid the headache of running an application server in the enterprise's data center.
As your sites become more critical and complex, you need tools to automate management--and you need them now. Enter the new generation of Web site content-management products--a seasoned batch of tools and systems ready to help you meet the challenges of the brave new Web world. There's a wide range of products out there, and while they overlap somewhat in functionality, the phrase Web site content management means different things to different people. For some, content management is really asset management--that is, a system to keep track of media assets, such as graphic elements, text and video. More commonly, however, Web site content management refers to a set of integrated tools that helps manage some portion of the whole range of site development and deployment tasks. Although no single product can do everything, many offer deployment/publishing, versioning and rollback, site design and page authoring tools, link checking, access control, change routing and notification, and site-visualization tools among their features.
The CMS market really took wing with the liftoff of the LAMP stack and the growth of a supportive development community. Suddenly it seemed everyone was producing LAMP-based CMSes under Open Source licenses.
As ridiculous as that may sound many are getting away with doing it. There are many comparisons of open source CMS software that are popping up that are total garbage. The reviewers are comparing CMS systems that are in 5 to 8 different categories and have 4 different sets of requirements. No wonder they are confused and can't make a choice.
Open source content management systems can make creating and managing your website a lot easier - and there's no licensing fee involved. But which should you use? We look carefully at Joomla, Drupal, and Plone to compare their strengths and weaknesses.
Open source content management systems (CMS) are particularly attractive to the nonprofit community because of their cost-efficiency, but what do these systems actually do? And what are the differences between the most common CMSs? We’ll compare Joomla, Drupal, and Plone for typical nonprofit needs.
In this report, we take a look at four different open source Content Management Systems—WordPress, Joomla, Drupal and Plone—and rate them on a variety of criteria, including system flexibility, features, ease of use and the availability of support. We chose these systems because they’re the most popular four in the nonprofit sector today, according to our analysis (see Appendix C for more details on our market analysis). We also dig a little deeper into what open source is all about, and how a CMS can help streamline processes. We even take a look at some vendor-provided systems, along with a few other open source ones, in case you don’t find what you’re looking for among the four original choices.
YSlow assigns letter grades (A thru F) for a page in each of 13 categories of best-practice. I decided to run YSlow against the home pages of 35 well-known web content management and/or enterprise content management vendors, then calculate a Grade Point Average. The scores are posted below.
Once you've built the business case for purchasing a CMS, this guide can serve as a 'field guide' for the evaluation, implementation and deployment process. It begins by analyzing the anatomy of a CMS project, going through the decide and buy, implement and integrate, manage and maintain and upgrade and enhance phases. As part of the first phase, this guide provides a very useful sample of a Request for Proposal (RFP) to help you evaluate content management vendors. The guide also underlines the importance of viewing content management as a process, not a product, and suggests working with a content management vendor who will become a core part of your Web site management team.
It is quite possible, in fact could be preferable, to manage content and distributed authorship without the use of a content management system (CMS). Regardless, it’s very important to have a process in place before you choose a CMS.
In SharePoint, we are likely to think of developers as people who work to customise SharePoint, but there are a lot of developers out there who are simply end users of SharePoint. How do they like the system?
Microsoft markets SharePoint as an omnibus information-management platform, but like all software, it has meaningful strengths and weaknesses. People frequently label SharePoint a collaboration product, when in fact, it excels at some types of collaboration but virtually ignores other. SharePoint is useful for some Web Content Management scenarios, but poor at (many) others.
Most organizations don’t need content management software. Unless you have a very busy website with lots and lots of content being published, the return on investment is not there. The majority of those who do require such software need a very simple, streamlined solution.
The mission of this site is to help web site developers who are considering or using Drupal. Drupal is a very powerful content management system using php and mysql. There are hundreds of modules and themes available, but instructions for most of these are sparse. My goal is to help you with Drupal, its modules, and its themes.
After a week of fighting with it I have come to the conclusion that Drupal access control modules are all inadequate and are based on some weak database design. Taxonomy access and node access are flawed from the start. This type of access control where the assets are assigning their own internal security is not scalable and suffers from very high database overhead.
In this article we will explore various ways of adding downloads to your web site to provide free content, or to deliver paid content to users. We will also discuss the automatic conversion of pages to PDF files, which your users can download to read or print.
Some writers truly hate Adobe Acrobat and any tool that can do the job better is worth a shot, particularly if it’s open source and easily navigated. Flossmanuals.net introduces FLOSS which does a lot of the single desktop Acrobat Pro’s job - collaboratively and open source.
We reviewed and compared the seven tools most frequently used to create a blog. Which are easiest to get up and running, or to tailor to match your site? Which has the best comment moderation features? Reporting functionality? We'll give you all the details and recommend a tool for you.
Git, though remarkably handy and powerful, is also remarkably hard to use sometimes. Though you can learn the basics easily enough, it can be really tough to dig yourself out of certain corners if you don’t understand what’s going on under the covers. This page provides links to documents, how-tos, cheat sheets, tips, and tricks related to learning and using git.
When companies decide whether or not to adopt a CMS or continue using a HAT, there are many factors to consider. Perlin outlines elements of both CMSs and HATs that could help you determine which is best for your organization.
With FrameMaker 9 comes a new way to work with files on a CMS (Content Management Server) that supports HTTP/WebDAV protocol. WebDAV is a kind of extension over HTTP which allows user to write files on Web along with usual viewing. Multiple users can collaboratively edit and manage files hosted on the Web server. Since many of today’s CMS servers provide users with a WebDAV route to access and edit files, FrameMaker 9 can automate the collaborative tasks by providing direct ways to view and make changes to files on CMS systems.
There's recently been a lot of discussion and considerable interest in content management systems. Buyers are starting to ask for these solutions from vendors with greater regularity and the buyers are clearly better informed than in the past. Still the issue that comes up again and again is, how do you know which content management system (CMS) is right for you?