实例探究 > Elastic’s Move to Contentstack from WordPress Speeds up Development Process by over 500%

Elastic’s Move to Contentstack from WordPress Speeds up Development Process by over 500%

公司规模
200-1,000
地区
  • America
国家
  • United States
产品
  • Contentstack
  • Built.io Flow
  • WordPress
技术栈
  • Headless CMS
  • Integration Platform
实施规模
  • Enterprise-wide Deployment
影响指标
  • Cost Savings
  • Customer Satisfaction
  • Productivity Improvements
技术
  • 平台即服务 (PaaS) - 连接平台
  • 平台即服务 (PaaS) - 数据管理平台
适用行业
  • Software
适用功能
  • 商业运营
  • 销售与市场营销
服务
  • 软件设计与工程服务
  • 系统集成
关于客户
Elastic provides real-time insights and makes data usable for developers and enterprises. They power the world’s leading mobile, social, consumer, and business applications. Elastic was in the midst of merging its .com and .org domains when its new webmaster turned to the pioneering headless CMS Contentstack. Today, Elastic’s 100+ content managers can focus all their attention on developing great content. The company operates in the computer software industry and has a size of 201-500 employees.
挑战
As soon as Sylvie Shimizu started her new role as Webmaster at Elastic, she knew the content management system needed an overhaul. The existing process with WordPress was clumsy, slow and had a tendency to crash. There was no functional staging area and the production site ran on a completely different system, so once edits were complete, all the steps had to be repeated on the production server. Because Elastic had two domains, that meant Shimizu had to effectively perform each step four times every time she needed to publish content. With just three months to merge the .com and .org sites, Shimizu was already under a tight deadline. With any system other than Contentstack, this process would have easily taken six to nine months to complete. Additionally, the company was looking to move away from using the web production agency that had been responsible for its themes and updates in the past. The agency was slow to make necessary changes and their developers weren’t experienced enough to make the process run smoothly. Elastic had to wait anywhere from a few days to several weeks for changes, and were often told the features and integrations they wanted were impossible, which Shimizu knew wasn’t true. She had experience using a variety of different content management systems over the years and had discovered Contentstack previously. She knew it could scale with the company’s needs, that its implementation would be lightning fast, and that it was intuitive enough for content managers to jump in without any training sessions.
解决方案
Elastic was up and running in Contentstack within three months. WordPress and other CMS solutions require hours to get new users up and running, but with Contentstack, little training is required. Members of the team are able to easily navigate the platform, thanks to the intuitive and visual interface. Shimizu hired Contentstack’s services to manage the migration from WordPress. Integrating with Built.io Flow’s integration platform, Elastic successfully automated the creation and deployment of its documentation guide, which allowed Elastic to push documentation content to production, staging, and development as needed. Contentstack helped Elastic achieve three goals: 1. Swapped out an inefficient staging process for a simple, one-step system that’s completely integrated and ready at a moment’s notice. New pages now take minutes or hours, not weeks or months. 2. Removed dependency on third-party template developers. The Elastic team can now keep development moving and create new pages by relying entirely on its existing staff. 3. Created greater flexibility, while at the same time making it easier to add, alter and remove content. Contentstack’s interface provides the flexibility needed and is so easy that new users can instantly use it with little training.
运营影响
  • Now that Elastic is using Contentstack, onboarding time is essentially zero. New content managers can jump right in without a lengthy training process, so Elastic no longer needs to pay an expensive agency to handle the development side.
  • The publishing bottleneck has disappeared, too, since Elastic no longer has to go through an agency to make changes. In their old system, creating a new page could easily take three weeks; now it takes a third of that time, which has allowed Elastic to complete three major redesigns in the last year and a half.
  • Elastic has more than doubled the page views at a fraction of the cost and can now dream up and implement big web projects without limitations.
数量效益
  • Development costs reduced to 1/5th compared to WordPress.
  • Development process sped up by 500%.
  • Onboarding and training time reduced to 0 hours.
  • Monthly server costs reduced from $7,000 to $890.
  • Developer costs reduced from $125 per hour to $28 per hour.

Case Study missing?

Start adding your own!

Register with your work email and create a new case study profile for your business.

Add New Record

相关案例.

联系我们

欢迎与我们交流!
* Required
* Required
* Required
* Invalid email address
提交此表单,即表示您同意 IoT ONE 可以与您联系并分享洞察和营销信息。
不,谢谢,我不想收到来自 IoT ONE 的任何营销电子邮件。
提交

感谢您的信息!
我们会很快与你取得联系。