Contributing

If you're reading this, you're likely interested in contributing to the Camellia Wiki - and we're excited to have you!

• Please keep all articles respectful, unbiased, and professional.
• Articles must be easy to understand and digest.
• Content must follow RFC 2119.
• Please ensure to use proper markdown for writing.
• All trademarks in any content must be correctly typed, including games, media, music, etc. For example: Discord, YouTube, BEMANI, etc.
• Any media uploaded, including videos and photos, must be one of the following: your own work; freely licensed; within the public domain; or under fair use.
• All articles must follow the correct format:

            ---layout: articletitle: Your Title Heredate: ISO 8601 (like 2025-07-08T04:04:53.522Z)description: Brief summary of what this article is about.image: An optional link to a cover image. (may be relative)---
        

A good portion (if not all) of the Camellia Wiki uses GitHub and Git. You will need to familiarize yourself with both GitHub and Git.

To begin your contribution journey, please ensure you have read and understand our standards. Next, you will need to fork the GitHub repository (or "repo" for short) that you wish to work on. This will allow you to create changes without affecting our main repos. Please fork one of the following:

• Articles (Site content): wiki-articles
• Frontend (The site in itself): wiki-frontend
• Backend (Provides content and other data to site): wiki-backend

Afterwards, you may begin your contribution edits.

If you are writing Wiki Articles, we have a fancy Preview system, which allows you to roughly view your changes, even in-time, as it would appear on the site.

Woohoo! If you've made it this far, congrats - it's time to check to ensure everything looks good and you've followed our standards. If you're sure that you're ready to go, please create a Pull Request on the main repo that you have forked. Code reviewers may be requested automatically, but you may request individuals when applicable.

Once your contribution(s) have been reviewed, you'll be notified whether your contribution(s) were merged or need further changes.

• If merged, you're all set and you can see them live.
• If not merged, the reviewer will usually leave a comment or two so you can go back and perform those necessary changes. Any changes made to your fork will automatically apply within the context of the Pull Request.

If you have any questions, comments, or concerns about anything in this guide or in general, feel free to let us know in the #💻dev-discussion channel in our Discord.