General concepts

Lino community

The natural and legal persons who use the Lino framework and want to collaborate with other members.

Lino consultant

Knows the possibilities and limitations of the Lino framework and gives neutral advice about whether or not to choose Lino as a solution. Helps you with analyzing and formulating your needs and finding the right business partners who will implement a solution.

service provider

A legal or natural person who sells services to a customer.

maintenance

When a support provider helps their customer to keep a given system running.

demo site

A Lino site that contains fictive data used for demonstration or testing purposes.

production site

A Lino site that contains sensitive data owned by its site operator.

Lino server

A virtual or physical computer operated in order to run one or several Lino sites.

A Lino server is installed and maintained by a server operator, either for themselves (self-hosting) or for a server provider who sells this as a service to their customers.

production server

A Lino server used to host one or several production sites.

demo server

A Lino server designed to host one or several of demo sites.

client device

Any device used by an end user to access a Lino site.

This can be a desktop or notebook computer, or a mobile device.

Components

documentation tree

A collection of documentation pages grouped together and published as a book or a website.

Lino core

A source repository containing core functionality used by every Lino application.

Lino Extensions Library

A plugin library with shared plugins that are used by many Lino applications.

plugin

A module or logical part of an application which potentially can be shared among several applications.

plugin library

A collection of plugins grouped into a single source repository and maintained by a given development provider.

front end

A software interface designed to enable user-friendly interaction with a computer

More specifically in Lino, a specialized plugin responsible to render the web interface of a Lino site.

A same database can be exposed on different sites, using the same application code but different front ends.

source repository

A set of source files that is grouped together as a whole and published together with a version control system.

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 .py, .js and .rst.

Some consumable content file formats commonly used in a Lino project are .html and .pdf.

configuration file

A file that contains configuration settings to be read by a program.

end-user documentation

Documentation targeted at end users of a given Lino application. Written in the language requested by the site operator.

technical documentation

Documentation written for developers and motivated site experts. Only in English. Includes tested source code snippets and part of the test suite.

test suite

A set or source code files that don’t add any functionality and is used only for running automated tests.

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 operator to test new features and to reduce stress caused by unexpected results after an upgrade.