-
Notifications
You must be signed in to change notification settings - Fork 6.3k
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 Status Page link to README / and/or website #7050
Comments
+1 to put on:
|
Can we have bage for the current status ? |
On the website? |
For the read me |
Makes sense, feel free to add a badge to README. |
it's was a question is it possible to have a badge ? |
bump @ovflowd |
Last i checked you needed JS |
I think there are two issues here:
I feel like if we (as @AugustinMauroy mentioned) add a statement to the bottom of the "About" page, we can knock two birds with one stone. Something like the following, right?: Official Node.js ResourcesTo ensure authenticity and security when working with Node.js, always use official sources. Avoid trusting emails, Official Node.js DomainsFor downloading Node.js binaries and accessing official documentation, use only these domains: Official npm PackagesThe Node.js team maintains the following official npm package scopes:
Additionally, the Node.js team maintains packages published by the Using packages from these scopes and accounts guarantees that you are working with officially supported Node.js components. Official GitHub OrganizationsNode.js and related projects are maintained under these official GitHub organizations: Official Communication ChannelsNode.js and the OpenJS Foundation communicate through various official and community-supported channels. You can find details on Reporting Website Issues & DowntimeIf you encounter issues with the Node.js website, report them at the Node.js website repository. |
IMO you should open a pr with this content |
On it! Just wanted to verify that that content was suitable first, opening a PR now. |
Enter your suggestions in details:
Today I learned that we had a status page at https://status.nodejs.org/ - I see nodejs/build#2265 but no real mention of teaching people about it. I've been involved with the project for over a year and first learned about it.
Also, I acknowledge that putting on the site (or maybe just the README) is ironic if the site itself is down. Relates to nodejs/build#2265 (comment)
If nothing else, this helps people learn about this communication tool for status and for resolutions.
The text was updated successfully, but these errors were encountered: