fix: remakr-lint-no-literal-urls

nschonni · nschonni · commit 748682f55816 · 2020-05-04T02:18:33.000-04:00
diff --git a/OKR.md b/OKR.md
@@ -31,8 +31,8 @@ Here are some external references that may help provide further context on OKRs.
   * **Key Result:** Create a feature roadmap
   * **Key Result:** Track features & priorities in one place (project?)
   * **Key Result:** Make available the top two features in nodejs.org:
-    1. Docs — https://nodejs.org/en/docs/
-    2. Download — https://nodejs.org/en/download/
+    1. Docs — <https://nodejs.org/en/docs/>
+    2. Download — <https://nodejs.org/en/download/>
 
 * **Objective:** Make explicit the channels of interfacing internally and with larger org
   * **Key Result:** Write down implicit team norms
diff --git a/meetings/2018-02-01.md b/meetings/2018-02-01.md
@@ -18,7 +18,7 @@
 ### General objectives, strategy going forward
 
 * Olivia, Tierney: We should ensure that goals are long-term
-* Adam: Rediscussing the points listed in https://github.com/nodejs/nodejs.org/issues/1534
+* Adam: Rediscussing the points listed in <https://github.com/nodejs/nodejs.org/issues/1534>
 * Adam: Site Structure, Design, Implementation
 * Adam: In that order
 * Olivia: Previous discussions have been too implementation-focused
@@ -28,7 +28,7 @@
 
 ### Overall site structure
 
-* See also https://github.com/nodejs/nodejs.org/issues/1534 (Assess current site structure, see what's needed and what's not).
+* See also <https://github.com/nodejs/nodejs.org/issues/1534> (Assess current site structure, see what's needed and what's not).
 
 * Frederic: History of website. There never was a well defined content structure, it was made as needed.
 * Jeremiah: brief notes on iojs.org's design
@@ -40,7 +40,7 @@
 * Olivia: Suggestion to start. What do we have now, a sort of site map. Then go from there.
 * Frederic: volunteers to write up a site map of the existing site (link)
 * Tierney, Jeremiah: discussion of how the node api docs are maintained somewhat separate.
-* Adam: Overview of his blog post write up which compares to other "competeting" websites in some detail: https://medium.com/the-node-js-collection/redesigning-nodejs-part-1-fac08a0e015a
+* Adam: Overview of his blog post write up which compares to other "competeting" websites in some detail: <https://medium.com/the-node-js-collection/redesigning-nodejs-part-1-fac08a0e015a>
 * Fransisco: what are the main goals of the current website?
 * Tierney: Primary uses of site to date: Downloads, information, Documentation, Getting involved.
 
@@ -50,7 +50,7 @@
 * Frederic: I want to see the Code of Conduct, governance docs, etc, directly. Should be part of the website.
 * Adam: I'd love to see some "Learn" page, a normal-language guided tour. Something more comprehensive and ergonomic.
 * Adam: We may not need to write this content as it may already exist and we may be able to get it contributed back.
-* Frederic: The getting started guides are currently at https://nodejs.org/en/docs/guides/getting-started-guide/, needs to be surfaced better. As does the introduction https://nodejs.org/en/about/.
+* Frederic: The getting started guides are currently at <https://nodejs.org/en/docs/guides/getting-started-guide/>, needs to be surfaced better. As does the introduction <https://nodejs.org/en/about/>.
 * Adam: The site should feel more cohesive.
 * Timothy: I don't really agree - have seen other examples where the docs and main site work for different purposes.
 * Adam: Some things should probably look the same as the home page, e.g. the 'getting started'.
@@ -66,7 +66,7 @@
 
 ### Decision structure (consensus, etc.)
 
-* There is a Foundation marketing committee. Check with Greg (gwallace@linuxfoundation.org)
+* There is a Foundation marketing committee. Check with [Greg](mailto:gwallace@linuxfoundation.org)
 * Tierney: I sit on that committee as part of my job, and it is a pretty open group.
 
 * Discussion of existing consensus-seeking model, seems acceptable (lazy consensus).
diff --git a/meetings/2018-02-15.md b/meetings/2018-02-15.md
@@ -17,7 +17,7 @@ Order in the agenda will be rearranged to prioritize issues
 * group discussed overall structure proposed by Adam, no objections were raised
 * wireframe the suggestions and share to github
 * TODO: Set up balsamiq and get a GDoc configured with it
-https://chrome.google.com/webstore/detail/balsamiq-wireframes-for-d/jmebhflpaooegildgjfecegknjahhfki?hl=en
+<https://chrome.google.com/webstore/detail/balsamiq-wireframes-for-d/jmebhflpaooegildgjfecegknjahhfki?hl=en>
 * Sub-sites of nodejs.org
 
 ### Getting started section #9
@@ -32,8 +32,8 @@ https://chrome.google.com/webstore/detail/balsamiq-wireframes-for-d/jmebhflpaooe
 ### Updating Node.js messaging #242 (in CommComm)
 * Also discussed in nodejs.org/#1534:
   Examples:
-  * http://styleguide.mailchimp.com
-  * http://voiceandtone.com
+  * <http://styleguide.mailchimp.com>
+  * <http://voiceandtone.com>
 * messaging is old and may have been outgrown
 * Existing content in Evangelism repo: Social Media Style Guide
 * Must make sure to collaborate with the Foundation to make sure of buy in
diff --git a/meetings/2018-03-15.md b/meetings/2018-03-15.md
@@ -48,6 +48,6 @@ TODO Tierney: Organize another meeting between NodeSchool and the Website Redesi
 
 ## Upcoming Meetings
 
-* **Node.js Foundation Calendar**: https://nodejs.org/calendar
+* **Node.js Foundation Calendar**: <https://nodejs.org/calendar>
 
 Click `+GoogleCalendar` at the bottom right to add to your own Google calendar.
diff --git a/meetings/2018-03-29.md b/meetings/2018-03-29.md
@@ -18,7 +18,7 @@
 * there was also an understanding that we would get content from them
 * depending on the amount of engagement we can start with content and go from there
 * maybe instead of going to Nodeschool, go straight to the Learnyounode repo maintainers
-* https://github.com/workshopper/learnyounode
+* <https://github.com/workshopper/learnyounode>
 * reiterate having a dedicated meeting with open invitation. "We're using what you have as a foundation. We'd like to have you involved."
 * TODO: Tierney creating an issue for dedicated meeting
 
@@ -43,7 +43,7 @@
 * TODO: review to come
 
 #### Content Structure [#4](https://github.com/nodejs/website-redesign/issues/14)
-* suggest that we have a Branding page in the Community section, in a similar vein to what Webpack does: https://webpack.js.org/branding/
+* suggest that we have a Branding page in the Community section, in a similar vein to what Webpack does: <https://webpack.js.org/branding/>
 * we need consistency to help inform colour palettes, and the correct spelling of Node.js, assets; for the benefit of anyone working in design and community
 
 ## Announcements
@@ -55,6 +55,6 @@
 
 ## Upcoming Meetings
 
-* **Node.js Foundation Calendar**: https://nodejs.org/calendar
+* **Node.js Foundation Calendar**: <https://nodejs.org/calendar>
 
 Click `+GoogleCalendar` at the bottom right to add to your own Google calendar.
diff --git a/meetings/2018-04-12.md b/meetings/2018-04-12.md
@@ -2,9 +2,9 @@
 
 ## Links
 
-* **Recording**: https://www.youtube.com/watch?v=YJaBlwCfg1o
-* **GitHub Issue**: https://github.com/nodejs/website-redesign/issues/30
-* **Minutes Google Doc**: https://docs.google.com/document/d/148YR77GBZf10B45zFR0BTppbrCT3IghE40I3dxOT1kk/edit
+* **Recording**: <https://www.youtube.com/watch?v=YJaBlwCfg1o>
+* **GitHub Issue**: <https://github.com/nodejs/website-redesign/issues/30>
+* **Minutes Google Doc**: <https://docs.google.com/document/d/148YR77GBZf10B45zFR0BTppbrCT3IghE40I3dxOT1kk/edit>
 
 ## Present
 Manil Chowdhury (@chowdhurian)
@@ -61,6 +61,6 @@ Welcome @codeekage to the team! Happy to have you!
 
 ## Upcoming Meetings
 
