-
Notifications
You must be signed in to change notification settings - Fork 16.2k
docs: move organizational info docs to new directory #17865
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
Conversation
a6bb605
to
3d289c1
Compare
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.
🚲 🏚 "organizational" is a word I don't think I've seen used for administrivia kinds of docs on websites (not that I'm advocating for "administrivia", mind you). I can't think of a better word at the moment, though.
I'm mostly worried about what it'll look like on the website, as you mentioned in the summary.
@malept agree, i spent 15 minutes just struggling to find a new name 😅 totally open to suggestions! |
bb28166
to
37e1a69
Compare
@codebytere @malept 🤔what do you think of these? So far I think organizational is a good one to begin with if we cannot think of a better term. |
I think leaving them "top level" is fine for now. |
37e1a69
to
497b3bf
Compare
Release Notes Persisted
|
* docs: move organizational info docs to new directory * fix some markdown lint issues
Description of Change
This moves our important ecosystem documentation for consumers into a bespoke directory. Please feel free to comment if you think more documents should be moved here or it should be organized differently. This will also require changes to the website, so i'd love to hear ya'lls thoughts!
/cc @electron/wg-docs-tools @electron/wg-website
Checklist
npm test
passesRelease Notes
Notes: Moved some administrative documentation to a clearer location.