CoreMedia is Great for Contributors and for Developers
Overall Satisfaction with CoreMedia
CoreMedia is used across the organization. Governance is done centrally by the Communications Department while content creation is done by 100+ users across all departments. Product implementation is done by software engineers in IT and by web developers in Electronic Communications. CoreMedia is used to deliver our content-driven public website, a peer-reviewed publications site, and a career advising content application.
Pros
- Integrates well with existing infrastructure and software applications. We leveraged ActiveDirectory authentication, a Solr search engine, Java/Spring, Oracle, and other technologies.
- Allows for multiple workflows for content publishing based on user roles. Each of our sites has separate workflows and allow for managed and unmanaged content production.
- Templating system is extremely customizable without being unmanageable. This allows developers to custom tailor content and presentation without worry about performance.
Cons
- Some technical concepts require quite a bit of learning. There is very good training and documentation available, but you will need a strong team of developers to leverage all the features of CoreMedia.
- The overhead of maintaining a 16,000+ page site is minimal now where it was entirely unmanageable previously.
CoreMedia Implementation
- Vendor implemented
- Implemented in-house
Yes - We had two tracks of tasks for the project. One was a set of tasks for developing the design then implementing the software based on those designs. This work was done by a team of in-house developers and a few consultants from CoreMedia.
The other track was a set of tasks for migrating content from our previous system (aka, HTML files). These were content analysis, information architecture, and data entry tasks.
The other track was a set of tasks for migrating content from our previous system (aka, HTML files). These were content analysis, information architecture, and data entry tasks.
Change management was a big part of the implementation and was well-handled
- Content migration took significantly longer than anticipated due to the complexity of analyzing static HTML files. We attempted to hire a 3rd party to automate the migration which turned out to be a waste of time and money. In the end, content experts migrated content manually.
Comments
Please log in to join the conversation