-* **Node.js Foundation Calendar**: https://nodejs.org/calendar
+* **Node.js Foundation Calendar**: <https://nodejs.org/calendar>
 
 Click `+GoogleCalendar` at the bottom right to add to your own Google calendar.
diff --git a/meetings/2018-04-26.md b/meetings/2018-04-26.md
@@ -2,13 +2,13 @@
 
 ## Links
 
-* **Recording**: https://www.youtube.com/watch?v=M2pLEkJuCEk
-* **GitHub Issue**: https://github.com/nodejs/website-redesign/issues/38
-* **Minutes Google Doc**: https://docs.google.com/document/d/1qj9JJRzbO-cCbwG5-NZeQF5A3avSe1G-NfkOC7BLplY/edit
+* **Recording**: <https://www.youtube.com/watch?v=M2pLEkJuCEk>
+* **GitHub Issue**: <https://github.com/nodejs/website-redesign/issues/38>
+* **Minutes Google Doc**: <https://docs.google.com/document/d/1qj9JJRzbO-cCbwG5-NZeQF5A3avSe1G-NfkOC7BLplY/edit>
 
 ## Present
 * @amiller-gh (Adam Miller)
-* @jennschiffer (Jenn Schiffer, community engineer glitch, https://glitch.com/forteams)
+* @jennschiffer (Jenn Schiffer, community engineer glitch, <https://glitch.com/forteams>)
 * @bnb (Tierney Cyren)
 * @chowdhurian (Manil Chowdhury)
 * @tolmasky (Francisco)
@@ -41,11 +41,11 @@ Dropped / punted for now.
 * Make Call for Proposals ready to launch by date of the Collab Summit. Launch at Collab Summit
 
 #### Tech Exploration for In-Browser Node.js Playground [#12](https://github.com/nodejs/website-redesign/issues/12)
-* Jenn Schiffer presented a bit of history around Glitch and their platform. See: https://glitch-nodejsorg.glitch.me/
+* Jenn Schiffer presented a bit of history around Glitch and their platform. See: <https://glitch-nodejsorg.glitch.me/>
 * Glitch has no lock-in. Everything can be exported to github or downloaded in a zip.
 * Existing features are free in perpetuity. "For Teams" to be launched as paid. It will be available to Nodejs.org for free.
 * Glitch would make it the BE more visible to frontend developers.
-* related: https://github.com/nodejs/website-redesign/issues/39
+* related: <https://github.com/nodejs/website-redesign/issues/39>
 * Eg. Runkit to improve docs, Glitch to make interactive Getting Started content
 
 #### Identify topics to discuss for Collab Summit Spring 2018 [#29](https://github.com/nodejs/website-redesign/issues/29)
@@ -62,10 +62,10 @@ Dropped / punted for now.
 
 ## Q&A, Other
 
-* Glitch demo: https://glitch-nodejsorg.glitch.me/
+* Glitch demo: <https://glitch-nodejsorg.glitch.me/>
 
 ## Upcoming Meetings
 
-* **Node.js Foundation Calendar**: https://nodejs.org/calendar
+* **Node.js Foundation Calendar**: <https://nodejs.org/calendar>
 
 Click `+GoogleCalendar` at the bottom right to add to your own Google calendar.
diff --git a/meetings/2018-05-10.md b/meetings/2018-05-10.md
@@ -2,9 +2,9 @@
 
 ## Links
 
-* **Recording**: https://youtu.be/CnccqFY2HFw
-* **GitHub Issue**: https://github.com/nodejs/website-redesign/issues/40
-* **Minutes Google Doc**: https://docs.google.com/document/d/1nBFsEmAdSAhqBoHXCpC8qAHbXLTJGieGdpBi2M-msyI/edit
+* **Recording**: <https://youtu.be/CnccqFY2HFw>
+* **GitHub Issue**: <https://github.com/nodejs/website-redesign/issues/40>
+* **Minutes Google Doc**: <https://docs.google.com/document/d/1nBFsEmAdSAhqBoHXCpC8qAHbXLTJGieGdpBi2M-msyI/edit>
 
 ## Present
 
@@ -71,6 +71,6 @@ Adam: This WG should function, among other things, as a design management body s
 
 ## Upcoming Meetings
 
-* **Node.js Foundation Calendar**: https://nodejs.org/calendar
+* **Node.js Foundation Calendar**: <https://nodejs.org/calendar>
 
 Click `+GoogleCalendar` at the bottom right to add to your own Google calendar.
diff --git a/meetings/2018-05-24.md b/meetings/2018-05-24.md
@@ -2,9 +2,9 @@
 
 ## Links
 
-* **Recording**: https://youtu.be/2gqCrBBiavs
-* **GitHub Issue**: https://github.com/nodejs/website-redesign/issues/50
-* **Minutes Google Doc**: https://docs.google.com/document/d/1gcQExgTMVkDx440IvfQOmQ9hLxMcd7Y2mCfj-Jp270s/edit
+* **Recording**: <https://youtu.be/2gqCrBBiavs>
+* **GitHub Issue**: <https://github.com/nodejs/website-redesign/issues/50>
+* **Minutes Google Doc**: <https://docs.google.com/document/d/1gcQExgTMVkDx440IvfQOmQ9hLxMcd7Y2mCfj-Jp270s/edit>
 
 ## Present
 
@@ -39,6 +39,6 @@
 
 ## Upcoming Meetings
 
-* **Node.js Foundation Calendar**: https://nodejs.org/calendar
+* **Node.js Foundation Calendar**: <https://nodejs.org/calendar>
 
 Click `+GoogleCalendar` at the bottom right to add to your own Google calendar.
diff --git a/meetings/2018-05-31.md b/meetings/2018-05-31.md
@@ -3,9 +3,9 @@
 ## Links
 
 * **Recording**: `<Recording URL>`
-* **Slides**: https://docs.google.com/presentation/d/1gGwqydeSHa8CsqZW49X9u7AL0BUrxuao-oZXYox2c5k/edit
-* **GitHub Issue**: https://github.com/nodejs/summit/issues/89
-* **Minutes Google Doc**: https://docs.google.com/document/d/1vqo9KOkyKP8q9cirpjqEcYnuv1NpUClPhFgEUioPMXc/edit
+* **Slides**: <https://docs.google.com/presentation/d/1gGwqydeSHa8CsqZW49X9u7AL0BUrxuao-oZXYox2c5k/edit>
+* **GitHub Issue**: <https://github.com/nodejs/summit/issues/89>
+* **Minutes Google Doc**: <https://docs.google.com/document/d/1vqo9KOkyKP8q9cirpjqEcYnuv1NpUClPhFgEUioPMXc/edit>
 
 ## Present
 @amiller-gh (Adam Miller)
diff --git a/meetings/2018-09-13.md b/meetings/2018-09-13.md
@@ -2,9 +2,9 @@
 
 ## Links
 
-* **Recording**: https://www.youtube.com/watch?v=Ye3_j4LkxDg
-* **GitHub Issue**: https://github.com/nodejs/website-redesign/issues/89
-* **Minutes Google Doc**: https://docs.google.com/document/d/1Sk_Ni8l_z0l7BGzvKqX8Kr9_v-eVA-aZJJn95fNqd-c/edit
+* **Recording**: <https://www.youtube.com/watch?v=Ye3_j4LkxDg>
+* **GitHub Issue**: <https://github.com/nodejs/website-redesign/issues/89>
+* **Minutes Google Doc**: <https://docs.google.com/document/d/1Sk_Ni8l_z0l7BGzvKqX8Kr9_v-eVA-aZJJn95fNqd-c/edit>
 
 ## Present
 
@@ -22,11 +22,11 @@
 * Creating a branch of the Docs using RunKit [#21723](https://github.com/nodejs/node/issues/21723)
 
 Progress is good! PR is made. Only things left is bikeshedding.
-PR: https://github.com/nodejs/node/pull/22831
+PR: <https://github.com/nodejs/node/pull/22831>
 
 Adam: Live demo of changes would be nice, or at least screenshots for visual review.
 
-Tierney: Example of syntax highlight here: https://nodejs.org/en/docs/guides/nodejs-docker-webapp/
+Tierney: Example of syntax highlight here: <https://nodejs.org/en/docs/guides/nodejs-docker-webapp/>
 
 **ACTION ITEM:** @tomalsky to provide screenshots or live demo for visual review on PR 22831.
 
@@ -48,7 +48,7 @@ No major updated here. Removing label. Will integrate when we start buildout.
 
 Adam: Mentioned LinkedIn Learning intro videos offer. 7-10 custom recorded videos to introduce major content type areas.
 
-Manil: Can't prioritize current list. Is there a tool we can use to help prioritize here? This one works well: https://www.uservoice.com/
+Manil: Can't prioritize current list. Is there a tool we can use to help prioritize here? This one works well: <https://www.uservoice.com/>
 
 Tierney: May get a little confusing, but could be useful!
 
@@ -86,6 +86,6 @@ Tierney provided extra context to add. Manil will work with the author at their
 
 ## Upcoming Meetings
 
-* **Node.js Foundation Calendar**: https://nodejs.org/calendar
+* **Node.js Foundation Calendar**: <https://nodejs.org/calendar>
 
 Click `+GoogleCalendar` at the bottom right to add to your own Google calendar.
diff --git a/meetings/2018-09-27.md b/meetings/2018-09-27.md
@@ -2,9 +2,9 @@
 
 ## Links
 
-* **Recording**: https://www.youtube.com/watch?v=dTh1VPFJgHY
-* **GitHub Issue**: https://github.com/nodejs/website-redesign/issues/97
-* **Minutes Google Doc**: https://docs.google.com/document/d/1dqeoPhKc7PfX8zh9UzkkFKchTcUvAZhINB39ExqOk6I/edit
+* **Recording**: <https://www.youtube.com/watch?v=dTh1VPFJgHY>
+* **GitHub Issue**: <https://github.com/nodejs/website-redesign/issues/97>
+* **Minutes Google Doc**: <https://docs.google.com/document/d/1dqeoPhKc7PfX8zh9UzkkFKchTcUvAZhINB39ExqOk6I/edit>
 
 ## Present
 
@@ -55,6 +55,6 @@ ACTION ITEM @ammilelr-gh – Reach out to flavio.
 
 ## Upcoming Meetings
 
-* **Node.js Foundation Calendar**: https://nodejs.org/calendar
+* **Node.js Foundation Calendar**: <https://nodejs.org/calendar>
 
 Click `+GoogleCalendar` at the bottom right to add to your own Google calendar.
diff --git a/meetings/2018-1-17.md b/meetings/2018-1-17.md
@@ -54,6 +54,6 @@
 
 ## Upcoming Meetings
 
-* **Node.js Foundation Calendar**: https://nodejs.org/calendar
+* **Node.js Foundation Calendar**: <https://nodejs.org/calendar>
 
 Click `+GoogleCalendar` at the bottom right to add to your own Google calendar.
diff --git a/meetings/2018-10-13.md b/meetings/2018-10-13.md
@@ -2,7 +2,7 @@
 
 ## Links
 
-* **Minutes Google Doc**: https://docs.google.com/document/d/16eRahz4dmoEBCyISoRr721Rg9gjCEXVRKVsz0RvxcUw/edit
+* **Minutes Google Doc**: <https://docs.google.com/document/d/16eRahz4dmoEBCyISoRr721Rg9gjCEXVRKVsz0RvxcUw/edit>
 
 ## Present
 
@@ -45,6 +45,6 @@ Should the new website facilitate content from projects like llnode and N-API? R
 
 ## Upcoming Meetings
 
-* **Node.js Foundation Calendar**: https://nodejs.org/calendar
+* **Node.js Foundation Calendar**: <https://nodejs.org/calendar>
 
 Click `+GoogleCalendar` at the bottom right to add to your own Google calendar
diff --git a/meetings/2018-12-06.md b/meetings/2018-12-06.md
@@ -52,6 +52,6 @@ No action items in website-redesign.
 
 ## Upcoming Meetings
 
-* **Node.js Foundation Calendar**: https://nodejs.org/calendar
+* **Node.js Foundation Calendar**: <https://nodejs.org/calendar>
 
 Click `+GoogleCalendar` at the bottom right to add to your own Google calendar.
diff --git a/meetings/2019-02-28.md b/meetings/2019-02-28.md
@@ -3,8 +3,8 @@
 ## Links
 
 * **Recording**:
-* **GitHub Issue**: https://github.com/nodejs/website-redesign/issues/146
-* **Minutes Google Doc**: https://docs.google.com/document/d/1JizrFXDqS7T3RzwuGELUBytBD3fBHn-Pzc2XuY5SrS8/edit
+* **GitHub Issue**: <https://github.com/nodejs/website-redesign/issues/146>
+* **Minutes Google Doc**: <https://docs.google.com/document/d/1JizrFXDqS7T3RzwuGELUBytBD3fBHn-Pzc2XuY5SrS8/edit>
 
 ## Present
 
@@ -61,6 +61,6 @@ TODO: Adam to move over content
 
 ## Upcoming Meetings
 
-* **Node.js Foundation Calendar**: https://nodejs.org/calendar
+* **Node.js Foundation Calendar**: <https://nodejs.org/calendar>
 
 Click `+GoogleCalendar` at the bottom right to add to your own Google calendar.
diff --git a/meetings/2019-03-14.md b/meetings/2019-03-14.md
@@ -3,8 +3,8 @@
 ## Links
 
 * **Recording**:
-* **GitHub Issue**: https://github.com/nodejs/website-redesign/issues/152
-* **Minutes Google Doc**: https://docs.google.com/document/d/1bYKtO1T5iB0q6P8yLYUtiHqxNgx-T0M6xnLu4mdoy7k/edit
+* **GitHub Issue**: <https://github.com/nodejs/website-redesign/issues/152>
+* **Minutes Google Doc**: <https://docs.google.com/document/d/1bYKtO1T5iB0q6P8yLYUtiHqxNgx-T0M6xnLu4mdoy7k/edit>
 
 ## Present
 
@@ -46,6 +46,6 @@ For now, we need more data on this issue so keeping it open for now.
 
 ## Upcoming Meetings
 
-* **Node.js Foundation Calendar**: https://nodejs.org/calendar
+* **Node.js Foundation Calendar**: <https://nodejs.org/calendar>
 
 Click `+GoogleCalendar` at the bottom right to add to your own Google calendar.
diff --git a/meetings/2019-03-28.md b/meetings/2019-03-28.md
@@ -3,8 +3,8 @@
 ## Links
 
 * **Recording**:
-* **GitHub Issue**: https://github.com/nodejs/website-redesign/issues/156
-* **Minutes Google Doc**: https://docs.google.com/document/d/1HeV7f_lg0h9YFfrtRj0QCiTCcFJZ77rvWuuaYnbj6Vg/edit
+* **GitHub Issue**: <https://github.com/nodejs/website-redesign/issues/156>
+* **Minutes Google Doc**: <https://docs.google.com/document/d/1HeV7f_lg0h9YFfrtRj0QCiTCcFJZ77rvWuuaYnbj6Vg/edit>
 
 ## Present
 
@@ -52,9 +52,9 @@ Awais: We can probably use the `.png` after GitHub user profile links to generat
 
 E.g.
 
-Profile: https://github.com/AhmadAwais
-Profile Image: https://github.com/AhmadAwais.png
-Profile Image Resize: https://github.com/AhmadAwais.png?size=90
+Profile: <https://github.com/AhmadAwais>
+Profile Image: <https://github.com/AhmadAwais.png>
+Profile Image Resize: <https://github.com/AhmadAwais.png?size=90>
 
 Tested the API calls via:
 
@@ -68,6 +68,6 @@ Doesn't seem to be rate limited by looking at the rate.remaining property.
 
 ## Upcoming Meetings
 
-* **Node.js Foundation Calendar**: https://nodejs.org/calendar
+* **Node.js Foundation Calendar**: <https://nodejs.org/calendar>
 
 Click `+GoogleCalendar` at the bottom right to add to your own Google calendar.
diff --git a/meetings/2019-04-25.md b/meetings/2019-04-25.md
diff --git a/meetings/2019-06-06.md b/meetings/2019-06-06.md
diff --git a/meetings/2020-01-30.md b/meetings/2020-01-30.md
