-
-
Notifications
You must be signed in to change notification settings - Fork 9
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
Update glossary items #94
Comments
@OscarSiba Had you decided whether to keep the glossary in the handbook or in the existing glossary (https://github.com/carpentries/community-engagement/blob/main/glossary.md)? As we have a lot to do, it may be easier to keep the existing glossary as it is, and consider moving it to the handbook later. |
We will eventually move this to the Handbook later, but let us keep it where it is for now while we deal with more pressing issue. We can link to it under the Resources section. |
Thanks @OscarSiba |
Discussed with @OscarSiba |
@OscarSiba I am working on transferring the glossary from this repo into the handbook. You noted the content is complete but I want to double check with you as I see some things that are out of date. For example:
I have not gone through everything but I saw those as I went through the first few letters of the alphabet. Would you and/or the CET be able to review this before I transfer everything to the handbook? Thanks! Assigning back to you for now. Please assign back to me when your updates are complete. |
Thanks @maneesha - have added this to the CET meeting agenda garage. |
We now have a single glossary page: https://carpentries-beta-handbook-preview.netlify.app/pages/glossary.html
Most of the items are missing definitions, so definitions need to be added in. Definitions can be added by replacing the text "definition goes here" with the intended definition. Be sure the definition text is indented.
We also need to identify cross-referenced items (currently noted as "See also..."). @brynnelliott has identified this as ableist language. We should decide what language we want to use instead of that before creating all these cross-referenced links, so we don't have to update them all later.
The text was updated successfully, but these errors were encountered: