-
-
Notifications
You must be signed in to change notification settings - Fork 207
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
Add Further reading
section
#286
Comments
Would it maybe make sense to include this in the tool itself, and propose a specific resource for each issue in the text? I feel like just adding a section to the readme and the website will not be as helpful because people might only use the tool itself without wanting to reading about it first. Also, I think a further reading section would either be too broad ( e.g. slave/master and white-listing are both examples of racist language but require different explanations as to why not to use them) or too specific (too many links/resources might deter readers). I would love to hear your opinion on this. I realise of course this would require a lot more work, so I'd still like to help with assembling a list of resources. |
Hi Effi! We have some of that in the tool indeed: some urls and short descriptions with reasoning and a bit more explanation. We could use more of that though. And as they’re about specific words: also useful, but very specific. The issue I want to solve here, is more of a broader explainer to educate folks in general about why language matters. Not lists of words to (not) use! alex is currently explained as something that solves your language, whereas I hope to shift that more to: humans solve language, here’s a list of resources to learn more about why that’s important, and: use alex to help catch some stuff! |
I can write a short blurb for the alex homepage, to get this started. I am planning to spend some time on open source/Hacktoberfest this upcoming Thursday. If anyone else wants to help out, let me know and we can collaborate! |
That’s awesome! Thanks Jen! And indeed: looking for more folks who have suggestions or want to help! |
@jenweber yes, absolutely! I should find the time sometime next week. |
Partially addresses get-alex#286 Capitalization
Related to: GH-286 Closes GH-306. Reviewed-by: Titus Wormer <[email protected]>
Problem
Expected behaviour
The readme, and the website, should answer this information, perhaps in the form as a list of prereqs, that answer 1, and some form of further exercises, that answer 2.
The text was updated successfully, but these errors were encountered: