feat(posts): added many posts from node.js blog

Author: ovflowd

.eslintignore

@@ -1 +1,2 @@
 public
+content/blog

CODE_OF_CONDUCT.md

@@ -2,5 +2,4 @@
 
 The [Node.js Code of Conduct][] applies to this repo.
 
-[Node.js code of conduct]:
-  https://github.com/nodejs/node/blob/HEAD/CODE_OF_CONDUCT.md
+[Node.js code of conduct]: https://github.com/nodejs/node/blob/HEAD/CODE_OF_CONDUCT.md

CONTRIBUTING.md

@@ -3,6 +3,7 @@
 ## 🚀 Get Started
 
 * Fork the [nodejs.dev repo][] using the Fork button on the rop right
+
 * Clone your fork using SSH, GitHub CLI, or HTTPS
 
   ```bash
@@ -36,6 +37,7 @@
   ```
 
 * Commit your work. See [Commit Guidelines](#-commit-message-guidelines)
+
 * Push to your branch
 
   ```bash
@@ -63,6 +65,7 @@ Basic rules:
   > build, chore, ci, docs, feat, fix, perf, refactor, revert, style, test
 
 * Commit messages **must** start with a capital letter
+
 * Commit messages **must not** end with a period `.`
 
 ## 📜 Pull Request Policy
@@ -104,15 +107,15 @@ The production Storybook can be viewed at <https://nodejs.dev/storybook>
 
 For failing formatting or linting, you can try running:
 
-  ```bash
-  npm run format
-  ```
+```bash
+npm run format
+```
 
 Tests sometimes fail when adding or updating HTML. To update snapshots you can run:
 
- ```bash
- npm run update-snapshot
- ```
+```bash
+npm run update-snapshot
+```
 
 ## Developer's Certificate of Origin 1.1
 

ModerationPolicy.md

@@ -2,5 +2,4 @@
 
 The [Node.js Moderation Policy][] applies to this repo.
 
-[Node.js moderation policy]:
-  https://github.com/nodejs/admin/blob/main/Moderation-Policy.md
+[Node.js moderation policy]: https://github.com/nodejs/admin/blob/main/Moderation-Policy.md

README.md

@@ -28,13 +28,13 @@
    npm install
    ```
 
-1. **Start project locally.**
+2. **Start project locally.**
 
    ```bash
    npm start
    ```
 
-1. **Open the source code and start editing!**
+3. **Open the source code and start editing!**
 
 ## 🙌 Contributing
 

WRITING_A_BLOG_POST.md

@@ -5,7 +5,7 @@ In order to publish a new blog post, make sure that you added yourself into `src
 The current schema supports the following fields:
 
 | Field   | Description                                                                                          | Required |
-|---------|------------------------------------------------------------------------------------------------------|----------|
+| ------- | ---------------------------------------------------------------------------------------------------- | -------- |
 | id      | Your unique id. In preference it should be your GitHub Username as we resolve the images from there. | Yes      |
 | name    | Your display name. It could be your full name.                                                       | Yes      |
 | website | A link to open when someone wants to get to know more about you                                      | No       |

content/about/about.md

@@ -36,7 +36,7 @@ Node.js directly performs I/O, so the process never blocks. Because nothing bloc
 If some of this language is unfamiliar, there is a full article on
 [Blocking vs. Non-Blocking][].
 
----
+***
 
 Node.js is similar in design to, and influenced by, systems like Ruby's
 [Event Machine][] and Python's [Twisted][]. Node.js takes the event model a bit

content/about/governance.md

@@ -4,6 +4,7 @@ description: 'Project Governance | Node.js'
 authors: XhmikosR, fhemberger, thefourtheye, ryanmurakami, refack
 category: governance
 ---
+
 ## Consensus Seeking Process
 
 The Node.js project follows a [Consensus Seeking][] decision making model.

content/about/privacy.md

@@ -8,11 +8,15 @@ category: about
 ## Logo Downloads
 
 <!--lint disable nodejs-links-->
+
 Please review the [trademark policy](/trademark) for information about permissible use of Node.js® logos and marks.
+
 <!--lint enable nodejs-links-->
 
 <!--lint disable nodejs-links-->
+
 Guidelines for the visual display of the Node.js mark are described in the [Visual Guidelines](/static/documents/foundation-visual-guidelines.pdf).
+
 <!--lint enable nodejs-links-->
 
 <table class="resources-logos">

content/about/resources.md

@@ -29,5 +29,7 @@ If you have any questions don't hesitate to
 [email us](mailto:[email protected]).
 
 <!--lint disable nodejs-links-->
+
 Guidelines for the visual display of the Node.js mark are described in the [Visual Guidelines](/static/documents/foundation-visual-guidelines.pdf).
+
 <!--lint enable nodejs-links-->

content/about/trademark.md

@@ -0,0 +1,106 @@
+---
+title: Advisory Board Update
+blogAuthors: ['tjfontaine']
+category: advisory-board
+---
+
+A lot has been happening in Node.js, so I wanted to bring everyone up to date on
+where we are with regards to the advisory board, its working groups, and the
+release of v0.12.
+
+The interim [advisory
+board](https://www.joyent.com/blog/node-js-advisory-board) has met three times
+since its creation. You can find the minutes from the advisory board meetings
+here: <https://nodejs.org/en/about/advisory-board/>. As
+we have more meetings and minutes, we will announce the dates and times for
+those meeting and their minutes here on the blog. The next meeting is this
+Thursday December 4th, at 1:30PM PST. We're looking to collect as much feedback
+and input from as many representatives of the community as we can, so it's
+important that we keep everyone up to date as much as possible.
+
+The interim advisory board has been working through a series of topics (in
+general meetings as well as working groups) to further hone the scope of the
+board, as well as define the structure that the advisory board will use to
+conduct its meetings. Everyone on the board wants to make sure we're being as
+transparent as possible, so let me describe how things operate so far. The
+board is using a traditional two conference call structure, a public portion
+that is recorded and open for anyone to join, and a private portion that is
+only for board members.
+
+The public portion is meant to provide an update of what happened in the
+previous meeting, as well as the status of action items from the previous
+meeting. At the end of each public session is a open comment section, where
+listeners are able to ask questions and the advisory board can respond.
+
+Following the public portion the board dials into the private conference,
+further discussion happens during this time around specific agenda items,
+working groups providing updates, and facilitating conversations about those
+topics. These conversations are open and frank, and their content is recorded
+in the minutes. Those minutes are then published a few days after the meeting
+in the GitHub repository
+<https://github.com/joyent/nodejs-advisory-board>,
+as well as on the website
+<https://nodejs.org/en/about/advisory-board/>.
+
+There are a few working groups so far, for instance one is focused on making
+sure the membership of the board is representative of the community Node.js
+serves. While the board was initially bootstrapped with its existing
+membership, we want to quickly move to a model that fully represents our
+community. We want the board to represent the broadest spectrum of our
+community, that also enables the board to move swiftly and make progress.
+
+Another working group is having a conversation about governance. This includes
+topics like what is the team that makes decisions for Node.js, how do you
+become a member of that team, how does that team set the roadmap for the
+project, and how does that team makes decisions.
+
+One thing that we all agree on, is that we're not going to be using the
+Benevolent Dictator model. In fact, recently the project hasn't been operating
+that way. We can be more clear about that in our
+[documentation](https://nodejs.org/en/about/organization). We all agree we want
+a healthy and vibrant team, a team focused on making progress for Node.js, not
+for progress's sake, but for the betterment of the software project and the
+community we serve. We also agree that this means that there should be
+consensus among the team. The conversation has been fruitful, and is on going,
+we're continuing to work through the finer points of how much consensus we
+need.
+
+I want to take a moment to describe what consensus means in this context. The
+consensus model is about accountability. Accountability for the changes being
+integrated into the project, accountability for documentation, and
+accountability for releases. While members of the team are responsible for
+subsystems or features of Node.js, everyone reviews each others changes. They
+make sure to understand the impact on their relevant responsibilities.
+
+The goal of the team, especially that of the project lead, is to drive
+consensus and ensure accountability. This means asking critical questions and
+being able to answer them specifically and succinctly, for example:
+
+* What are we trying to solve with this change?
+* Does this change effectively solve for this problem?
+* Does this API have a consumer?
+* Does this API reach the broadest amount of use cases?
+* Is this API supportable?
+* Does this change have adverse effects on other subsystems or use cases (and is that acceptable)?
+* Does this change have tests that verify its operation, now and in the future?
+* Does this change pass our style guidelines?
+* Does this change pass our integration tests for the matrix of our supported configurations?
+  * For instance: ia32 and x64 for Windows, Linux, OSX, SmartOS
+
+These are just some of the questions, and while the questions are not unusual
+or unique to Node.js, they are still important.
+
+Finally, we are very close to releasing v0.12, there's only one major patch
+we're waiting to land. Once that's done we'll be releasing v0.11.15 as a
+release candidate. Assuming no severe issues are filed against v0.11.15 we will
+be going live with v0.12 about two weeks after the v0.11.15 release.
+
+If you have questions for the advisory board you can email
+<[email protected]> or file an issue on
+its repository
+<https://github.com/joyent/nodejs-advisory-board>.
+Thanks for all of your continued contributions to Node.js, in the form of
+[filing issues](https://github.com/joyent/node/issues), [submitting pull
+requests](https://github.com/joyent/node/pulls), and publishing your modules.
+Node.js is lucky to have such an enthusiastic and engaged community, and we're
+excited to be working with you on the future of Node.js.

content/blog/advisory-board/2014-12-03-advisory-board-update.md

@@ -0,0 +1,20 @@
+---
+title: Listening to the Community
+blogAuthors: ['advisory-board']
+category: advisory-board
+---
+
+We assembled the Node.js Advisory Board (AB) to listen to the community and
+make the necessary changes to have a unified direction for Node.js, a
+passionate group of developers, a vibrant ecosystem of product and service
+providers, and a satisfied user base. Over the last month we have made great
+progress on an open governance model, API standards, IP management, and
+transparency to ensure the project is community-driven. These efforts
+explicitly target helping resolve conflicts and with the goal of moving the
+community forward together. It is important that we understand voices of
+dissent and frustration and work together to build the greater ecosystem. We
+are committed to this goal.
+
+Node.js remains the trusted platform that users rely on for creative projects
+and to drive business goals. The v0.12 release will ship shortly and the
+project team is already engaged in discussions about the next release.

content/blog/advisory-board/2014-12-05-listening-to-the-community.md

@@ -0,0 +1,35 @@
+---
+title: Node.js Foundation Elects Board of Directors
+blogAuthors: ['node-js-website']
+category: 'announcements'
+---
+
+> New Foundation Committed to Accelerating Growth of the Node.js Platform Also Adds Marketing Chair and Community Manager
+
+SAN FRANCISCO, Sept. 4, 2015 – The [Node.js Foundation](https://foundation.nodejs.org/), a community-led and industry-backed consortium to advance the development of the Node.js platform, today announced key executives have been elected to its Board of Directors. The Board of Directors represents the broad Node.js community and will guide the Foundation as it executes on its mission to enable widespread adoption and help accelerate development of Node.js and other related modules.
+
+The Node.js Foundation board, which sets the business and technical direction as well as oversees IP management, marketing, and events on behalf of the organization, includes:
+
+* [Danese Cooper](https://www.linkedin.com/in/danesecooper), chairman of the board, distinguished member of technical staff - open source at PayPal;
+* [Scott Hammond](https://www.linkedin.com/pub/scott-hammond/1/a4b/92a), vice-chairman of the board, chief executive officer at Joyent;
+* [Brian McCallister](https://www.linkedin.com/in/brianmccallister), silver-level director of the board, chief technology officer of platforms at Groupon;
+* [Todd Moore](https://www.linkedin.com/pub/todd-moore/2b/540/798), board member, vice president of open technology at IBM;
+* [Steve Newcomb](https://www.linkedin.com/in/stevenewcomb), board member, founder and chief executive officer at Famous Industries;
+* [Gianugo Rabellino](https://www.linkedin.com/in/gianugo), secretary of the board, senior director of open source programs at Microsoft;
+* [Charlie Robbins](https://www.linkedin.com/in/charlierobbins), gold-level director of the board, director of engineering at GoDaddy.com;
+* [Imad Sousou](https://www.linkedin.com/pub/imad-sousou/6/b49/2b8), board member, vice president and general manager at Intel;
+* [Rod Vagg](https://www.linkedin.com/in/rvagg), technical steering committee chairperson, chief node officer at NodeSource.
+
+In addition to formalizing the board, [Bill Fine](https://www.linkedin.com/pub/bill-fine/2/497/916), vice president of product and marketing at Joyent, was elected as the marketing chairperson. The Linux Foundation also hired [Mikeal Rogers](https://www.linkedin.com/in/mikealrogers) as its community manager to help support and guide the new organization.
+
+“The new board members represent the diversity of the Node.js community and the commitment that these companies have to supporting its overall efforts,” said Danese Cooper, chairman of the board, Node.js Foundation. “Node.js is incredibly important to the developer ecosystem and is increasingly relevant for building applications on devices that are changing the pace of commerce. The board will work to support and build the Node.js platform using the blueprint of an open governance model that is transparent and supportive of its community.”
+
+In early June, the Node.js and io.js developer community announced that they were merging their respective code base to continue their work in a neutral forum, the Node.js Foundation. The new leaders will help support the ongoing growth and evolution of the combined communities and will foster a collaborative environment to accelerate growth and the platform’s evolution.
+
+### About Node.js Foundation
+
+Node.js Foundation is a collaborative open source project dedicated to building and supporting the Node.js platform and other related modules. Node.js is used by tens of thousands of organizations in more than 200 countries and amasses more than 2 million downloads per month. It is the runtime of choice for high-performance, low latency applications, powering everything from enterprise applications, robots, API engines, cloud stacks and mobile websites.
+
+The Foundation is made up of a diverse group of companies including Platinum members Famous, IBM, Intel, Joyent, Microsoft and PayPal. Gold members include GoDaddy, NodeSource and Modulus/Progress Software, and Silver members include Apigee, Codefresh, DigitalOcean, Fidelity, Groupon, nearForm, npm, Sauce Labs, SAP, StrongLoop and YLD!. Get involved here: <https://nodejs.org/>.
+
+The Node.js Foundation is a Collaborative Project at The Linux Foundation. Linux Foundation Collaborative Projects are independently funded software projects that harness the power of collaborative development to fuel innovation across industries and ecosystems. [www.linuxfoundation.org](http://www.linuxfoundation.org)

content/blog/announcements/2015-09-04-foundation-elects-board.md

@@ -0,0 +1,24 @@
+---
+title: Node.js Interactive
+blogAuthors: ['node-js-website']
+category: 'announcements'
+---
+
+Are You Ready for Node.js Interactive?
+
+The Node.js Foundation is pleased to announce [Node.js Interactive](http://interactive.nodejs.org) happening from December 8-9, 2015 in Portland, OR. With Node.js growing in all aspects of technology, the gathering will cover everything from streamlining development of fast websites and real-time applications to tips for managing Node.js applications, and much more.
+
+The event will be the first of its kind under the Node.js Foundation led in cooperation with The Linux Foundation. Vendor-neutral by design, it will focus on the continued ideals of open governance collaboration between the now joined Node.js and io.js community. The conference welcomes experienced developers as well as those interested in how Node.js might be of use to their business with tracks that focus on IoT, front-end and back-end technologies. To curate these tracks and create the best experience for attendees, track chairs include seasoned veterans:
+
+* [Kassandra Perch](https://github.com/nodebotanist) for IoT, a software developer / evangelist / advocate / educator / roboticist living in Austin, TX, who you can follow at: [@nodebotanist](https://twitter.com/nodebotanist).
+* [Jessica Lord](https://github.com/jlord/) for Front-End, a GitHub developer and designer who loves open source, JavaScript & Node.js, and stories of Tudor England and is a Portland transplant.
+* [C J Silverio](https://github.com/ceejbot) for Back-End, who is all node, all the time and works as VP of engineering at npm, Inc. in the Bay area.
+
+As the Node.js community continues to grow, the Node.js Foundation believes this event is the perfect place to continue to develop collaboration and better understand what’s next for this extremely popular technology. Interested in joining us? Register [here](http://events.linuxfoundation.org/events/node-interactive/attend/register). Timeline for discount rates are as follows:
+
+* Super Early Bird - US$200 for the 1st 100 tickets
+* Early Bird - US$325, ends October 17
+* Standard - US$425, ends November 21
+* Late & Onsite - US$525, begins November 22
+
+If you are interested in becoming a speaker, please check out our [Call For Participation](http://events.linuxfoundation.org/events/node-interactive/program/cfp) page for more details. Call for Participation closes on September 24, 2015.