wtf is docs?

This repository holds the documentation for SensorBee, which is a system for processing streams of data in real time. Rather than being a guide for end users, this repo is actually a style guide and template collection for the people writing SensorBee's documentation. The main job of this repository is to establish consistent formatting rules so that all the documentation looks and feels the same. The README defines a hierarchy of heading levels, think of it like an outline structure, using different symbol markers. For example, the biggest divisions use one symbol, chapters use another, sections use equals signs, and smaller subdivisions use dashes and other characters. By following these rules, anyone contributing to the docs can write in a standard way that matches the rest of the project. This type of repository is useful for teams that care about documentation quality and consistency. If you're building an open-source project, an internal tool, or any product that needs user-facing guides, having a shared documentation standard makes it easier for multiple people to contribute without creating a messy, inconsistent final product. New contributors can look at this repo and immediately understand how to format their additions. The README doesn't go into detail beyond the marker definitions, so it's likely meant to be paired with examples or templates stored elsewhere in the project. For someone maintaining or expanding SensorBee, this is a practical resource, it prevents the common problem where different writers use wildly different heading styles and structures, which can confuse readers and make documentation harder to maintain and update over time.