The Lino framework is defined by a set of source repositories : the Lino core, the extensions library, a series of Lino applications maintained by the core team, a series of front ends, the technical docs and this community guide.
- Client device
This can be a desktop or notebook computer, or a mobile device.
- Lino core
- Extensions library
A module or logical part of an application which potentially can be shared among several applications.
- Plugin library
- Front end
A plugin which defines the web interface for an application.
A same database can be exposed on different sites, using the same application but different front ends.
- Source repository
A set of source files that implements a given set of functions.
For example we have different repositories for the Lino Core, the Lino Extensions Library the Lino Book* and the Community Guide.
- Source code
Content to be edited by a developer and to be built (compiled) into an executable program file or consumable content (e.g. text, image, sound or video).
- Source file
A file which contains source code.
Some source file formats commonly used for building executable program code are
Some consumable content file formats commonly used in a Lino project are
- Configuration file
A file that contains configuration settings to be read by a program.
- Database application
A computer program used by humans for entering and retrieving information from a database.
- Customized database application
A suite of software tools used by developers who write and maintain applications for their employer or their customers.
- End-user documentation
- Technical documentation
- Test suite
- Automated tests
A part of the development process which verifies that a change in the software doesn’t break any existing functionality.
- Preview site
A copy of the production site as it would look when using some newer version of the software.
It is made available to end users so they can preview and test their coming version before a site upgrade.
The primary goal of a preview site is to help the site owner to test new features and to reduce stress caused by unexpected results after an upgrade.