Modules

A module is a set of features or services that can be added, cooperate, the whole being used by the main application. Modules can be public and reusable by a number of applications, or be private and specific to a particular application. In that case, a module is not necessarily a way to reuse code, but rather a mean to manage complexity by dividing it to smaller problems.

Conventionally, modules can be added in two places: vendor/ and module/. Modules in vendor are kind of reusable libraries, typically provided by third parts, while modules in module/ belong to your application.

Flow-er comes with several vendor modules :

• flCore: The core Flow-er reusable services,
• flBo: A powerfull back-office and user interface that can be the foundation for building a CRM for example,
• flDoc: Everything needed to publish documentation for your application,
• flDocument: An engine for a simple document management system,
• flHub: An API orchestrator for providing graphically supervised automations,
• flMdb: An extension of Flow-ER UI using the Material Design for Bootstrap ™ style sheet,
• flMy: A set of services to help implementing a public app,
• flPub: Public and protected web form to be hosted in a website or accessible by a personalized link inside a mail,
• flStudio: a no-code app to adapt flow-er's configuration and settings to each client context,
• flTranslation: for worldwide applications,
• flUser: for managing user enrollment.

Except the vendor modules listed above, modules added to flow-er are gitignored, letting you manage the versioning in a per module basis.