+<a name="file-naming-conventions">
+
+### How should files be named?
+Please adhere to [Kebap-Case](https://en.wikipedia.org/wiki/Letter_case#Special_case_styles) naming rules for any files in Codeberg Documentation.

+and PNG formats (webP and JPEG for photographs), they should be in a large enough resolution so that text is clearly
+readable and their filenames should follow Codeberg Documentation's [naming conventions](#file-naming-conventions).
+
+Please put screenshots under `assets/images/[section]/[article]/...` where `[section]` and `[article]` are the kebap-cased names of the section or your article, respectively.

+To contribute to Codeberg Documentation, the first thing you should do (if you haven't already done it) is to create your own fork of the [Codeberg/Documentation repository](https://codeberg.org/Codeberg/Documentation).
+
+Then, for each major contribution that you want to make (e.g. for each new article), create a new branch, make your contributions and finally make a Pull Request to the Codeberg/Documentation repository. You can find the source code to all articles in the `content` directory of Codeberg
+Documentation's source tree.

+
+Every section and article has a unique `key`. If `parent` is set to the `key` of another section, the current article will become a child of that other section.
+
+The other fields are `title` and `order`, where `title` is merely a display name and determines the menu entry label as well as the article's heading but has no other "technical" semantics and `order` is a number that can be used to enforce a specific order of articles (which is good for step-by-step guides such as Getting Started for example).

+> Please do not repeat the article's title as a first-level heading in Markdown. It will added automatically when generating the final site.
+
+### Can I preview my article?
+Yes, but currently only if you're working with a local clone of the repository. In that case, simply follow the instructions in the `README.md` file to set up and run a local preview.

+- For changes that are critical, e.g. ones that might legally affect Codeberg e.V., the chairperson of Codeberg e.V. will need to approve of the changes as well
+
+### Where to create example repositories?
+Please create example repositories for the Documentation in the `knut` organization on `codeberg-test.org`.