doc: Create applications section

Ruth Fuchss · carlescufi · commit 2d8bf6b2f071 · 2019-02-14T18:15:09.000+01:00
Split up the samples into samples and applications and add documentation
to distinguish between the two.

Signed-off-by: Ruth Fuchss &lt;ruth.fuchss@nordicsemi.no&gt;
diff --git a/applications/asset_tracker/README.rst b/applications/asset_tracker/README.rst
@@ -3,17 +3,17 @@
 nRF9160: Asset Tracker
 ######################
 
-The Asset Tracker sample demonstrates how to use the :ref:`lib_nrf_cloud` to connect an nRF9160 DK to the `nRF Cloud`_ via LTE and transmit GPS and sensor data.
+The Asset Tracker demonstrates how to use the :ref:`lib_nrf_cloud` to connect an nRF9160 DK to the `nRF Cloud`_ via LTE and transmit GPS and sensor data.
 
 
 Overview
 ********
 
-The sample sends GPS position, temperature, and accelerometer data that is collected by an nRF9160 DK to Nordic Semiconductor's cloud solution, `nRF Cloud`_, where the data is visualized.
+The application sends GPS position, temperature, and accelerometer data that is collected by an nRF9160 DK to Nordic Semiconductor's cloud solution, `nRF Cloud`_, where the data is visualized.
 The accelerometer data is used to infer the device's physical orientation, which is sent as the nRF Cloud sensor data type "FLIP".
 Temperature data is sent as the nRF Cloud sensor type "TEMP".
 
-By default, the sample uses simulated sensor and GPS data, but it can be configured with Kconfig options to use real sensors to collect data.
+By default, the application uses simulated sensor and GPS data, but it can be configured with Kconfig options to use real sensors to collect data.
 The LTE link control driver is used to establish the LTE link automatically.
 When the device is connected to the nRF Cloud, you can use the LTE Link Monitor to send AT commands and receive the response.
 
@@ -27,7 +27,7 @@ Requirements
 
 * :ref:`secure_boot` must be programmed on the board.
 
-  The sample is configured to compile and run as a non-secure application on nRF91's Cortex-M33.
+  The applications is configured to compile and run as a non-secure application on nRF91's Cortex-M33.
   Therefore, it requires the :ref:`secure_boot` bootloader that prepares the required peripherals to be available for the application.
 
 .. _asset_tracker_user_interface:
@@ -53,7 +53,7 @@ LED 3 and LED 4:
     * LED 4 blinking: Pattern sent - Pattern has been entered and sent to nRF Cloud for verification.
     * LED 4 ON: Connected - The device is ready for sensor data transfer.
 
-    .. figure:: ../../../doc/nrf/images/nrf_cloud_led_states.svg
+    .. figure:: ../../doc/nrf/images/nrf_cloud_led_states.svg
        :alt: Application state indicated by LEDs
 
     Application state indicated by LEDs
@@ -66,13 +66,13 @@ All LEDs (1-4):
 Building and running
 ********************
 
-This sample can be found under :file:`samples/nrf9160/asset_tracker` in the |NCS| folder structure.
+This application can be found under :file:`applications/asset_tracker` in the |NCS| folder structure.
 
-The sample is built as a non-secure firmware image for the nrf9160_pca10090ns board.
+The application is built as a non-secure firmware image for the nrf9160_pca10090ns board.
 It can be programmed independently from the secure boot firmware.
 
 See :ref:`gs_programming` for information about how to build and program the application.
-The Kconfig file of the sample contains options to configure the sample.
+The Kconfig file of the application contains options to configure the application.
 For example, configure ``CONFIG_POWER_OPTIMIZATION_ENABLE`` to enable power optimization or ``CONFIG_TEMP_USE_EXTERNAL`` to use an external temperature sensor instead of simulated temperature data.
 In |SES|, select **Project** > **Configure nRF Connect SDK project** to browse and configure these options.
 Alternatively, use the command line tool ``menuconfig`` or configure the options directly in ``prj.conf``.
@@ -82,8 +82,7 @@ Alternatively, use the command line tool ``menuconfig`` or configure the options
 Power optimization
 ******************
 
-The Asset Tracker sample can run in three power modes that are configured in the
-Kconfig file of the sample.
+The Asset Tracker can run in three power modes that are configured in the Kconfig file of the application.
 
 Demo mode
 	This is the default setting.
@@ -102,7 +101,7 @@ Request Power Saving Mode (PSM)
 Testing
 =======
 
-After programming the :ref:`secure_boot` to your board, test the Asset Tracker sample by performing the following steps:
+After programming the :ref:`secure_boot` sample to your board, test the Asset Tracker application by performing the following steps:
 
 1. Connect the board to the computer using a USB cable.
    The board is assigned a COM port (Windows) or ttyACM device (Linux), which is visible in the Device Manager.
