Jolojo is a headless application which doesn't provide its own front end. Traditionally web applications have been built as 'monolith applications', where all of the functionality, including the front end, is bundled up in the same project.
The trouble with a monolithic application is that after years of work it becomes very difficult to make substantial changes. In contrast to that, a headless application provides a simple way to decouple the different parts of an application from each other, which in turn makes the application more flexible, open to experimentation and constant evolution.
Why Go and Vue.js?
Go is used to build the core headless API which drives the entire CMS. The reasons for choosing Go are that it's easy to pick up and learn, it's a strongly typed, compiled language, it's very stable, and it's secure.
The fact that both the Go language and the Vue.js framework are simple means that our code is accessible to anyone who needs to work on it, and means we don't get bogged down in the minutia of the tool, so we and you can focus on making better applications for everyone.
Jolojo presents all back end data via a series of APIs to front end code.
This is the perfect scenario for developers who are looking for a back-end CMS system from which they can either adapt / add to an existing front end (the 'out-of-the-box' front end code that runs the core CMS system is written in Vue.js) or write their own in their preferred language.
As Jolojo is fully headless the opportunities for connecting bespoke front-end systems to the Jolojo back end data is almost limitless.
You are only limited by your imagination (lucky you!) We however are running to a publishing deadline, so here is what we have though of:
Whatever you want to do, we would love to hear from you.
Go on. Make a splash with your next project!
With Go and Node used for the back end and an extensive set of APIs already built, Joljo could help kick-start your project by offering a ton of well written, well thought out functionality.
Administration of most of the back end functionality is already handled by the front end code, so this will be super easy for you to pick-up and modify to your requirements.
SQLite is used as the DB engine, this is easy to deploy, has a good OS licence and has multiple advantages for the developer (such as the ability to query JSON within a table).
All front end data is well presented via APIs, so your functionality can be branched from the core code and presented it its own API inherently stabilising deployment and isolating change.
As with the examples above, this is just the tip of the iceberg!