You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Some background information should be made available for each airport, in order for users to have access to the diagrams, explanations, limitations on procedures, airspace boundaries, and other information required to understand how to effectively work in that particular airspace. This would be achieved through *.md files, as well as links to further readings, and charts, etc.
Additionally, each page should contain some links to relevant charts, diagrams, etc.
This issue should simply handle the arrangement of the framework and template for how we will display this information. Then individual issues and PRs can be created to fill out the content needed for each airport.
Some background information should be made available for each airport, in order for users to have access to the diagrams, explanations, limitations on procedures, airspace boundaries, and other information required to understand how to effectively work in that particular airspace. This would be achieved through
*.md
files, as well as links to further readings, and charts, etc.Additionally, each page should contain some links to relevant charts, diagrams, etc.
Related: #35.
Originally reported in zlsa/atc#612.
The text was updated successfully, but these errors were encountered: