-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
Remove some community resources #1579
Remove some community resources #1579
Conversation
✅ Deploy Preview for expressjscom-preview ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
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.
LGTM!
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.
I am mostly okay with this. However, I would like "GitHub Discussion" be added as the community place for support.
@IamLizu If the other TC members agree, I’d be happy to add "GitHub Discussion" as a place for support. |
Thanks for this @bjohansebas, I've been wanting to do this for some time! Yes, please do add a link to https://github.com/expressjs/discussions. I see in expressjs/discussions#258 there was discussion of adding the Slack channel. I'd vote in favor of that, but that can be done in another PR; no need to hold up this one.
That's understandable, however, I'd like to ask that we try to keep all the langs in sync as much as possible. One does not need to read the language to delete the sections in question. Since the content is well-structured, simply do this:
@bjohansebas Can you please try to do that? If you run into difficulty, please comment here and I'll try to help. |
@crandmck I've noticed there are references to the wiki on GitHub. Should I also remove those links? |
The only links to the wiki I see are in "Moving to Express 4". We can leave those for now. If/when we decide to delete the wiki, we should do a thorough review of the content there to determine what needs to move into the docs and what can be simply deleted. |
* remove some community resources * remove some community resources in other langs * add github discussions
As we discussed here expressjs/discussions#258, some of the recommended resources on the page are no longer used by the community. Therefore, they will be removed so they are no longer recommended while we look for new options from a new community.
Notes: