mary marchini

> "Foundation-blessed" seems irrelevant to me, only "node project-blessed", and the node project has blessed the prior two locations, officially, for years Just to be clear, what I meant by...

FYI opened https://github.com/nodejs/nodejs.org/pull/3619

I think it would be reasonable to automate an audit report of sorts, probably not opening an issue here but maybe sending to TSC and Moderation team emails.

I think we can do both using the `config-file` option, it takes a JSON file to configure the underlying markdown-link-check npm package: https://github.com/tcort/markdown-link-check#config-file-format. ```json { "ignorePatterns": [ { "pattern": "^http://example.net"...

Because we receive a new token on each run, and since the file is a JSON we can't set the authentication headers programatically on the config file. If markdown-link-check accepted...

I moved the issue to nodejs/build as I think it's the most relevant repository to continue this discussion (since there'll be work around setting up infrastructure). As discussed on Slack...

(sorry, I thought I replied here but apparently I forgot to hit "Comment" days ago :upside_down_face:) We have a nodejs.org DNS entry pointing to the dashboard now, and I moved...

Cool! I guess the only item missing to move it to the org is a `CONTRIBUTING.md`?

One thing I noticed (and don't have a good fix for) is that Node.js members won't be able to ping teams on the pkgjs org. Not sure if that's something...

There's a private repo, but it's more for feedback on beta features instead of new features. Sending the suggestion via support might be a good idea.