Repository navigation
docs: refresh working group landing page and meeting index - #240
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Make Working Group participation and meeting history easier to navigate. Refresh the README with current work areas, contribution routes, quarterly meetings and the shared foundation project directory. Organize the meeting index by date, topic and presentation materials while preserving historical records. Link the current dynamic specification on the UXL website.
Depends on the foundation project-directory change, which will merge first.
Validation: local documentation link checker and its two tests pass; both changed reStructuredText documents render successfully; diff whitespace checks pass.
The repository owner reviewed side-by-side previews and explicitly requested publication and merge. If GitHub requires a separate reviewer, an administrator merge will apply that authorization after required automated checks pass; this does not represent an independent CODEOWNER review.