@@ -111,7 +110,7 @@ After programming the :ref:`secure_boot` to your board, test the Asset Tracker s
    Follow the instructions to set up your account and add an LTE device.
    A pattern of switch and button actions is displayed.
 #. Make sure that the :ref:`secure_boot` sample is programmed to the board.
-#. Compile and program the Asset Tracker sample to the board.
+#. Compile and program the Asset Tracker application to the board.
 #. Observe in the terminal window that the board starts up in secure boot and that the application starts.
    This is indicated by output similar to the following lines::
 
@@ -121,7 +120,7 @@ After programming the :ref:`secure_boot` to your board, test the Asset Tracker s
 
 #. Observe that LED 3 starts blinking as the LTE link is established. This may take several minutes.
 #. Observe in the terminal window that connection to nRF Cloud is established.
-#. The first time you start the sample, pair the device to your account:
+#. The first time you start the application, pair the device to your account:
 
    a. Observe that both LED 3 and 4 start blinking, indicating that the pairing procedure has been initiated.
    #. Follow the instructions on `nRF Cloud`_ and enter the displayed pattern.
@@ -141,7 +140,7 @@ After programming the :ref:`secure_boot` to your board, test the Asset Tracker s
 Dependencies
 ************
 
-This sample uses the following |NCS| libraries and drivers:
+This application uses the following |NCS| libraries and drivers:
 
     * :ref:`lib_nrf_cloud`
     * ``drivers/gps_sim``
diff --git a/doc/CMakeLists.txt b/doc/CMakeLists.txt
@@ -108,9 +108,11 @@ set(NRF_EXTRACT_CONTENT_COMMAND
   --outputs ${NRF_CONTENT_OUTPUTS}
   --ignore ${CMAKE_CURRENT_BINARY_DIR}
   "*:doc:${NRF_RST_OUT}"
+  "*.rst:applications:${NRF_RST_OUT}"
   "*.rst:samples:${NRF_RST_OUT}"
   "*.rst:boards:${NRF_RST_OUT}"
   "*.rst:include:${NRF_RST_OUT}"
+  "*.rst:applications:${NRF_RST_OUT}/doc/nrf"
   "*.rst:samples:${NRF_RST_OUT}/doc/nrf"
   "*.rst:boards:${NRF_RST_OUT}/doc/nrf"
   "release-notes*.rst:doc:${NRF_RST_OUT}/doc/nrf"
diff --git a/doc/nrf/applications.rst b/doc/nrf/applications.rst
@@ -0,0 +1,18 @@
+.. _applications:
+
+Applications
+############
+
+Applications typically include a fully integrated software stack and can serve as a starting point for developing your product.
+They use interface drivers and libraries from the |NCS| and its set of repositories to implement a specific use case.
+
+Some applications target custom hardware designed for a specific use case.
+They can also be run on different hardware like a generic development kit, but with limited functionality.
+
+The following applications are available:
+
+.. toctree::
+   :maxdepth: 1
+   :glob:
+
+   ../../applications/*/README
diff --git a/doc/nrf/examples.rst b/doc/nrf/examples.rst
@@ -0,0 +1,16 @@
+.. _examples:
+
+Samples and applications
+########################
+
+The `Zephyr Project`_ contains a variety of application samples and demos.
+Documentation for those is available in the :ref:`zephyr:samples-and-demos` section.
+
+Nordic Semiconductor provides additional examples that specifically target Nordic Semiconductor devices and show how to implement typical use cases with our libraries and drivers.
+Samples showcase a single feature or library, while applications include a variety of libraries to implement a specific use case.
+
+.. toctree::
+   :maxdepth: 2
+
+   samples
+   applications
diff --git a/doc/nrf/index.rst b/doc/nrf/index.rst
@@ -24,7 +24,7 @@ Documentation for different versions of the |NCS| is available at the following
    release_notes
    getting_started
    user_guides
-   samples
+   examples
    libraries
    reference/kconfig/index
 
diff --git a/doc/nrf/samples.rst b/doc/nrf/samples.rst
@@ -1,13 +1,12 @@
 .. _samples:
 
-Samples and demos
-#################
+Samples
+#######
 
-The `Zephyr Project`_ contains a variety of application sample and demos.
-Documentation for those is available in the :ref:`zephyr:samples-and-demos` section.
+For very simple samples, see the :ref:`zephyr:basic-sample` in Zephyr.
+Those samples are a good starting point for understanding how to put together your own application.
 
-Nordic Semiconductor provides additional examples that specifically target Nordic Semiconductor devices and show how to implement typical use cases with our libraries and drivers.
-The following demo applications are available:
+In addition, the |NCS| provides the following samples that showcase the use of a single feature or library:
 
 .. toctree::
    :maxdepth: 1
@@ -32,3 +31,5 @@ The following demo applications are available:
    :glob:
 
    ../../samples/*/README
+
+For more complex examples, see :ref:`applications`.
