The ToC needs to have links to the *files* and that determines the
location of the article in the overall document structure.

Do not confuse this with internal reference *links* that are based on
the names. Although links get made if the ToC isn't hidden, that isn't
the way to create the references in the ToC.

Refer to docs/docs.beagleboard.io!105

The "expansion" section is meant to be about how to *build* expansion
hardware. This is where we provide information about what we expect
people to do when building add-on hardware, not about telling people how
to use it. They can infer how to use it, but that should really be
broken down into the "quick start", "design" and "demos" sections.

beagleplay: demo: Add low power video doorbell

See merge request docs/docs.beagleboard.io!104

Add a bunch of todo items and case fixups.
Also add a few links and info on how to write systemd shellscript

Signed-off-by: Dhruva Gole <d-gole@ti.com>

Fix formatting in BeagleBone Blue firmware flashing page (flashing-firmware.rst)

See merge request docs/docs.beagleboard.io!106

docs/docs.beagleboard.io!105

docs/docs.beagleboard.io!105

docs/docs.beagleboard.io!105

Helping out a little bit with docs/docs.beagleboard.io!105

Still need to move to sub-sections

Add docs for low power video doorbell demo made at EOSS 2024

Signed-off-by: Dhruva Gole <d-gole@ti.com>