To keep device information consistent, use a small per device database
embedded in the frontmatter of the device page source.
Device information is extracted from the database and formatted into
tables with the provided shortcodes
The data can then further be used to build comparison tables and filters for
specific usecases.
New devices should make use of the provided archetype, which provides an
example of most used fields:
```
hugo new content/hardware/my-device.md
```
Fixes: #5
Some pages require a scroll bar, some do not. If the scroll bar is
hidden on a page that do not require it (default behavior of most
browsers), centered content is shifted to the right slightly.
Fix this behavior by using the scrollbar-gutter property, so the
renderer automatically reserves space for the scrollbar.
Changelogs haben auf der Releases-Seite im gitea bereits einen gut zu
lesenden Platz. Daher sollten diese nicht noch einmal getrennt davon in
der Dokumentation gepflegt werden müssen.
Currently all even table rows are dimmed down to help the reader's
orientation. The problem is that <tr> elements within a table are
further split into sections of <thead> and <tbody>. As a result, the
counter is not the some for all <tr> in the table, but there are two
separate counters for elements within <thead> and <tbody> respectively.
This can be visually distracting since the table appears to start with 2
light rows and only then the pattern of alternating backgrounds begins.
For most cases dimming the table headers works fine to help with this
issue.
Fixes: #23