test edits

.gitignore

@@ -2,6 +2,10 @@
 .project
 .vagrant/
 
+meta.json
+landr-dist
+*.traineddata
+
 /config
 /docker-compose.yml
 /package-lock.json

README.md

@@ -11,13 +11,13 @@
 - **Powerful API & SDK**: Extend openBalena to fit your needs
 - **Built-in VPN**: Access your devices regardless of their network environment
 
-## Field-ready fleet management
+## Motivation
 
 openbalena’s backend services, composed of battle-tested components that we’ve run in production on [balenaCloud][balena-cloud-website] for years, can store device information securely and reliably, allow remote management via a built-in VPN service, and efficiently distribute container images to your devices.
 
 To learn more about openbalena, visit [balena.io/open][open-balena-website].
 
-## Getting Started
+## Setup and Configuration
 
 Our [Getting Started guide][getting-started] is the most direct path to getting
 an openBalena installation up and running and successfully deploying your

docs/01-introduction.md

@@ -0,0 +1,14 @@
+# Introduction
+
+To understand how openbalena works, let's start with learning about balenaOS.
+
+## What is balenaOS?
+balenaOS has been designed to include the minimal set of required components to reliably support operation of the Docker engine in embedded scenarios. It uses the Yocto framework as a foundation, systemd as the init system.
+
+The networking stack consists of Network Manager, DNSmasq and Modem Manager. We have found these components to be a robust stack for dealing with the diversity of hardware and unpredictability of configuration of networks in which a device may be booted.
+
+In addition, we include Avahi, OpenSSH, and OpenVPN, which add support for mDNS, SSH, and VPN connections respectively.
+
+This foundation is uniquely suited to running arbitrary containers on a wide range of embedded devices which balenaOS supports. Balena has also made available a wide selection of base images for containers which are optimised for the same scenario and allow developers to create applications based on the Debian, Alpine, or Fedora distributions. That is not to say, of course, that any other container base image may not be used, but that the images by balena have been verified to work well with balenaOS, implementing patterns which are particularly suitable for embedded devices, like balenaOS itself.
+
+![balenaOS components](/docs/assets/balenaOS-components.png)