We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
The (new and exciting!) jupyter/accessibility documentation site mentions the JupyterLab accessibility meeting minutes on the Community page, but links to a jupyterlab/team-compass issue that only holds the meeting minutes up to March 2021. This means it does not have all the meeting minutes and presents them as a long list (which may be difficult to navigate).
The up to date Markdown file versions of these minutes are still in this repo and seem to be in the correct directory to appear on the Community page. It's just a matter of changing the link.
I don't know much about how this site is set up, but I'm happy to clean this up myself once I know what is desired. Do people want:
Thanks!
The text was updated successfully, but these errors were encountered:
Successfully merging a pull request may close this issue.
The issue
The (new and exciting!) jupyter/accessibility documentation site mentions the JupyterLab accessibility meeting minutes on the Community page, but links to a jupyterlab/team-compass issue that only holds the meeting minutes up to March 2021. This means it does not have all the meeting minutes and presents them as a long list (which may be difficult to navigate).
The good news
The up to date Markdown file versions of these minutes are still in this repo and seem to be in the correct directory to appear on the Community page. It's just a matter of changing the link.
Possible approaches
I don't know much about how this site is set up, but I'm happy to clean this up myself once I know what is desired. Do people want:
Thanks!
The text was updated successfully, but these errors were encountered: