Understanding JayDMS

The concept for JayDMS is quite simple, the idea of JSON objects serving as components. The reason for choosing JSON was because of the multi-language support.

JSON (JavaScript Object Notation) is a lightweight data-interchange format. It is easy for humans to read and write. It is easy for machines to parse and generate. It is based on a subset of the JavaScript Programming Language Standard ECMA-262 3rd Edition - December 1999. JSON is a text format that is completely language independent but uses conventions that are familiar to programmers of the C-family of languages, including C, C++, C#, Java, JavaScript, Perl, Python, and many others. These properties make JSON an ideal data-interchange language.

The idea of components is obviously nothing new (https://www.webcomponents.org, https://reactjs.org/, etc). However, when it comes to a CMS and rapid development, this simply isn't mainstream. Themes and plugins dominate the CMS world. The idea of merging the two concepts (CMS & components) is where JayDMS comes into play.

This needed to be something that translated well for developers & UX/UI designers, while bypassing all the development grunt work that goes into setting up a dev environment, and keeping the same concepts general CMS users can recognize.

So what goes into a JayDMS component? Field types, HTML (Twig), CSS (SCSS), and JavaScript. Along with some minor values, these four sets of data allows JayDMS to not only create admin views, but also web pages.

More coming soon...