-
Notifications
You must be signed in to change notification settings - Fork 72
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
docs: QRH inital commit #897
base: primary
Are you sure you want to change the base?
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
This PR is being prevented from merging because Review Required. Use the Approved label to run build validation and auto merge the PR. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Question did you mean to make this page as a directory or just as a standalone page -- as the dual heading is a little ugly on the front end.
Additionally, this is a great idea! I would hazard a convenience redirect in the config that's like:
docs.com/qrh
I'll think of new things to add to this.
Summary
Add a QRH for common operational problems or failures from the EFB failure page / Generator.
Feel free to add more.
Location
Discord username (if different from GitHub): slein15