nodejs · Trott · Mar 29, 2020 · Mar 29, 2020 · Mar 29, 2020 · Mar 29, 2020
diff --git a/meetings/2018-03-01.md b/meetings/2018-03-01.md
@@ -31,10 +31,10 @@ Context: We left the last meeting with an action item to have wireframes for dis
 * Creating the user personas, who comes to conferences, who comes to website, to see what kind of humour would be acceptable. It could be very off-putting if the audience doesn't feel the same kind of humour as the company. Err on the side of being serious.
 * TODO: add humour to user personas issues.
 
-### Tech Exploration for In-Browser Node Playground [#12](https://github.com/nodejs/website-redesign/issues/12) (related to, but not the same as, [#9](https://github.com/nodejs/website-redesign/issues/9))
+### Tech Exploration for In-Browser Node.js Playground [#12](https://github.com/nodejs/website-redesign/issues/12) (related to, but not the same as, [#9](https://github.com/nodejs/website-redesign/issues/9))
 Context: Console/editor with which to test the capabilities of node.
 * It could be useful on the homepage and the learning page
-* Glitch has a heavy focus on the Nodejs community and bringing new people into Node
+* Glitch has a heavy focus on the Node.js community and bringing new people into Node.js
 * Runkit has a few options to dynamically create the embedded script
 * TODO: explore the suggested options to see which fits the needs
 * Runkit: you don't see package files which is arguably better for tutorials
@@ -44,7 +44,7 @@ Context: Console/editor with which to test the capabilities of node.
 * Past TODO: Investigate how frameworks and languages implement interactive Getting Started experiences
 * The purpose: onboard people on getting running from scratch. We should add more detailed getting started docs.
 * Suggest a learning path doc. A suggested path, where if completed someone will know how to use nodejs and start on more custom things.
-* Is there a way within Getting Started to tie into NodeSchool and other community initiatives? For this, the workshoppers need to be updated (some are Node 4). These would need an official maintainer to ensure they're up to date.
+* Is there a way within Getting Started to tie into NodeSchool and other community initiatives? For this, the workshoppers need to be updated (some are Node.js 4). These would need an official maintainer to ensure they're up to date.
 * TODO: open a new issue to explore connecting to NodeSchool on Getting Started
 
 ### Updating Node.js messaging [#242](https://github.com/nodejs/community-committee/issues/242) (in CommComm)

diff --git a/meetings/2018-03-15.md b/meetings/2018-03-15.md
@@ -14,12 +14,12 @@
 * Hot button issue needs input from the release team
 * Do we want the package manager included? We have traffic numbers for the package manager page. Bringing that and showing its popularity to the release team may further the cause.
 
-#### Getting started with node [#9](https://github.com/nodejs/website-redesign/issues/9)
+#### Getting started with Node.js [#9](https://github.com/nodejs/website-redesign/issues/9)
 * Some of this could actually go into Learn section
 * For the embedded runtime: What do we want?
   * We want people to be able to jump in and use it without having the install dependencies
-  * We want to build up from JS knowledge and take users into using Node
-* Do we want to also guide through Express or just explain Node core? The power of Node is the ecosystem and we should strike a balance. Take a look at how NodeSchool separates Core workshoppers from Electives.
+  * We want to build up from JS knowledge and take users into using Node.js
+* Do we want to also guide through Express or just explain Node.js core? The power of Node.js is the ecosystem and we should strike a balance. Take a look at how NodeSchool separates Core workshoppers from Electives.
 
 TODO Tierney: Organize another meeting between NodeSchool and the Website Redesign Initiative
 

diff --git a/meetings/2018-03-29.md b/meetings/2018-03-29.md
@@ -12,25 +12,25 @@
 ### Notes
 
 #### Coordinating "Getting Started" content with NodeSchool content [#18](https://github.com/nodejs/website-redesign/issues/18)
-* one person responded, but we may not get the engagement that we’re looking
+* one person responded, but we may not get the engagement that we're looking
 * suggest we need to re-prioritize this task
 * looking for a meeting to see if we can get the interactive tooling into our getting started
 * 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
-* reiterate having a dedicated meeting with open invitation. “We’re using what you have as a foundation. We’d like to have you involved.”
+* 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
 
 #### Website Wireframes [#15](https://github.com/nodejs/website-redesign/issues/15)
-* There’s been additional feedback from the TSC on the path we should go down for Downloads
+* There's been additional feedback from the TSC on the path we should go down for Downloads
 * keep pressing the issue of package manager
 * TODO: Tierney and Adam will work to meet with the TSC on this discussion
 * Feedback around the releases section in the downloads page:
-  * The full releases section probably isn’t useful as a source for downloads, since most downloads of older versions of Node.js are automated deployments and not direct downloads from the site
+  * The full releases section probably isn't useful as a source for downloads, since most downloads of older versions of Node.js are automated deployments and not direct downloads from the site
   * The metadata portion of it is interesting and useful, and worth having. Even having it in a truncated but expandable way for each release line would be helpful and a nice addition to the site.
 
