Nick

If there was a good example of this, it'll be good to consider. I'm not sure if there's too much trouble in just keeping the four registers in close proximity...

What if we defined registers in the current way: ```yaml registers: - Red: address: 0x00 length: 8 title: Red LED description: Red LED saturation - Blue: ... ``` And then...

Using the phrase "start" and "end" could be conflated in some environments, so it may be a good idea to see if it's possible to handle either direction. Additionally, we...

On https://arm-software.github.io/CMSIS_5/SVD/html/elem_registers.html, under the topic */device/peripherals/peripheral/registers/.../fields/field element*, CMSIS has several styles: * `bitOffset` (LSB) and `bitWidth` * `lsb` and `msb` * `bitRange` - A string in the format "[:]"

The lifecycle code would exist as additional functions which may present init or teardown logic. At the moment I only implemented support for register I/O until I get a better...

Looks like a good start. Putting everything into `docs/` will allow us to host with GitHub. Should we start looking for an easy domain to point to? (If this is...

If we build the docs, we'll need a host provider, as Google policy does not allow automated systems to make commits to a GitHub repository. And this could easily be...

Seems to be fine to get whatever domain name as it's not an official product. Edit: Nevermind

This should be merged with #71 and a new build script should handle deployments to cyanobyte.dev on the master branch from the `docs/` directory.

See [RegisterDevice API](https://cs.opensource.google/pigweed/pigweed/+/master:pw_i2c/public/pw_i2c/register_device.h;bpv=1;bpt=0) and [Getting Started](https://pigweed.dev/docs/getting_started.html#docs-getting-started)