Overall Satisfaction with Concrete5
We use Concrete5 internally to track and control internal processes. It was very quick to set up and use. We are able to host it on our own Apache server, and setup was similar to other CMS software like Drupal or WordPress--set up database, install code, provision users and permissions. Then we set up some pages for writing out procedures and then we ran it through Concrete5's publish workflow.
- Has a great community
- It's open source
- It's free
- Has an add-on market for features not built in
- Huge time saver
- Add-on market could be bigger
- Documentation can sometimes be lacking
- Positive impact on our workflow at very little cost to us in terms of time
- Negative impact in that it is one more thing to maintain on our server rack.
Concrete5 is much easier to use than Drupal and has more functionality set up out of the box with just enough add-ons to get the job done. I have used both WordPress and Drupal, and this sits between them. Concrete5 is not quite as easy as WordPress but much easier than Drupal and still has the ability to be configured as needed since it is open source.
Do you think Concrete CMS delivers good value for the price?
Yes
Are you happy with Concrete CMS's feature set?
Yes
Did Concrete CMS live up to sales and marketing promises?
Yes
Did implementation of Concrete CMS go as expected?
Yes
Would you buy Concrete CMS again?
Yes
Concrete CMS Feature Ratings
Evaluating Concrete5 and Competitors
Yes - It replaced WordPress; our WordPress install got hacked and our boss asked us to find something else easy to use, and this is what we went with. I know a few other developers that like to use it, so that made the decision easier to justify.
- Product Features
- Product Usability
We like the publishing workflow and ease of editing items on screen, which is something we did not feel we could easily do with products like Drupal.
I would like to have doubled the amount of time we spent evaluating the product and set a specific set of goals for each division to attempt to achieve to see where the exact sticking points would be for the development of add-ons.