Contributing to the Wiki
If you're reading this, then you're interested in helping us document the system via the Wiki, thank you! We want to make sure that contributing to the Wiki is as easy as possible so that anyone that would like to help us with this task can do so. In that light, some guidelines to contribute to the Wiki are outlined below.
Typically, a repository's Wiki can only be updated by the owners of that repo, this made community provided documentation cumbersome to include. In order to easily accept community provided documentation this repository is utilizing a GitHub Action which will generate the Wiki from any Markdown files merged to the publish-wiki branch's /wiki/ folder. If you would like to submit documentation to be included in the Wiki, please review the recommendations and the steps to open an Issue and submit a Pull Request below.
When submitting a Markdown file for consideration for the Wiki, we ask you to follow the style guide outlined here, this will ensure consistency between all of our wiki pages.
Use GitHub's Basic Formatting Syntax as a guide on how to format text with Markdown, as GitHub does not support all general Markdown formatting you may find in other guides.
When taking a screenshot or screen recording, all modules should be disabled. The wiki is intended for core System functionality only.
When adding an image or video, first upload the asset to the original Issue created for the update. This will provide us with a reliable link to that asset for use between your Fork and the dnd5e system.
Keep in mind that the maximum file size for an embedded file is 10MB, so using webm format or keeping the dimensions of the video small, such as only the size of the dialog box you are demoing, is a good way to keep within the 10M limit.
The name of your Markdown file is what will be used for the name of the Wiki Page in the table of contents, with hyphens turning into spaces, so My-first-Wiki-page.md will become My first Wiki page.
When you want to link to another page in the wiki, in your file make sure to link to the Markdown file in the wiki folder, the GitHub Action will automatically strip the .md extension and generate the appropriate link to the wiki page, for example linking to [Hyperlink Text](Advancement-Type-Hit-Points) in your documents will always generate a link to [Hyperlink Text](https://github.com/foundryvtt/dnd5e/wiki/Advancement-Type-Hit-Points) in the Wiki.
Always make sure to update the Home.md file with a link to your new Markdown file, as it serves ar the Wiki's homepage.
In order to let readers know what system release version a Wiki page is accurate for, please include a Version badge like the one below at the top of your page. When updating an existing wiki page, make sure to update this badge when relevant.
Just like any other Issue on the repo, the title should reflect a brief description of the task at hand, and the description should provide us with information about what will be added to the wiki. Make sure to include all of your assets in this issue, as mentioned in the style guide above.
Example: Review the Issue created for submitting this document you're currently reading here: Wiki - Create a Contributing to the Wiki guide
In order to contribute directly to the Wiki, you will need to fork the dnd5e repo and make a branch from the publish-wiki branch of the repo, then you will be able to add your Markdown files or update the existing files, and submit a Pull Request.
To contribute to the wiki, fork this project. Once you have forked the dnd5e repo, you will want to create a branch from the publish-wiki branch of the dnd5e repo. To do this, click on the Branches button, then click on New Branch. Give your new Branch a descriptive name, then make sure to update the Source to the upstream repository foundryvtt/dnd5eand select the publish-wiki branch. You only need to fork the dnd5e repo once, but you will create a new branch for each new issue/PR.
ForkandBranch.mp4
Either edit the existing files, or add your own Markdown files within the wiki folder of your newly created branch, when done click the Commit changes button, you will be asked to either Save and Merge or Create a New Branch, choose Save and Merge. This will commit the changes to your branch, keep in mind that each commit to the branch will be recorded and listed individually in your PR, so we recommend making sure to Preview your changes prior to commiting to catch any minor mistakes, or editing your files in a separate editor such as Notepad ++, VSCode, or your text editor of choice, to keep the PR as clean as possible.
SubmitandCommit.mp4
You will now be able to submit those changes back to the dnd5e system via a pull request (PR) against the publish-wiki branch.
From the main page of your repo, click the Contribute button and Open pull request for the system. When submitting a PR for the wiki, make sure the base repository is foundryvtt/dnd5e and the base branch is publish-wiki. Give the PR a name, and reference your original issue in the description.
Your PR is now submitted and will be reviewed by the repo maintainers!
Example: Review the PR created for submitting this document you're currently reading here: Create Contributing-to-the-Wiki.md
RequestaPull.mp4
You may want to make changes to your files, or may be asked to make changes by the repo maintainers. To do this, you will make those changes to the branch that your PR originated from, any new commits to your branch will automatically be applied to the PR for review.
The repo maintainers will merge your PR once all appropriate changes are made, the GitHub Action will automatically run, and your submission will be added to the Wiki page!