-#### Tech Exploration for In-Browser Node Playground [#12](https://github.com/nodejs/website-redesign/issues/12)
+#### Tech Exploration for In-Browser Node.js Playground [#12](https://github.com/nodejs/website-redesign/issues/12)
 * bring back next meeting
 * Getting Started will inform what this look like
 * to be included in the meeting around Getting Started content and material

diff --git a/meetings/2018-04-12.md b/meetings/2018-04-12.md
@@ -19,7 +19,7 @@ Abraham Agiri Jnr. (@codeekage)
 
 * Coordinating "Getting Started" content with NodeSchool content [#18](https://github.com/nodejs/website-redesign/issues/18)
 * Website Wireframes [#15](https://github.com/nodejs/website-redesign/issues/15)
-* Tech Exploration for In-Browser Node Playground [#12](https://github.com/nodejs/website-redesign/issues/12)
+* Tech Exploration for In-Browser Node.js Playground [#12](https://github.com/nodejs/website-redesign/issues/12)
 
 ## Announcements
 
@@ -32,29 +32,29 @@ Welcome @codeekage to the team! Happy to have you!
 ### nodejs/website-redesign
 
 #### Coordinating "Getting Started" content with NodeSchool content [#18](https://github.com/nodejs/website-redesign/issues/18)
-* shouldn’t let getting started block us.
+* shouldn't let getting started block us.
 * We should start to transition to active content development and high-fidelity mockups – can happen in tandem.
 * Should move on the getting started breakout meeting
 
 #### Website Wireframes [#15](https://github.com/nodejs/website-redesign/issues/15)
 * Adam: Made updates to reflect feedback on download and releases flow. Will be live soon.
-* The homepage needs an iteration for content. For homepage, the content will inform the layout so we’ll need to do that first.
+* The homepage needs an iteration for content. For homepage, the content will inform the layout so we'll need to do that first.
 * Homepage will need a space for events that the Foundation can push to, and security notifications
-* We need tighter feedback loop (such as a dedicated channel in Node Slackers or Twitter DMs) between design iterations and users
+* We need tighter feedback loop (such as a dedicated channel in Node.js Slackers or Twitter DMs) between design iterations and users
 
-#### Tech Exploration for In-Browser Node Playground [#12](https://github.com/nodejs/website-redesign/issues/12)
+#### Tech Exploration for In-Browser Node.js Playground [#12](https://github.com/nodejs/website-redesign/issues/12)
 
 * See [RunKit demo](http://nodejs-org-runkit-demo.com/)
 * Idea from RunKit: Active Nightly Demos?
-* Docs run behind nightlies, dedicated “hot features” page?
-* Lock RunKit Node version down to docs version
+* Docs run behind nightlies, dedicated "hot features" page?
+* Lock RunKit Node.js version down to docs version
 
 ## Action Items
 
 * TODO: Manil to split out the current team members by interest in IA, Design, Code.
 * TODO: Adam to send out Dribble for breakout meeting.
 * TODO: Adam/Tierney to make a list of items we want on Getting Started.
-* TODO: Adam to create Node Slackers #website-redesign channel.
+* TODO: Adam to create Node.js Slackers #website-redesign channel.
 * TODO: Adam to submit a Node.js extended colour palette for review.
 
 ## Q&A, Other

diff --git a/meetings/2018-04-26.md b/meetings/2018-04-26.md
@@ -18,7 +18,7 @@
 * Potentially using an API service for website content [#31](https://github.com/nodejs/website-redesign/issues/31)
 * Coordinating "Getting Started" content with NodeSchool content [#18](https://github.com/nodejs/website-redesign/issues/18)
 * Website Wireframes [#15](https://github.com/nodejs/website-redesign/issues/15)
-* Tech Exploration for In-Browser Node Playground [#12](https://github.com/nodejs/website-redesign/issues/12)
+* Tech Exploration for In-Browser Node.js Playground [#12](https://github.com/nodejs/website-redesign/issues/12)
 * Identify topics to discuss for Collab Summit Spring 2018 [#29](https://github.com/nodejs/website-redesign/issues/29)
 
 ## Announcements
@@ -40,7 +40,7 @@ Dropped / punted for now.
 * Make this call available outside of GitHub
 * Make Call for Proposals ready to launch by date of the Collab Summit. Launch at Collab Summit
 
-#### Tech Exploration for In-Browser Node Playground [#12](https://github.com/nodejs/website-redesign/issues/12)
+#### 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/
 * 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.

diff --git a/meetings/2018-05-10.md b/meetings/2018-05-10.md
@@ -20,7 +20,7 @@
 ## Agenda
 
 * Website Wireframes [#15](https://github.com/nodejs/website-redesign/issues/15)
-* Tech Exploration for In-Browser Node Playground [#12](https://github.com/nodejs/website-redesign/issues/12)
+* Tech Exploration for In-Browser Node.js Playground [#12](https://github.com/nodejs/website-redesign/issues/12)
 * Extended Color Palette [#42](https://github.com/nodejs/website-redesign/issues/42)
 * Identify topics to discuss for Collab Summit Spring 2018 [#29](https://github.com/nodejs/website-redesign/issues/29)
 * Discuss Meeting Time
@@ -33,7 +33,7 @@
 
 * Website Wireframes [#15](https://github.com/nodejs/website-redesign/issues/15)
 Removed from agenda, since we've moved on to Design
-* Tech Exploration for In-Browser Node Playground
+* Tech Exploration for In-Browser Node.js Playground
 [#12](https://github.com/nodejs/website-redesign/issues/12)
 Removed from Agenda, since we've moved on to design
 * Extended Color Palette [#42](https://github.com/nodejs/website-redesign/issues/42)

diff --git a/meetings/2018-05-31.md b/meetings/2018-05-31.md
@@ -1,4 +1,4 @@
-# Node.js Foundation Website Redesign Strategic Initiative Meeting 2018-05-31 at the Node Collaborators Summit
+# Node.js Foundation Website Redesign Strategic Initiative Meeting 2018-05-31 at the Node.js Collaborators Summit
 
 ## Links
 
@@ -27,7 +27,7 @@
 ## Minutes
 
 **Adam**: This is a content-focused discussion on Getting Started Tutorials, and a
-high-level overview of progress. Then figure out user-personas (who’s coming to
+high-level overview of progress. Then figure out user-personas (who's coming to
 the site and why) and stakeholders and logical topics. Manil and I have been
 approaching this from a product-oriented flow. Process so far: Info gathering,
 then UX, and wireframes, then emerged voice and tone guidelines. Current phase:
@@ -54,7 +54,7 @@ tagline. It does not invite or draw in new users.
 
 **Adam**: Opening up to discussion. What did you all think about these exercises?
 
-**Addison**: The content on the website doesn’t explain what Node is well today.
+**Addison**: The content on the website doesn't explain what Node.js is well today.
 
 **Francisco**: Does anyone do a good job of this today?
 
@@ -65,26 +65,26 @@ tagline. It does not invite or draw in new users.
 **Seandon**: Maybe an `http` example? Or Express?
 
 **Thomas**: I know what Apache and Tomcat are, I expect people may get the wrong
-impression of what Node is.
+impression of what Node.js is.
 
-**Addison**: I was a PHP developer, I didn’t understand what the
-application/possibilities of Node was, but this is the selling point. The
+**Addison**: I was a PHP developer, I didn't understand what the
+application/possibilities of Node.js was, but this is the selling point. The
 problems of taking people down a prescribed path is you close some of the
 options. Imagine taking people through all these contexts and possibilities
 without making people walk far down a single possibilities.
 
 **Thomas**: Like a dating site, almost.
 
-**Francisco**: I don’t want the paralysis of choice—the first date if you will.
+**Francisco**: I don't want the paralysis of choice—the first date if you will.
 
 **Addison**: Yeah, like one quick tutorial, then all the choices.
 
 **Francisco**: And choose a particularly good and expressive example.
 
-**Seandon**: Event-based, non-blocking examples are where Node shines, so we
+**Seandon**: Event-based, non-blocking examples are where Node.js shines, so we
 should emphasize these.
 
-**Francisco**: And use the latest and greatest syntax: async/await. Things you’re
+**Francisco**: And use the latest and greatest syntax: async/await. Things you're
 not going to find elsewhere.
 
 **Greg**: And answer the question, why you should care. First that, then go to the
@@ -100,22 +100,22 @@ and create these stories.
 **Greg**: I can probably help with that. We ask in the annual survey if people
 would like to be contacted.
 
-**Adam**: I’d definitely appreciate the help. In that survey, how do these
+**Adam**: I'd definitely appreciate the help. In that survey, how do these
 categories map to users surveyed?
 
-**Greg**: We don’t ask all these categories, but three main ones.
+**Greg**: We don't ask all these categories, but three main ones.
 
-**Adam**: There’s also the legal questions too…
+**Adam**: There's also the legal questions too…
 
 **Greg**: Yeah, Linux Foundation can add to that.
 
 **Addison**: Definitely talk to Dan in the User Feedback group.
 
-**Adam**: (wrapping up) We’ll go through all these and come up with actual content
+**Adam**: (wrapping up) We'll go through all these and come up with actual content
 for these topics listed. Maybe it makes sense to make a pitch deck for
 stakeholders.
 
-**Greg**: Maybe we could use a CMS, for those who aren’t good with PRs.
+**Greg**: Maybe we could use a CMS, for those who aren't good with PRs.
 
-**Adam**: We have an open issue for thinking of using a CMS. So we’re definitely
+**Adam**: We have an open issue for thinking of using a CMS. So we're definitely
 looking into this! What option we choose will also depend on budget.
diff --git a/meetings/2018-09-13.md b/meetings/2018-09-13.md
@@ -60,7 +60,7 @@ Stub ticket to talk about design! We're going to show off iteration 1 designs to
 
 ### PR Review
 
-* Instruction for installation Node on Mac [#85](https://github.com/nodejs/website-redesign/pull/85)
+* Instruction for installation Node.js on Mac [#85](https://github.com/nodejs/website-redesign/pull/85)
 
 Tierney provided extra context to add. Manil will work with the author at their next meetup!