The structure of the Qoob

For better understanding we divided the Qoob into 3 parts

Libraries

Qoob Core

Driver

Qoob core

The main goal of the Qoob core is to be universal. So you can integrate it with any existing project. All what you need is to write a simple driver. The Core uses Backbone framework and works only on the client side. The Qoob core is simple and easy extendable.

Driver

The driver consists of 2 parts. Backend and Frontend.

Frontend part of the driver

Frontend should be written in JavaScript and implement next methods

savePageData(pageId, data, cb);
loadPageData(pageId, cb);
loadQoobTemplates(cb);
loadQoobData(cb);
getIframePageUrl(pageId);
exit(pageId);

Backend part of the driver

Backend can be written in any languages for any CMS. You can do without backend if you don’t need to save pages or you save them in a database like firebase.

Libraries

The Qoob core can use many libraries at once. Each library is a pack of blocks. The Qoob core is written in a way that the page speed does not depend on the number of libraries. Moreover, the library can work from any online resources. It means you can use one library for all your projects without copying it to each project.

Blocks in libraries

The library consists of blocks. Any block can be a visual block or a pack of images or video. Once a block is written it can be used in any project with Qoob no matter what driver is used.