Blog

Single Page Application (SPA) Development with Nuxt.js: A Quick Review

Single Page Applications (SPAs) have proven to be game-changers in the domain of frontend web development. Ever since the advent of SPAs, the web ecosystem has experienced a significant positive drift in terms of speed, performance, code quality, rel

Crafter: A Headless CMS for SPAs

Single-page applications (SPAs) have been quietly taking center stage in the world of web development for some time. While the average user might not be aware, many of the most commonly used popular websites and social media platforms are SPAs. The l

UI Development with Flutter: First Impressions

Organizations across every industry are laying plans to provide a mobile app to access their services. And with nearly 90% of mobile internet time spent in apps, it’s not hard to see why.  While the web dev world has spent its time solving probl

REST APIs vs GraphQL: Both Have Their Strengths for a Headless CMS

While the advantages and disadvantages of both REST APIs and GraphQL have been hotly debated in recent years, the reality is that both approaches have their uses. The standardization that GraphQL provides also brings limitations that only REST APIs c

In-Context Preview for Gatsby with CrafterCMS

GatsbyJS is a ReactJS and GraphQL based Static Site Generator that is great for developers and Ops but what about the content creators? Content Creators what in-context features like preview, point-n-click editing and drag-n-drop. CrafterCMS and Gatsby provide the solution.  

Is GraphQL the Next API Standard for CMS?

GraphQL has enjoyed tremendous growth in popularity, becoming a de'jour standard in the development community with bindings for well over 15 languages and pluggability with many backends. While GraphQL was never designed to be an API standard for CMS platforms, it may be one of the best things to happen for APIs for content management. Is GraphQL the Next API Standard for CMS?

Introducing CrafterCMS 3.1

CrafterCMS 3.1 Community Edition just released and we couldn't be more excited! In this blog we look a few on the major capabiltiies, features and updates introduced by CrafterCMS 3.1.

5 Areas of Focus for CrafterCMS in 2019

It’s almost 2019 and we couldn’t be more excited with what’s in store for CrafterCMS in the coming months. What’s on the roadmap? Here is a quick summary of five main areas of focus that we know will help Crafter to remain the best CMS platform for innovative organizations.

CMS for SPAs Tutorial: Using React and Node JS with CrafterCMS 3.x

The most traditional, full-featured CMS platforms are not designed to handle headless content and most headless CMS platforms aren’t full-featured and have only basic authoring support. CrafterCMS is both full-featured and fully supports headless CMS capabilities. That’s pretty unique. In this tutorial, you will learn how to create a content-rich, ReactJS-based Single Page Application (SPA) with in-context editing and other full-featured authoring capabilities.

Headless CMS: Enable In-Context Preview and Editing in an External Application

Do you have an existing application that has content in it that you want to manage but you don’t want to completely rebuild in a CMS? This use case is more common than you can imagine. Developers start building an application only much later to find it would benefit from CMS authoring capabilities like in-context editing and preview. What’s the solution? Rebuild the application? No. CrafterCMS is a headless CMS that’s front-end agnostic. It can plug into any application. Let’s look at a very simple example. Just recently I posted a blog that used Node JS an external application that called CrafterCMS headless CMS capabilities for content via APIs.

CMS for SPAs (2 of 4): Save the Content Authors

In Part 1 of the series CMS for SPAs: Are Single Page Applications and Headless CMS a Slam Dunk?  we looked at the trend toward Single Page Applications (SPA) and Headless Content Management Systems (CMS) in general. SPA applications are becoming the de facto way to build web-based applications and sites. Headless CMS is a decoupled, API-first approach to content management that aligns neatly with SPA architecture. Further, the decoupled nature of the architecture makes content more reusable (multi-channel) and completely divorces development from the CMS allowing for greater freedom and agility for developers. While these can be seen as major wins, several developer and DevOps issues remain while others have been created. Further, most of the headless CMS solutions available today set content authors back nearly 20 years in terms of content editing and workflow tooling and practices. In this installment, we’ll focus on the various ways content authors have been impacted by headless CMS and how CrafterCMS addresses these issues to provide authors with true headless CMS support for SPA applications.

Introducing CrafterCMS Javascript SDK

In this blog, we will focus on the language-specific bindings for Javascript, the CrafterCMS Javascript SDK. These bindings can be used in any client side (e.g. a browser-based application) or server-side (e.g. Node.js) applications.