Allow publishing the documentation to a website, see also #43

Defines a physical object model with a certain purpose that embeds a certain hardware in order to provide functionalities.

• name
• handle
• model-id
• part-numbers
• hardware-type

See also edgehog-device-manager/edgehog-astarte-interfaces#17

It should be possible to find devices using following keys:

• device id
• location (formatted_address, country, locality, postal_code, street_address, gps_area?)
• appliance part number
• appliance handle
• appliance name
• hardware type part number
• hardware handle
• hardware name

Device page should display a tab with information about local storage status (e.g. avail / used disk space) for each disk.

It is the type of connected device hardware, it has a CPU with a certain architecture where the device manager agent runs.

From a practical point of view, the hardware type defines a set of capabilities (e.g. MCU system, ARM CPU system, x86 CPU system, etc...)

• name
• handle
• (manufacturer) part-numbers

In order to make Edgehog ready for prodution, we should define the Auth strategy.
Defining a JWT special claim for global admin access, such as "*" would be a good first start, while defining a comprensive solution.

Display information about the Edgehog agent running on the device, such as the version.

See also edgehog-device-manager/edgehog-astarte-interfaces#26

An API for fetching data about all disks connected to the device should be implemented.

Device should be associated to the correct Appliance Model using io.edgehog.devicemanager.ApplianceInfo interface.

Following scenarios should be also supported:

• Device Appliance Model is changed to a different one after a part number change (when using a valid part number)
• Device Appliance Model is unset after a part number unset
• Device Appliance Model is unset after an invalid part number is set

It should be possible to upload one or more (optional) images for a given appliance model.
This image should be displayed when opening the Appliance Model page and the Device page, furthermore it should be possible to fetch this image using an easy-to-use API (that can be used from 3rd party frontends).

It should be evaluated if it might make sense to provide support to different sizes or image purposes (e.g. icon / small appliance photo / full size appliance photo).

Allow multiple languages for the description of each Appliance Model, with the ability of setting a description as the default one

Device Page should display battery and power supply status.

An API for fetching data about all batteries connected to the device should be implemented.

Edgehog should work also when some interfaces (or most of them) are not implemented on the device side.
The frontend should show less tabs in that case.

An additional tab for displaying information that can be fetched using OS Bundle API should be added.

Add documentation scaffolding to the main repo.

An interface for publishing storage status should be defined.

Following data should be sent to the cloud:

• available space
• totale space

It should be parametrized using storage label.

Display information that devices send using io.edgehog.devicemanager.CellularConnectionProperties and io.edgehog.devicemanager.CellularConnectionStatus interfaces.
See also edgehog-device-manager/edgehog-astarte-interfaces#17

Add a documentation page for Device, Appliance and Hardware Type concepts.

It should be possible to input a description text for each appliance, that is displayed on the Appliance Model page, on the Device page, and that can be fetched using an easy-to-use API.
It should be possible to input different descriptions for different locales, and to default to english one when the translation is missing.

Add a button that makes the onboard indicator led blink. The button should be hidden or not visible when the led interface is not available.
The purpose of this feature is to allow finding/identify a specific board among a number of boards using a visual feedback, and to perform a quick connectivity test.

It required to add all functions and configuration options in order to handle user uploads and downloads, that will be used when dealing with assets such as Appliance Model image.
It required to enable support for an external storage bucket.