Thank you for contributing to the FTC community docs! You are enhancing the knowledge base for current and future FTC teams, making FTC better for everyone.
- Locate the page on the live website.
- Click the edit icon. The button is located to the right of the page title.
- Make your desired changes in the GitHub interface.
- Once you are done, click the green "Commit changes" button.
- Follow GitHub's instructions to create a pull request for your changes. For this type of change, set the target branch to
content.
Once you have made your changes, we will review them, and if they pass, we will merge your pull request and it will soon become part of the documentation.
- Go to
source/docsfolder in GitHub. - Open the appropriate folder based on the topic of your new page.
- Create a new
.mdfile. - Title your file:
- On line 1, put
#in front of your page title.
- On line 1, put
- Populate your file with the information you wish to add.
- Once you are done, click the green "Commit changes" button.
- Optional: If you feel inclined to make your page visible, you may do so. Otherwise, skip this step and we can do this for you.
- Open
source/mkdocs.yml. - Locate the
navproperty (this is located at the top). - Add the path to your file in the appropriate location.
- Once you are done, click the green "Commit changes" button.
- Open
- Follow GitHub's instructions to create a pull request for your changes. For this type of change, set the target branch to
content.
- Go to
source/docs/teamsfolder in GitHub. - Create a file with this format:
[team-number].md- If your team number is
12345, name your file12345.md.
- If your team number is
- Populate your file with the information you wish to add.
- Once you are done, click the green "Commit changes" button.
- Optional: If you feel inclined to make your page visible, you may do so. Otherwise, skip this step and we can do this for you.
- Open
source/mkdocs.yml. - Locate the
navproperty (this is located at the top). - In the
Teamssection, add an entry for your new page with the following format:teams/[team-number].md. Mind the numerical order. - Once you are done, click the green "Commit changes" button.
- Open
- Follow GitHub's instructions to create a pull request for your changes. For this type of change, set the target branch to
content.
- Fork this repository.
- Clone your fork onto your machine.
- Create a virtual Python enviornment for this repository.
- Install the dependencies from the list contained in
source/requirements.txt. - Navigate to the root folder of this repository in your terminal
- Run the appropriate activation script for your virtual enviornment and system
- Change your directory to
source - Run
mkdocs serve, and open the link it outputs in your browser. - Make your desired changes.
- You may need to update
requirements.txtif your changes require another Python library to build the website
- You may need to update
- After verifying your changes work, push the code to your fork.
- Contribute your fork as a PR, and set the target branch to
config.