# ✍️ How to Contribute to This Documentation > [!abstract] About > This vault is **participative**. If you have notes, tutorials, fixes, screenshots or drafts that would fit in **KNOWLEDGE** or **PROTOCOL**, you can send them through any of the channels below — I'll review and integrate them into the public documentation. --- ## 🧭 TL;DR > [!tip] Two ways to contribute today > 1. **📁 Drop a file in the shared Google Drive** — simplest, best for artists. > 2. **💬 Send it on Discord** — fastest for short notes, screenshots or questions. > > A **GitHub pull-request workflow** will come later. --- ## 1. 📁 Google Drive — "Submissions" folder > [!example] Link > **[Open the shared submissions folder on Google Drive](https://drive.google.com/drive/folders/1zn5QdNiD6t7quEw9u8sI6uhhECLfqnfa?usp=drive_link)** ### How to submit 1. Open the Drive folder via the link above. 2. Create a new folder named after your Name — e.g Thomas Spony 3. Inside that folder, put: - The **note itself** as a `.md` file, a Google Doc, or a plain `.txt` — whatever is easiest for you. - All **attachments** (screenshots, reference images, small videos, PDFs…). 4. If relevant, add a short `README.txt` explaining: - **Who** you are (so you can be credited). - **Any context** the reader needs. --- ## 2. 💬 Discord — `#PROTOCOL channel > [!example] Link > Join Our discord with this link, if you want to make project together : https://discord.gg/bDYbfZfdhA > **[Open the Discord documentation channel](https://discord.com/channels/1204552429866324079/1220178487940481145)** ### How to submit - Drop your note, screenshot, reference, link or question directly in the channel. - Mention me (`@alte`) if you'd like it reviewed quickly. - If you have a longer draft, paste it as a message, upload a `.md` / `.txt` file, or paste a Drive / Doc link. ### What happens next - Same as the Drive workflow — I review, reformat, integrate, and credit you. > [!info] Best for > Short notes, quick tips, one-off corrections, a single screenshot, or asking a question before writing a full note. --- ## 3. 🐙 GitHub Pull Requests *(coming soon)* Once the vault is published on GitHub, contributors will be able to: - Fork the repository. - Add or edit a `.md` note and its attachments. - Open a **pull request** for review line-by-line. This path is **not live yet** — use Google Drive or Discord in the meantime. --- > [!warning] Please avoid > - **NDA / studio-confidential material** — don't send anything from a studio pipeline you are under NDA with. > - **Screenshots exposing personal info** (paths with your username, tokens, credentials…). > - **Copying copyrighted material** (full course content, books, paid tutorials) — link to the source instead. --- ## 🙏 Thanks Big thanks to the first contributors who made this documentation possible: **Loris Eck, Leo Hanrion, Viktor Weiss, Arthur Cauchois, Fabio Sguerra, Thomas Milcamps, Tristan Goupy, Erwan Vaquet.** --- ## 🔗 Related - [[THE PROTOCOL VAULT|THE PROTOCOL VAULT]] — vault landing page. - [[KNOWLEDGE/KNOWLEDGE MOC|KNOWLEDGE MOC]] — software & theory index. - [[PROTOCOL/PROTOCOL MOC|PROTOCOL MOC]] — pipeline index.