Since the birth of content management system (CMS) technology, well over 20 years ago, platforms have been leveraging “obvious backends" like SQL databases as a store for the content. Not because it’s the best or right store for the job, but because SQL databases are a commonly available, simple to use technology that (kinda) gets the job done. By the early 2000s, it was clear with many implementations that directly leveraged SQL and similar database stores do not provide the full range of features like versioning that a CMS requires. They can’t. They were not built to do it. The Java Content Repository (JCR) and other similar technologies entered the scene. The implementations of these technologies sit on top of the same old database stores and add a layer of capability to fill the gaps. This is good but not good enough. Ultimately, the fact that they sit on top of a database comes back to haunt them.
In Part 1, we looked at what kind versioning model is needed to support modern digital experiences. Today, we focus on another critical capability that is missing in traditional CMS solutions: a distributed repository. More specifically, distributed versioning and workflow.
Traditional CMS platforms like Drupal, WordPress, Adobe Experience Manager, Sitecore, and most others either have severely limited versioning or provide basic versioning capabilities that track single object graphs or maintain clunky data structures to track relationships.
Figure 1: Single file versioning model. Each object has its own version tree. How and whether relationships are tracked between objects differ from one system to the next.
In 2017, my blog has been powered by Hexo.js. However, I am looking for a replacement since Hexo.JS is lacking crucial features.
TLDR : HexoJS is too limited, I want online post edition!
Highlighting search terms in search results is a common requirement for many websites. Crafter CMS builds on top of Apache Solr and makes implementing rich search and other query-driven experiences super simple.
Step 0: Prerequisites
If you haven’t gotten Crafter CMS set up and built your first site you can follow this tutorial to get started: Working with Your First Crafter CMS Web site.
Imagine a very simple blog. Blog posts are just a title and a paragraph or three. In that case, having a CMS where you enter the title and those paragraphs and hit publish is perfect. Perhaps some metadata like the date and author come along for the ride. I’m gonna stick my neck out here and say that title-and-content fields only is a CMS anti-pattern. It’s powerful in its flexibility but causes long-term pain in lack of control through abstraction.…
How Different CMS’s Handle Content Blocks is a post from CSS-Tricks
Joomla follows WordPress as the second most popular and most used CMS worldwide. The team of professional supplier RSJoomla! has something to give away to three lucky readers of our beloved Noupe magazine. Joomla is […]
Have you ever seen the movie Office Space where the fax machine doesn’t work? Every day, the office workers struggle to use it, especially one certain employee, until he decides that enough is enough and ultimately kills it (with the help of his equally frustrated colleagues).
I think we can all relate to wanting to drop-kick outdated technology.
Most CMS platforms do a decent job of simplifying content and digital experience creation and editing for non-technical content managers. The challenges really start once you need to innovate and development is required. Traditionally CMS platforms have been pretty bad for developers. They require a lot of CMS specific knowledge and don’t integrate with developer tools and process.Here are 7 things that developers really want with a CMS:
Let me work locally with my own tools like my IDE and my source code management.
Let me leverage my existing skills. I want a low learning curve. Don’t make me learn a new, niche framework.
Let me work in teams on multiple projects at the same time without interfering.
Let me maintain a real development process.
Make the integration with the CMS seamless.
Don’t make me do builds.
Don’t make me do heavy deployments.
In this installment of the Work Your Way Series, we’re going to tackle item #1: Let me work locally with my own tools like my IDE and my source code management. Let’s start with some background: Crafter CMS uses Git as its primary content store. That’s the foundation of the solution for developer desire #1. A developer can mount a local clone of a Crafter CMS project directly with their IntelliJ, Netbeans, Eclipse or other IDE. That means they can use their preferred development tools to edit and debug code and templates. And as they work, all of the changes they make are tracked by the Crafter CMS via its native Git support. Sounds awesome right? Let’s learn how to get set up.
In a previous article (Querying Content in Crafter CMS), we talked about how you can query content in Crafter using content and search services. Under the hood, Crafter CMS saves all of the content you create through the authoring interface (Crafter Studio) as XML. This XML is published from Crafter Studio to dynamic delivery engines (Crafter Engine) and is available through the content services and is also indexed in Solr and thus available through Crafter’s search services. There are times in the rendering engine (Crafter Engine) when you may want to get access to values in the XML directly and work with the content as an XML Document Object Model (DOM) API.
In the example below, I will show you how you can:
The Move From Static to Dynamic
We saw the emergence of dynamic when the constraints of static failed to meet the new demands of the web. They were hard to update and did not allow for dynamic navigation and user interactivity. In order to maintain timely and relevant websites, companies started to store their content in databases and dynamically deliver it to their site visitors. This spurred the growth of content management systems (CMS), which allowed for the managing of content and files that could be dynamically displayed on different pages and areas of a website. A CMS meant that a content editor could update the content of a page or site and their changes would be reflected instantly, without having to use FTP or know HTML. These dynamic publishing platforms unleashed the tidal wave of online publishing that has changed our world and how we consume information.