-
-
Notifications
You must be signed in to change notification settings - Fork 28.1k
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 Technical Communication category #2486
Comments
This would be really great - the LaTeX list might also fit well here: https://github.com/egeerardyn/awesome-LaTeX#readme |
These two are also great candidates:
Edit: Naming the category "Technical and Scientific Writing" might be better at tackling the intersection of these two fields. |
This one made my day! Thanks for sharing.
Could be, but I'd keep "communication" over "writing" for a wider scope including other content types creation, information architecture, etc. |
@silopolis I was curious to your choice of "communication" instead of "writing", I think your explanation makes sense. |
I believe Quarto would also fit in that category instead of "Miscellaneous" #2550 |
If that's okay for a PR, it seems like the issue is actionable 👍 |
👍 PR welcome |
This category would group lists about technical documentation, developer experience etc.
For starters, it could host #1883 , #2424 and #2288
The following would be candidate entries:
The text was updated successfully, but these errors were encountered: