There are a plethora of content management systems (CMS) available in the marketplace.
Wordpress, Drupal, Joomla, DNN, Craft, Ghost, Liferay, Contently, Prismic - all do great for what they are designed to do; store articles, pages, and media presented on a website.
Contently and Prismic are the exceptions to this last point as they are designed to be completed by a website or app separate from the content.
What none of these do well is actual content workflow management. When you think about who designed and wrote these platforms, they are written by developers that wanted to put content up for blogs and websites. They didn't take the time to think about the publishers and writers. As such, they are missing an essential bit of workflow.
CMS 2.0 - The Content Workflow System
In my trials and tribulations or finding a system that works for me, I have written many website technologies that either was written from scratch or forked from their original intent.
I've hacked Ghost CMS, perfected a growth driven WordPress system, built a full journalistic Drupal site and extended another. But they all felt hacked and cobbled together.
After working with Google's Firebase serverless platform, I have tested opportunities that will likely allow for winning.
The content structures are stored in the Firestore database. There is a NoSQL focused collection/document data structure providing for the flexibility desired in the initial start of a new system.
Firebase Cloud Storage
The media and files will be uploaded directly to Firebase Cloud Storage. Now the files can be scaled and distributed based on your data service needs.
Some elements from dynamic URLs creation and storing to responsive image thumbnails all operate from Firebase Functions.
Firebase Dynamic Urls
Love branded URLs? Now you can create a shortened URL that redirects to an article on another site, giving you greater onsite metrics tracking in the Firebase metrics.
What about hosting the site?
Static HTML? Yes, please!
Dynamic blog posts? You can get this here, also!
Don't forget about putting in your forms for newsletter signup or other form-based needs.
What are the drawbacks?
There is a significant paradigm shift for how a CMS is thought about currently in the creation of a CMS 2.0 platform. A CMS is a singular piece of software that manages all aspects of a website and installs as a single package. This system is more of a distributed platform of services. One that is maintained and packaged to work together, but it is targeted to work on the Google Firebase Platform of services.
It is much easier because of the Firebase Platform itself and how it was developed to work. It won't be a simple click install on any host you choose like you can with WordPress however.
Where are we now?
I have started the admin development on Angular 6. I considered Vue and React, but I like the admin systems I've worked on in Angular. The great thing about Vue is I can put in other bits in Vue if there is a need.
I think there may be a substantial likelihood for Vue in the front client host, but this won't need to be the only hosted theme, Angular and React could as easily find their way into the hosted templates.
These are thoughts for the future, however. For now, I have the name of the project, Open Source License to review and organization structuring. Oh, and code to write.
Subscribe to Darren by Design
Get the latest posts delivered right to your inbox