This repository contains all of the code and content that powers Astro and Astronomer Software documentation.
If you notice something in our documentation that is wrong, misleading, or could use additional context, the easiest way to make an impact is to create a GitHub issue in this repository. To do so,
- Go to Issues
- Select New Issue
- Depending on the change you have in mind, select a GitHub issue template.
- Tell us what you think we can do better by answering the questions in the template.
GitHub issues are triaged by the Astronomer team and addressed promptly. Once you create a GitHub issue, our team may follow up with you with additional questions or comments. Once our team has addressed it, you'll get a notification via GitHub that the issue has been closed and that a change is now live.
If you'd like to contribute to Astronomer Docs directly, you are welcome to create a Pull Request (PR) to this repository with your suggested changes. To do so:
- Fork this repository
- Create a branch off of
main - Make your changes in that branch.
- Submit a PR for review.
Once you have submitted a PR for your changes, Netlify will add a comment to your PR that includes a link to a staging website with your changes.
Small edits and typo fixes don't need to be linked to an issue and should be merged quickly. To get a timely review on a larger contribution, we recommend first creating a detailed GitHub issue describing the problem and linking that within your PR.
Every update to the main branch of this repository will trigger a rebuild of our production documentation page at https://www.docs.astronomer.io. It might take a few moments for your merged changes to appear.
There are two core documentation folders: astro and software. These folders contain the primary Astronomer docsets that you see by default on Astronomer's documentation site. More specifically, software is equivalent Latest version of the Astronomer Software docset, which is the docset that users see by default when accesssing docs.astronomer.io/software.
An additional software_versioned_docs folder contains docsets for previous versions of Software. Whenever there's a new release of Astronomer Software, a new versioned docset is copied from software and added to this folder, with all links and sidebars updated automatically by Docusuaurs.
If you're working on a change in Software docs, you should work primarily in software. Make changes to software_versioned_docs only if your change is version-specific or a critical fix (e.g. incorrect/ out-of-date information).
If you want to submit a screenshot, GIF, or a new documentation file, we recommend building and testing your documentation change locally. Astronomer docs are built with Docusaurus, which is our static site generator. Read the following sections for instructions on how to build and test your documentation changes locally with Docusaurus.
Please read the Docusaurus documentation for information on installing the tools you'll need to work with Docusaurus locally.
To serve a local version of the docs site with your changes, run:
yarn startThis command both builds and serves your local changes. By default, your local build is accessible at localhost:3000. From here, any changes you save in your text editor will render on this local site in real time.