Why use Glide, versus Open Source and ‘free’?
Being a professional content creator brings many challenges, and among the many critical decisions you as a publisher will make is choosing the right Content Management System for your needs.
CMS can bring with them a vast array of side-effects and complexities, which can mask the important question: which CMS will do the most for you, with the most positive impact on your goal of getting your content out to the world and making your website work better? Your expertise is publishing and content, so that’s what you should be free to focus on.
When considering your options, do you opt for one you can setup quickly online, but is not geared for what you need – and work around its shortcomings from then on? Or instead opt to go more hands-on with a blank sheet system which has infinite potential for adaptability, and immerse yourself in engineering and try to mould it to fit?
We’ve been there. We’ve seen editorial and content teams mired in their daily lives by the need to become CMS workaround experts first, and content people second. We’ve lived the frustration of being dragged further from making great and engaging media, to instead having to become specialists in tricking a system to fix a problem. All while deadlines loomed. We dreamed of a CMS which knew what publishers need, and just did it.
That’s why we created Glide - built upon vast experience in publishing, in editorial, in production, and a wealth of experience tailoring and integrating systems to give editors and creators what they need.
We’ve built a Content Management System that removes problems and gives you back time to create. A CMS that has all the tools modern publishing demands, ready to go, geared towards content makers, from a company that is rooted in publishing and focused on making it easier.
Free: break-to-fit, or death by customisation?
There are some fantastic free and Open Source CMS tools out there. WordPress democratised content as never before and gave millions a fast-track to the web when it arrived in 2003. More than any other software, WordPress handed the average person the tools to talk and create at their own pace, in blogs and simple sites where their voice was theirs own. It was inevitable big publishers would come calling and try to make it fit their needs.
We used it, and loved it, and saw how it helped move the world on from the pain of millennium-era web publishing. But as Web 1.0 and 2.0 became distant memories, like most we wrangled with issues caused by the staggering array of plug-ins created to try and fit the whole web into a single platform. A task so unsolvable there are now more than 54,000, all needing developer expertise, support, integration, patches, security updates, and the hope they don’t break one another. We knew the WordPress fear: “We finally got it to work, now don’t touch a thing…”. And that is not what modern publishing needs.
WordPress is still the choice which can arguably enter you into the fray of publishing the quickest. But it has become arguably the most complex to get right, and the most studied for vulnerabilities by those looking for gaps. It’s understandable that as a result the largest ‘free’ offering can have the most impact on your outcomes and resources.
Drupal’s Open Source platform is another free and well-known option. Where WordPress offered an easy front-door to the web with themes and easy start-up for individuals, Drupal and its enthusiastic community have extended its base in every direction with numerous extensions and major updates every few years - to update the toolset which your developers can use to build your custom solution.
But are you a publishing company, or a CMS company? Your developers are experts at making your business work better, at making your site’s front-end sing, and at making the cool stuff that changes the world of your users. Now you are asking them to become experts in building a CMS which solves the problems of publishers too.
Like WordPress, it’s no wonder so many Drupal Open Source users need outside support, or found themselves so far down a path of customisation that the system became the problem, not the solution.
The Glide goal: publishing success
This is why we do what we do. Glide CMS is a Content Management System by content people, for content people, built by engineers who have spent their careers working with publishers and solving their problems.
The Glide web CMS family has its focus on content creation and publishing rather than extending the base platform is every possible direction.
This ethos and focus is driven by decades of best-in-class publishing experience across newspapers, magazines and numerous digital properties, with a firm understanding that digital transformation for content creators is an ongoing, iterative process and not a one off event.
The Glide goal is giving creators a CMS that does the most for them out of the box and uses the least of their precious time. Launch quickly, with workflows and interfaces created specifically for newsrooms and creators, and engineered with publishing business objectives in mind by making websites work better, reaching more people, making more revenue, and costing less overall.
Glide is a CMS for creators and publishers, because it was created especially for you.