It should involve things such as description, s/w requirements, h/w requirements, schematics, usage etc.

Refer to the various Arduino project documentations for assistance.

Currently, the code formatting is not consistent across the project.

Preferred Formatting:

• Intend using tabs
• default tab size: 4

Use prettier to achieve the same

Hi,

We would like to ask for a review of the docs of Schleuder, a GPG-enabled mailing list manager with resending capabilities, and related projects:

• https://0xacab.org/schleuder/schleuder
• https://0xacab.org/schleuder/schleuder-cli
• https://0xacab.org/schleuder/schleuder-web
• https://0xacab.org/schleuder/schleuder-website

Thanks in advance, and for your work.

Cheers,
Georg

Add visualized image for each category

Hey, I was hoping to add a Header for the metrics in the Readme section. Let's use GitHub Actions for the optional header part.
The way we'll use it is with the actions.yml file. We can add a new inputs called Header and default to "" . If the user want to add a Header, he could add one. This in case will not break any of the current users stats and won't cause any issues(I hope it doesn't