Intro
The purpose for Qore is to set a solid base for future ERP/CRM systems. New projects can use this application as a foundation including authentication, tables, resources and more.
Terms
-
This application is called
Skeleton
.Skeleton
is a simple Laravel installation with a few resources, routes, fields and more built in. It can be cloned for future projects, and tuned to the customers' wishes. -
Skeleton
includesSystem/Qore
in the back-end.System/Qore
consists of the foundation for resources, fields and more. See it asLaravel/Framework
for new Laravel projects.
List of definitions
Term | Description | Is part of | Examples |
---|---|---|---|
Component | A component is a main part of the Qore and will be present in every project. Components define the foundation for subsystems. | System\Qore | Authentication, Roles and Permissions, Tables |
Module | A module is not a main part of the Qore and will typically use components. Modules can be build as a loose subsystem that can be active/inactive. | t.b.d. | Invoicing, Tasks, Timeregistration |
Plugin | Plugins are comparable to modules. Plugins are typically smaller in scope, and usually communicate with external API's. Plugins are usually built as an extension on a module. | t.b.d. | Postcode field, KvK field, VAT checker |
Mod (modification) | Mods are pieces of code that will either extend, edit or replace parts of Components, Modules or Plugins. Typically mods are necessary for business specific (logic) related wishes. | Skeleton | Layout changes, fully customised pages, VAT rate calculations |