zephyr

Currrently, if users are viewing a sample keymap file, and trying to understand all the behaviors they see there, they need to dig into our individual behavior docs to find each one.

It would be nice to have an aggregated index/lookup page, at the top of the "Behaviors" nested sidebar section, that gives has a table from "sample behavior" to the docs describing that behavior.

repo forall defines a useful set of environment variables for the duration of each call:

• REPO_PROJECT is set to the unique name of the project.
• REPO_PATH is the path relative to the root of the client.
• REPO_REMOTE is the name of the remote system from the manifest.
• REPO_LREV is the name of the revision from the manifest, translated to a local tracking branch. Used if you need to pass

The pinetime watch has a small motor to produce vibration. Let's imake it work !

The motor is plugged on the GPIO P0.16 of the NRF52. See image.

I guess simply driving low and high this GPIO would make it work.
We will need some kind of thread or timer if we want to make some spec

Please start with a use case description for a USER of this enhancement

[Who] As an application developer

[What] I need to use Herald classes with or instead of C++ STL classes in a compatible way, interchangeably

[Value] In order to achieve the principle of least astonishment to the use of the Herald API (thus saving me time during development)

**Describe the potential solution y