Articles

The next challenge is File Storage, with all the interesting problems that come with it. With a CMS, the content editor will want to add images, pdfs and all the other media they might need to attach to a page with a click, here's how we do it in the New CMS

Our new CMS is at the point where it is a fully functioning system, but it is simply a system that allows a user to use the it, nothing more. Without the Content Management, it has no purpose. This article will look at how we are adding the Content Management to the system.

When an app falls over, we can usually point at an update in the code that caused it, but what if there was no update? We have a who done it that would have Homes and Watson stumped. Who did it, why and how? Let's have a look.

The new CMS allows connection to the data using a RESTful, JSON:API 1.1 API. This article defines how we created that API and why we made the decisions we made. No ads and we don't want your data, just have a read and hopefully it helps with your own APIs.

We've already looked at the architecture, project management, data and the User Interface in previous articles, but in this article we'll look at the authentication and how we will allow the right access to the right users and processes at the right time.

We have been working on the the New CMS for a few weeks and it's starting to work like a real webapp, but we haven't really decided on a layout and UI. In this article, we'll look at the User Interface and layout.

In the last post we talked about what the project is likely to contain and how we expect the new CMS (Content Management System) to work. In this post we will talk about getting the project off the ground. Let's start with the approach.

We are creating a new Content Management System, but when it's finished we have no idea what to do with it, what are your thoughts? It's no secret we use Drupal for all our CMS needs at the moment, but what might be a secret is the time it takes to setup a Drupal CMS for a new project.