diff --git a/layouts/partials/primary-download-matrix.hbs b/layouts/partials/primary-download-matrix.hbs index 0731393b7cea2..f80e0bf18725f 100644 --- a/layouts/partials/primary-download-matrix.hbs +++ b/layouts/partials/primary-download-matrix.hbs @@ -10,7 +10,7 @@
  • - +
    {{downloads.current}}
    {{downloads.tagline-current}}
     diff --git a/locale/ar/about/governance.md b/locale/ar/about/governance.md index 6a23cffa32f2d..dfd7da9f012a0 100644 --- a/locale/ar/about/governance.md +++ b/locale/ar/about/governance.md @@ -24,7 +24,7 @@ layout: about.hbs [COLLABORATOR_GUIDE.md]: https://github.com/nodejs/node/blob/master/COLLABORATOR_GUIDE.md [لجنة المجتمع (CommComm)]: https://github.com/nodejs/community-committee/blob/master/Community-Committee-Charter.md -[منهج الإجماع في إتخاذ القرارات]: http://en.wikipedia.org/wiki/Consensus-seeking_decision-making +[منهج الإجماع في إتخاذ القرارات]: https://en.wikipedia.org/wiki/Consensus-seeking_decision-making [README.md]: https://github.com/nodejs/node/blob/master/README.md#current-project-team-members [لجنة التوجيه التقني (TSC)]: https://github.com/nodejs/TSC/blob/master/TSC-Charter.md [لجنة التوجيه التقني]: https://github.com/nodejs/TSC diff --git a/locale/ar/get-involved/index.md b/locale/ar/get-involved/index.md index ea3abeeb9e119..7644252be29bb 100644 --- a/locale/ar/get-involved/index.md +++ b/locale/ar/get-involved/index.md @@ -7,7 +7,7 @@ layout: contribute.hbs ## نقاش المجتمع - تعتبر [قائمة المشكلات على GitHub](https://github.com/nodejs/node/issues) المكان المخصص للنقاشات حول المميزات الأساسية للـ Node.js. -- لأجل الانخراط في دردشة آنية عن تطوير الـ Node.js، تفضل بزيارة `irc.freenode.net` على قناة `#node.js` باستعمال [أحد برامج IRC](http://en.wikipedia.org/wiki/Comparison_of_Internet_Relay_Chat_clients) أو اتصل بواسطة متصفحك باستعمال خدمة الشات الخاصة بـ [freenode](http://webchat.freenode.net/?channels=node.js) +- لأجل الانخراط في دردشة آنية عن تطوير الـ Node.js، تفضل بزيارة `irc.freenode.net` على قناة `#node.js` باستعمال [أحد برامج IRC](https://en.wikipedia.org/wiki/Comparison_of_Internet_Relay_Chat_clients) أو اتصل بواسطة متصفحك باستعمال خدمة الشات الخاصة بـ [freenode](https://webchat.freenode.net/#node.js) - الحساب الرسمي للـ Node.js على تويتر هو [nodejs](https://twitter.com/nodejs) - [رزنامة مؤسسة الـ Node.js](https://nodejs.org/calendar) تحتوي على تواريخ لقاءات جميع الفرق العامة. - [Node.js Everywhere](https://newsletter.nodejs.org) و تمثل الرسالة الإخبارية الشهرية للـ Node.js. @@ -16,7 +16,7 @@ layout: contribute.hbs ## التعلم -- [التوثيق الرسمي لواجهة برمجة التطبيق](/api) يتحدث بالتفصيل على وجاهة برمجة التطبيق الخاصة بالـ Node.js +- [التوثيق الرسمي لواجهة برمجة التطبيق](/api/) يتحدث بالتفصيل على وجاهة برمجة التطبيق الخاصة بالـ Node.js - [دلائل الـ Node.js](https://nodejs.dev) يرشدك إلى أساسيات تطوير تطبيقات باستعمال الـ Node.js. - [NodeSchool.io](http://nodeschool.io) سيعلمك مفاهيم الـ Node.js باستعمال العاب سطر اوامر تفاعلية. - [التاق الخاص بالـ Node.js على Stack Overflow](http://stackoverflow.com/questions/tagged/node.js) يجمع معلومات جديدة كل يوم. diff --git a/locale/ar/security.md b/locale/ar/security.md index ae5ae4190fb2c..c26de38fa9c43 100644 --- a/locale/ar/security.md +++ b/locale/ar/security.md @@ -46,8 +46,8 @@ title: الأمن يتم توزيع الإشعارات الأمنية بإتباع الطرق التالية. -- [https://groups.google.com/group/nodejs-sec](https://groups.google.com/group/nodejs-sec) -- [https://nodejs.org/en/blog](https://nodejs.org/en/blog) +- +- ## تعليقات على هذه السياسة diff --git a/locale/ar/site.json b/locale/ar/site.json index 8b5d028ae68e3..1739e9e780faf 100644 --- a/locale/ar/site.json +++ b/locale/ar/site.json @@ -93,12 +93,12 @@ "text": "ES6 وما بعدها" }, "api-lts": { - "link": "/dist/latest-%ver-major%/docs/api", + "link": "/dist/latest-%ver-major%/docs/api/", "subtext": "LTS", "text": "%ver% API" }, "api-current": { - "link": "/dist/latest-%ver-major%/docs/api", + "link": "/dist/latest-%ver-major%/docs/api/", "text": "%ver% API" }, "guides": { diff --git a/locale/ca/get-involved/index.md b/locale/ca/get-involved/index.md index 7715a4ec29124..3cfbeb81c8330 100644 --- a/locale/ca/get-involved/index.md +++ b/locale/ca/get-involved/index.md @@ -8,7 +8,7 @@ layout: contribute.hbs ## Discussió de la comunitat - La [llista d'incidències de Github](https://github.com/nodejs/node/issues) és el lloc per discutir les característiques del nucli de Node.js. -- Per xatejar en temps real sobre el desenvolupament de Node.js vagi a `irc.freenode.net` al canal `#node.js` fent servir un [client d'IRC](http://es.wikipedia.org/wiki/Anexo:Clientes_IRC) o connecti's amb el seu navegador al canal usant [WebChat de freenode](http://webchat.freenode.net/?channels=node.js). +- Per xatejar en temps real sobre el desenvolupament de Node.js vagi a `irc.freenode.net` al canal `#node.js` fent servir un [client d'IRC](https://es.wikipedia.org/wiki/Anexo:Clientes_IRC) o connecti's amb el seu navegador al canal usant [WebChat de freenode](https://webchat.freenode.net/#node.js). - El compte de Twitter oficial de Node.js és [nodejs](https://twitter.com/nodejs). - The [Node.js Foundation calendar](https://nodejs.org/calendar) with all public team meetings. - [Node.js Everywhere](https://newsletter.nodejs.org) és el Butlletí oficial mensual de Node.js. @@ -17,7 +17,7 @@ layout: contribute.hbs ## Aprenentatge -- La [Documentació oficial de l'API](/api) detalla l'API de Node. +- La [Documentació oficial de l'API](/api/) detalla l'API de Node. - [NodeSchool.io](http://nodeschool.io) li ensenyarà conceptes de Node.js de forma interactiva mitjançant jocs utilitzant la línia de comandes. - L'[etiqueta de Node.js en Stack Overflow](http://stackoverflow.com/questions/tagged/node.js) col·lecciona nova informació cada dia. - L'[etiqueta de Node.js en la DEV Community](https://dev.to/t/node) és un lloc on compartir projectes de Node.js, articles i tutorials, així com iniciar debats i demanar realimentació sobre temes relacionats amb Node.js. Els desenvolupadors de tots els nivells d'experiència són benvinguts a participar. diff --git a/locale/ca/security.md b/locale/ca/security.md index 8214aee36c77f..179ee4716f8e3 100644 --- a/locale/ca/security.md +++ b/locale/ca/security.md @@ -46,8 +46,8 @@ Es farà tot el possible per gestionar l'error en la forma més oportuna possibl Les notificacions de seguretat seran distribuïdes usant els següents mitjans. -- [https://groups.google.com/group/nodejs-sec](https://groups.google.com/group/nodejs-sec) -- [https://nodejs.org/en/blog](https://nodejs.org/en/blog) +- +- ## Comentaris sobre aquesta política diff --git a/locale/ca/site.json b/locale/ca/site.json index ef3d5be4a1740..e41e6cce9ccb0 100644 --- a/locale/ca/site.json +++ b/locale/ca/site.json @@ -93,12 +93,12 @@ "text": "ES6 i més enllà" }, "api-lts": { - "link": "/dist/latest-%ver-major%/docs/api", + "link": "/dist/latest-%ver-major%/docs/api/", "subtext": "LTS", "text": "%ver% API" }, "api-current": { - "link": "/dist/latest-%ver-major%/docs/api", + "link": "/dist/latest-%ver-major%/docs/api/", "text": "%ver% API" }, "guides": { diff --git a/locale/de/site.json b/locale/de/site.json index 8cf87078c99dc..7770e2ab0b36d 100644 --- a/locale/de/site.json +++ b/locale/de/site.json @@ -83,12 +83,12 @@ "text": "ES6 und darüber hinaus" }, "api-lts": { - "link": "/dist/latest-%ver-major%/docs/api", + "link": "/dist/latest-%ver-major%/docs/api/", "subtext": "LTS", "text": "%ver% API" }, "api-current": { - "link": "/dist/latest-%ver-major%/docs/api", + "link": "/dist/latest-%ver-major%/docs/api/", "text": "%ver% API" }, "guides": { diff --git a/locale/en/about/governance.md b/locale/en/about/governance.md index 035f6e3ce3370..24581f3780a94 100644 --- a/locale/en/about/governance.md +++ b/locale/en/about/governance.md @@ -30,7 +30,7 @@ extending the Node.js community. [COLLABORATOR_GUIDE.md]: https://github.com/nodejs/node/blob/master/COLLABORATOR_GUIDE.md [Community Committee (CommComm)]: https://github.com/nodejs/community-committee/blob/master/Community-Committee-Charter.md -[Consensus Seeking]: http://en.wikipedia.org/wiki/Consensus-seeking_decision-making +[Consensus Seeking]: https://en.wikipedia.org/wiki/Consensus-seeking_decision-making [README.md]: https://github.com/nodejs/node/blob/master/README.md#current-project-team-members [Technical Steering Committee (TSC)]: https://github.com/nodejs/TSC/blob/master/TSC-Charter.md [TSC]: https://github.com/nodejs/TSC diff --git a/locale/en/blog/release/v0.4.3.md b/locale/en/blog/release/v0.4.3.md index 4cf257c2fe436..d9400e289eaa6 100644 --- a/locale/en/blog/release/v0.4.3.md +++ b/locale/en/blog/release/v0.4.3.md @@ -29,7 +29,7 @@ Download: https://nodejs.org/dist/node-v0.4.3.tar.gz Website: https://nodejs.org/docs/v0.4.3/ -Documentation: https://nodejs.org/docs/v0.4.3/api +Documentation: https://nodejs.org/docs/v0.4.3/api/ Announcement diff --git a/locale/en/blog/release/v0.4.4.md b/locale/en/blog/release/v0.4.4.md index 40158a0755e17..bcaf32627aa16 100644 --- a/locale/en/blog/release/v0.4.4.md +++ b/locale/en/blog/release/v0.4.4.md @@ -25,6 +25,6 @@ Download: https://nodejs.or Website: https://nodejs.org/docs/v0.4.4 -Documentation: https://nodejs.org/docs/v0.4.4/api +Documentation: https://nodejs.org/docs/v0.4.4/api/ announcement diff --git a/locale/en/blog/release/v0.4.5.md b/locale/en/blog/release/v0.4.5.md index ede6a2c4ca1f5..13c0e77652df5 100644 --- a/locale/en/blog/release/v0.4.5.md +++ b/locale/en/blog/release/v0.4.5.md @@ -26,7 +26,7 @@ Download: https://nodejs.or Website: https://nodejs.org/docs/v0.4.5 -Documentation: https://nodejs.org/docs/v0.4.5/api +Documentation: https://nodejs.org/docs/v0.4.5/api/ announcement diff --git a/locale/en/blog/release/v0.4.7.md b/locale/en/blog/release/v0.4.7.md index df71c2e5208f9..ee590019d6d68 100644 --- a/locale/en/blog/release/v0.4.7.md +++ b/locale/en/blog/release/v0.4.7.md @@ -23,4 +23,4 @@ Download: https://nodejs.or Website: https://nodejs.org/docs/v0.4.7/ -Documentation: https://nodejs.org/docs/v0.4.7/api +Documentation: https://nodejs.org/docs/v0.4.7/api/ diff --git a/locale/en/blog/release/v0.4.9.md b/locale/en/blog/release/v0.4.9.md index 124bcd145b13e..dc05e463e4126 100644 --- a/locale/en/blog/release/v0.4.9.md +++ b/locale/en/blog/release/v0.4.9.md @@ -30,4 +30,4 @@ Download: https://nodejs.or Website: https://nodejs.org/docs/v0.4.9 -Documentation: https://nodejs.org/docs/v0.4.9/api +Documentation: https://nodejs.org/docs/v0.4.9/api/ diff --git a/locale/en/blog/release/v0.5.2.md b/locale/en/blog/release/v0.5.2.md index 9e2191ddcad1d..ddbd163084b33 100644 --- a/locale/en/blog/release/v0.5.2.md +++ b/locale/en/blog/release/v0.5.2.md @@ -27,4 +27,4 @@ Windows Executable: https://no Website: https://nodejs.org/dist/v0.5.2/docs/ -Documentation: https://nodejs.org/dist/v0.5.2/docs/api +Documentation: https://nodejs.org/dist/v0.5.2/docs/api/ diff --git a/locale/en/blog/release/v0.5.3.md b/locale/en/blog/release/v0.5.3.md index dcb7261242b64..2d424e913d64e 100644 --- a/locale/en/blog/release/v0.5.3.md +++ b/locale/en/blog/release/v0.5.3.md @@ -37,4 +37,4 @@ Windows Executable: https://no Website: https://nodejs.org/dist/v0.5.3/docs -Documentation: https://nodejs.org/dist/v0.5.3/docs/api +Documentation: https://nodejs.org/dist/v0.5.3/docs/api/ diff --git a/locale/en/blog/release/v0.5.4.md b/locale/en/blog/release/v0.5.4.md index 4408d0127ea89..176fe88a90a8f 100644 --- a/locale/en/blog/release/v0.5.4.md +++ b/locale/en/blog/release/v0.5.4.md @@ -28,4 +28,4 @@ Windows Executable: https://no Website: https://nodejs.org/dist/v0.5.4/docs -Documentation: https://nodejs.org/dist/v0.5.4/docs/api +Documentation: https://nodejs.org/dist/v0.5.4/docs/api/ diff --git a/locale/en/blog/uncategorized/ldapjs-a-reprise-of-ldap.md b/locale/en/blog/uncategorized/ldapjs-a-reprise-of-ldap.md index 1ecf19a7237e9..20354b09e2bfd 100644 --- a/locale/en/blog/uncategorized/ldapjs-a-reprise-of-ldap.md +++ b/locale/en/blog/uncategorized/ldapjs-a-reprise-of-ldap.md @@ -11,14 +11,14 @@ layout: blog-post.hbs This post has been about 10 years in the making. My first job out of college was at IBM working on the Tivoli Directory Server, and at the time I had a preconceived notion that working on anything related to Internet RFCs was about as hot as you could get. I spent a lot of time back then getting "down and dirty" with everything about LDAP: the protocol, performance, storage engines, indexing and querying, caching, customer use cases and patterns, general network server patterns, etc. Basically, I soaked up as much as I possibly could while I was there. On top of that, I listened to all the "gray beards" tell me about the history of LDAP, which was a bizarre marriage of telecommunications conglomerates and graduate students. The point of this blog post is to give you a crash course in LDAP, and explain what makes ldapjs different. Allow me to be the gray beard for a bit...

    What is LDAP and where did it come from?

    -Directory services were largely pioneered by the telecommunications companies (e.g., AT&T) to allow fast information retrieval of all the crap you'd expect would be in a telephone book and directory. That is, given a name, or an address, or an area code, or a number, or a foo support looking up customer records, billing information, routing information, etc. The efforts of several telcos came to exist in the X.500 standard(s). An X.500 directory is one of the most complicated beasts you can possibly imagine, but on a high note, there's -probably not a thing you can imagine in a directory service that wasn't thought of in there. It is literally the kitchen sink. Oh, and it doesn't run over IP (it's actually on the OSI model). +Directory services were largely pioneered by the telecommunications companies (e.g., AT&T) to allow fast information retrieval of all the crap you'd expect would be in a telephone book and directory. That is, given a name, or an address, or an area code, or a number, or a foo support looking up customer records, billing information, routing information, etc. The efforts of several telcos came to exist in the X.500 standard(s). An X.500 directory is one of the most complicated beasts you can possibly imagine, but on a high note, there's +probably not a thing you can imagine in a directory service that wasn't thought of in there. It is literally the kitchen sink. Oh, and it doesn't run over IP (it's actually on the OSI model). -Several years after X.500 had been deployed (at telcos, academic institutions, etc.), it became clear that the Internet was "for real." LDAP, the "Lightweight Directory Access Protocol," was invented to act purely as an IP-accessible gateway to an X.500 directory. +Several years after X.500 had been deployed (at telcos, academic institutions, etc.), it became clear that the Internet was "for real." LDAP, the "Lightweight Directory Access Protocol," was invented to act purely as an IP-accessible gateway to an X.500 directory. -At some point in the early 90's, a graduate student at the University of Michigan (with some help) cooked up the "grandfather" implementation of the LDAP protocol, which wasn't actually a "gateway," but rather a stand-alone implementation of LDAP. Said implementation, like many things at the time, was a process-per-connection concurrency model, and had "backends" (aka storage engine) for the file system and the Unix DB API. At some point the Berkeley Database (BDB) was put in, and still remains the de facto storage engine for most LDAP directories. +At some point in the early 90's, a graduate student at the University of Michigan (with some help) cooked up the "grandfather" implementation of the LDAP protocol, which wasn't actually a "gateway," but rather a stand-alone implementation of LDAP. Said implementation, like many things at the time, was a process-per-connection concurrency model, and had "backends" (aka storage engine) for the file system and the Unix DB API. At some point the Berkeley Database (BDB) was put in, and still remains the de facto storage engine for most LDAP directories. -Ok, so some a graduate student at UM wrote an LDAP server that wasn't a gateway. So what? Well, that UM code base turns out to be the thing that pretty much every vendor did a source license for. Those graduate students went off to Netscape later in the 90's, and largely dominated the market of LDAP middleware until Active Directory came along many years later (as far as I know, Active Directory is "from scratch", since while it's "almost" LDAP, it's different in a lot of ways). That Netscape code base was further bought and sold over the years to iPlanet, Sun Microsystems, and Red Hat (I'm probably missing somebody in that chain). It now lives in the Fedora umbrella as '389 Directory Server.' Probably the most popular fork of that code base now is OpenLDAP. +Ok, so some a graduate student at UM wrote an LDAP server that wasn't a gateway. So what? Well, that UM code base turns out to be the thing that pretty much every vendor did a source license for. Those graduate students went off to Netscape later in the 90's, and largely dominated the market of LDAP middleware until Active Directory came along many years later (as far as I know, Active Directory is "from scratch", since while it's "almost" LDAP, it's different in a lot of ways). That Netscape code base was further bought and sold over the years to iPlanet, Sun Microsystems, and Red Hat (I'm probably missing somebody in that chain). It now lives in the Fedora umbrella as '389 Directory Server.' Probably the most popular fork of that code base now is OpenLDAP. IBM did the same thing, and the Directory Server I worked on was a fork of the UM code too, but it heavily diverged from the Netscape branches. The divergence was primarily due to: (1) backing to DB2 as opposed to BDB, and (2) needing to run on IBM's big iron like OS/400 and Z series mainframes. @@ -59,8 +59,8 @@ Oh, and on top of the technical merits, better or worse, it's an established st As I said earlier, I spent a lot of time at IBM observing how customers used LDAP, and the real items I took away from that experience were:
    • LDAP implementations have suffered a lot from never having been designed from the ground up for a large number of concurrent connections with asynchronous operations.
      • -
    • There are use cases for LDAP that just don't always fit the traditional "here's my server and storage engine" model. A lot of simple customer use cases wanted an LDAP access point, but not be forced into taking the heavy backends that came with it (they wanted the original gateway model!). There was an entire "sub" industry for this known as "meta directories" back in the late 90's and early 2000's.
      • -
    • Replication was always a sticking point. LDAP vendors all tried to offer a big multi-master, multi-site replication model. It was a lot of "bolt-on" complexity, done before the CAP theorem was written, and certainly before it was accepted as "truth."
      • +
    • There are use cases for LDAP that just don't always fit the traditional "here's my server and storage engine" model. A lot of simple customer use cases wanted an LDAP access point, but not be forced into taking the heavy backends that came with it (they wanted the original gateway model!). There was an entire "sub" industry for this known as "meta directories" back in the late 90's and early 2000's.
      • +
    • Replication was always a sticking point. LDAP vendors all tried to offer a big multi-master, multi-site replication model. It was a lot of "bolt-on" complexity, done before the CAP theorem was written, and certainly before it was accepted as "truth."
    • Nobody uses all of the protocol. In fact, 20% of the features solve 80% of the use cases (I'm making that number up, but you get the idea).
    @@ -78,10 +78,10 @@ Well, in the last year, I went to work for ASN.1 (the binary wire protocol) or the LDAP RFC in detail (this one mostly worked out; ldap_modify is still kind of a PITA). +The obvious question is how it turned out, and the answer is, honestly, better than I thought it would. When I set out to do this, I actually assumed I'd be shipping a much smaller percentage of the RFC than is there. There's actually about 95% of the core RFC implemented. I wasn't sure if the marriage of this protocol to node/JavaScript would work out, but if you've used express ever, this should be _really_ familiar. And I tried to make it as natural as possible to use "pure" JavaScript objects, rather than requiring the developer to understand ASN.1 (the binary wire protocol) or the LDAP RFC in detail (this one mostly worked out; ldap_modify is still kind of a PITA). Within 24 hours of releasing ldapjs on Twitter, there was an implementation of an address book that works with Thunderbird/Evolution, by the end of that weekend there was some slick integration with CouchDB, and ldapjs even got used in one of the node knockout apps. Off to a pretty good start!

    The Road Ahead

    -Hopefully you've been motivated to learn a little bit more about LDAP and try out ldapjs. The best place to start is probably the guide. After that you'll probably need to pick up a book from back in the day. ldapjs itself is still in its infancy; there's quite a bit of room to add some slick client-side logic (e.g., connection pools, automatic reconnects), easy to use schema validation, backends, etc. By the time this post is live, there will be experimental dtrace support if you're running on Mac OS X or preferably Joyent's SmartOS (shameless plug). And that nagging percentage of the protocol I didn't do will get filled in over time I suspect. If you've got an interest in any of this, send me some pull requests, but most importantly, I just want to see LDAP not just be a skeleton in the closet and get used in places where you should be using it. So get out there and write you some LDAP. +Hopefully you've been motivated to learn a little bit more about LDAP and try out ldapjs. The best place to start is probably the guide. After that you'll probably need to pick up a book from back in the day. ldapjs itself is still in its infancy; there's quite a bit of room to add some slick client-side logic (e.g., connection pools, automatic reconnects), easy to use schema validation, backends, etc. By the time this post is live, there will be experimental dtrace support if you're running on Mac OS X or preferably Joyent's SmartOS (shameless plug). And that nagging percentage of the protocol I didn't do will get filled in over time I suspect. If you've got an interest in any of this, send me some pull requests, but most importantly, I just want to see LDAP not just be a skeleton in the closet and get used in places where you should be using it. So get out there and write you some LDAP. diff --git a/locale/en/blog/vulnerability/aug-2019-security-releases.md b/locale/en/blog/vulnerability/aug-2019-security-releases.md index a911c125941b1..5c7142fa89e4d 100644 --- a/locale/en/blog/vulnerability/aug-2019-security-releases.md +++ b/locale/en/blog/vulnerability/aug-2019-security-releases.md @@ -25,7 +25,7 @@ also be found on each release page. * Node.js 8.16.1: https://nodejs.org/dist/latest-v8.x/ * Node.js 10.16.3: https://nodejs.org/dist/latest-v10.x/ -* Node.js 12.8.1: https://nodejs.org/dist/latest-v12.x +* Node.js 12.8.1: https://nodejs.org/dist/latest-v12.x/ ## Vulnerabilities Fixed diff --git a/locale/en/get-involved/index.md b/locale/en/get-involved/index.md index b4998e5b49f42..6476d6dbc6254 100644 --- a/locale/en/get-involved/index.md +++ b/locale/en/get-involved/index.md @@ -7,7 +7,7 @@ layout: contribute.hbs ## Community Discussion - The [GitHub issues list](https://github.com/nodejs/node/issues) is the place for discussion of Node.js core features. -- For real-time chat about Node.js development go to `irc.freenode.net` in the `#node.js` channel with an [IRC client](http://en.wikipedia.org/wiki/Comparison_of_Internet_Relay_Chat_clients) or connect in your web browser to the channel using [freenode's WebChat](http://webchat.freenode.net/?channels=node.js). +- For real-time chat about Node.js development go to `irc.freenode.net` in the `#node.js` channel with an [IRC client](https://en.wikipedia.org/wiki/Comparison_of_Internet_Relay_Chat_clients) or connect in your web browser to the channel using [freenode's WebChat](https://webchat.freenode.net/#node.js). - The official Node.js Twitter account is [nodejs](https://twitter.com/nodejs). - The [Node.js Foundation calendar](https://nodejs.org/calendar) with all public team meetings. - [Node.js Everywhere](https://newsletter.nodejs.org) is the official Node.js Monthly Newsletter. @@ -17,7 +17,7 @@ layout: contribute.hbs ## Learning -- [Official API reference documentation](/api) details the Node.js API. +- [Official API reference documentation](/api/) details the Node.js API. - [NodeSchool.io](http://nodeschool.io) will teach you Node.js concepts via interactive command-line games. - [Stack Overflow Node.js tag](http://stackoverflow.com/questions/tagged/node.js) collects new information every day. - [The DEV Community Node.js tag](https://dev.to/t/node) is a place to share Node.js projects, articles and tutorials as well as start discussions and ask for feedback on Node.js-related topics. Developers of all skill-levels are welcome to take part. diff --git a/locale/en/knowledge/cryptography/how-to-use-crypto-module.md b/locale/en/knowledge/cryptography/how-to-use-crypto-module.md index 2cab0bd12b08f..eddaaf51563be 100644 --- a/locale/en/knowledge/cryptography/how-to-use-crypto-module.md +++ b/locale/en/knowledge/cryptography/how-to-use-crypto-module.md @@ -8,9 +8,9 @@ difficulty: 3 layout: knowledge-post.hbs --- -The [crypto](https://nodejs.org/api/crypto.html) module is a wrapper for [OpenSSL](http://en.wikipedia.org/wiki/Openssl) cryptographic functions. It supports calculating hashes, authentication with HMAC, ciphers, and more! +The [crypto](https://nodejs.org/api/crypto.html) module is a wrapper for [OpenSSL](https://en.wikipedia.org/wiki/Openssl) cryptographic functions. It supports calculating hashes, authentication with HMAC, ciphers, and more! -The crypto module is mostly useful as a tool for implementing [cryptographic protocols](http://en.wikipedia.org/wiki/Cryptographic_protocol) such as [TLS](http://en.wikipedia.org/wiki/Transport_Layer_Security) and [https](http://en.wikipedia.org/wiki/Https). For most users, Node's built-in [tls module](https://nodejs.org/api/tls.html) and [https module](https://nodejs.org/api/https.html) should more than suffice. However, for the user that only wants to use small parts of what's needed for full-scale cryptography or is crazy/desperate enough to implement a protocol using OpenSSL and Node: Read on. +The crypto module is mostly useful as a tool for implementing [cryptographic protocols](https://en.wikipedia.org/wiki/Cryptographic_protocol) such as [TLS](https://en.wikipedia.org/wiki/Transport_Layer_Security) and [https](https://en.wikipedia.org/wiki/Https). For most users, Node's built-in [tls module](https://nodejs.org/api/tls.html) and [https module](https://nodejs.org/api/https.html) should more than suffice. However, for the user that only wants to use small parts of what's needed for full-scale cryptography or is crazy/desperate enough to implement a protocol using OpenSSL and Node: Read on. ## Hashes @@ -30,7 +30,7 @@ A hash is a fixed-length string of bits that is procedurally and deterministiall The hashes that work with crypto are dependent on what your version of OpenSSL supports. If you have a new enough version of OpenSSL, you can get a list of hash types your OpenSSL supports by typing `openssl list-message-digest-algorithms` into the command line. For older versions, simply type `openssl list-message-digest-commands` instead! -One of the most common hash algorithms is [SHA-256](https://en.wikipedia.org/wiki/SHA-2). Older popular types like **[SHA-1](http://en.wikipedia.org/wiki/Sha1) or [MD5](https://en.wikipedia.org/wiki/MD5#Security) are not secure any more** and should not be used. +One of the most common hash algorithms is [SHA-256](https://en.wikipedia.org/wiki/SHA-2). Older popular types like **[SHA-1](https://en.wikipedia.org/wiki/Sha1) or [MD5](https://en.wikipedia.org/wiki/MD5#Security) are not secure any more** and should not be used. ### How To Calculate Hashes with Crypto diff --git a/locale/en/knowledge/cryptography/how-to-use-the-tls-module.md b/locale/en/knowledge/cryptography/how-to-use-the-tls-module.md index e40e09e5804f2..689d5d5d3a9f4 100644 --- a/locale/en/knowledge/cryptography/how-to-use-the-tls-module.md +++ b/locale/en/knowledge/cryptography/how-to-use-the-tls-module.md @@ -12,13 +12,13 @@ layout: knowledge-post.hbs ## What is TLS? -[Transport Layer Security](http://en.wikipedia.org/wiki/Transport_Layer_Security) (or TSL) is the successor to Secure Sockets Layer (or SSL). It, along with SSL, are the de-facto standard cryptographic protocols for secure communications over the web. TSL encrypts communications on top of a network transport layer (typically tcp), and uses public-key cryptography to encrypt messages. +[Transport Layer Security](https://en.wikipedia.org/wiki/Transport_Layer_Security) (or TSL) is the successor to Secure Sockets Layer (or SSL). It, along with SSL, are the de-facto standard cryptographic protocols for secure communications over the web. TSL encrypts communications on top of a network transport layer (typically tcp), and uses public-key cryptography to encrypt messages. ### Public-Key Cryptography In public-key cryptography, each peer has two keys: A public key, and a private key. The public key is shared with everyone, and the private key is (naturally) kept secret. In order to encrypt a message, a computer requires its private key and the recipient's public key. Then, in order to decrypt the message, the recipient requires its *own* private key and the *sender*'s public key. -In TLS connections, the public key is called a *[certificate](http://en.wikipedia.org/wiki/Digital_certificate)*. This is because it's "[signed](http://en.wikipedia.org/wiki/Digital_signature)" to prove that the public key belongs to its owner. TLS certificates may either be signed by a third-party certificate authority (CA), or they may be [self-signed](http://en.wikipedia.org/wiki/Self-signed_certificate). In the case of Certificate Authorities, Mozilla keeps [a list of trusted root CAs](http://mxr.mozilla.org/mozilla/source/security/nss/lib/ckfw/builtins/certdata.txt) that are generally agreed upon by most web browsers. These root CAs may then issue certificates to other signing authorities, which in turn sign certificates for the general public. +In TLS connections, the public key is called a *[certificate](https://en.wikipedia.org/wiki/Digital_certificate)*. This is because it's "[signed](https://en.wikipedia.org/wiki/Digital_signature)" to prove that the public key belongs to its owner. TLS certificates may either be signed by a third-party certificate authority (CA), or they may be [self-signed](https://en.wikipedia.org/wiki/Self-signed_certificate). In the case of Certificate Authorities, Mozilla keeps [a list of trusted root CAs](http://mxr.mozilla.org/mozilla/source/security/nss/lib/ckfw/builtins/certdata.txt) that are generally agreed upon by most web browsers. These root CAs may then issue certificates to other signing authorities, which in turn sign certificates for the general public. ### History of TLS/SSL Support in Node.JS @@ -28,7 +28,7 @@ TLS support in node is relatively new. The first stable version of node.js to su ### tls.createServer -In most ways, the tls module's server api is similar to that of the net module. Besides the fact that it's for encrypted connections, the major difference is that the options object passed to `tls.connect` or `tls.createServer` needs to include information on both the private key and the certificate, in [pem format](http://en.wikipedia.org/wiki/X.509#Certificate_filename_extensions). Here's an example of a tls server: +In most ways, the tls module's server api is similar to that of the net module. Besides the fact that it's for encrypted connections, the major difference is that the options object passed to `tls.connect` or `tls.createServer` needs to include information on both the private key and the certificate, in [pem format](https://en.wikipedia.org/wiki/X.509#Certificate_filename_extensions). Here's an example of a tls server: var tls = require('tls'), fs = require('fs'), diff --git a/locale/en/security.md b/locale/en/security.md index 85576a37b338e..3e728366ad6fd 100644 --- a/locale/en/security.md +++ b/locale/en/security.md @@ -60,7 +60,7 @@ release process above to ensure that the disclosure is handled in a consistent m Security notifications will be distributed via the following methods. - -- +- ## Comments on this Policy diff --git a/locale/en/site.json b/locale/en/site.json index 559eeac5766f8..c72ba1849bd2c 100644 --- a/locale/en/site.json +++ b/locale/en/site.json @@ -94,12 +94,12 @@ "text": "ES6 and beyond" }, "api-lts": { - "link": "/dist/latest-%ver-major%/docs/api", + "link": "/dist/latest-%ver-major%/docs/api/", "subtext": "LTS", "text": "%ver% API" }, "api-current": { - "link": "/dist/latest-%ver-major%/docs/api", + "link": "/dist/latest-%ver-major%/docs/api/", "text": "%ver% API" }, "guides": { diff --git a/locale/es/about/governance.md b/locale/es/about/governance.md index d48b0b45a19d4..4fc1e21f451ce 100644 --- a/locale/es/about/governance.md +++ b/locale/es/about/governance.md @@ -26,7 +26,7 @@ El proyecto está gestionado conjuntamente por el [Comité de Dirección Técnic [COLLABORATOR_GUIDE.md]: https://github.com/nodejs/node/blob/master/COLLABORATOR_GUIDE.md [Comité de la Comunidad (CommComm)]: https://github.com/nodejs/community-committee/blob/master/Community-Committee-Charter.md -[Búsqueda de Consenso]: http://en.wikipedia.org/wiki/Consensus-seeking_decision-making +[Búsqueda de Consenso]: https://en.wikipedia.org/wiki/Consensus-seeking_decision-making [README.md]: https://github.com/nodejs/node/blob/master/README.md#current-project-team-members [Comité de Dirección Técnica (TSC)]: https://github.com/nodejs/TSC/blob/master/TSC-Charter.md [TSC]: https://github.com/nodejs/TSC diff --git a/locale/es/get-involved/index.md b/locale/es/get-involved/index.md index 2e1a805ec4b8e..4747090f02d72 100644 --- a/locale/es/get-involved/index.md +++ b/locale/es/get-involved/index.md @@ -8,7 +8,7 @@ layout: contribute.hbs ## Discusión de la comunidad - La [lista de errores en](https://github.com/nodejs/node/issues) es el lugar para discutir las características del núcleo de Node.js. -- Para chatear en tiempo real sobre el desarrollo de Node vaya a `irc.freenode.net` en el canal `#node.js` usando un [cliente de IRC](http://es.wikipedia.org/wiki/Anexo:Clientes_IRC) ó conéctese con su navegador al canal usando [WebChat de freenode](http://webchat.freenode.net/?channels=node.js). +- Para chatear en tiempo real sobre el desarrollo de Node vaya a `irc.freenode.net` en el canal `#node.js` usando un [cliente de IRC](https://es.wikipedia.org/wiki/Anexo:Clientes_IRC) ó conéctese con su navegador al canal usando [WebChat de freenode](https://webchat.freenode.net/#node.js). - La cuenta de Twitter oficial de Node.js es [nodejs](https://twitter.com/nodejs). - El [calendario de la Fundación Node.js](https://nodejs.org/calendar) con todas las reuniones del equipo público. - [Node Weekly](http://nodeweekly.com) es una lista de correo que recopila los últimos eventos y noticias alrededor de la comunidad de Node.js. @@ -17,7 +17,7 @@ layout: contribute.hbs ## Aprendizaje -- La [Documentación oficial de la API](/api) detalla la API de Node. +- La [Documentación oficial de la API](/api/) detalla la API de Node. - [NodeSchool.io](http://nodeschool.io) le enseñará conceptos de Node.js de forma interactiva mediante juegos utilizando la línea de comandos. - La [etiqueta de Node.js en Stack Overflow](http://stackoverflow.com/questions/tagged/node.js) colecciona nueva información cada día. diff --git a/locale/es/security.md b/locale/es/security.md index d387b3176324c..cbd80056536f9 100644 --- a/locale/es/security.md +++ b/locale/es/security.md @@ -46,8 +46,8 @@ proceso descrito arriba, para asegurarse que la divulgación sea manejada de una Las notificaciones de seguridad serán distribuidas usando los siguientes medios. -- [https://groups.google.com/group/nodejs-sec](https://groups.google.com/group/nodejs-sec) -- [https://nodejs.org/en/blog](https://nodejs.org/en/blog) +- +- ## Comentarios sobre esta política diff --git a/locale/es/site.json b/locale/es/site.json index 274879fb0a481..9c60a9e17640e 100644 --- a/locale/es/site.json +++ b/locale/es/site.json @@ -94,12 +94,12 @@ "text": "ES6 y más allá" }, "api-lts": { - "link": "/dist/latest-%ver-major%/docs/api", + "link": "/dist/latest-%ver-major%/docs/api/", "subtext": "LTS", "text": "%ver% API" }, "api-current": { - "link": "/dist/latest-%ver-major%/docs/api", + "link": "/dist/latest-%ver-major%/docs/api/", "text": "%ver% API" }, "guides": { diff --git a/locale/fa/about/governance.md b/locale/fa/about/governance.md index 720a6fe30d06c..c300aff972260 100644 --- a/locale/fa/about/governance.md +++ b/locale/fa/about/governance.md @@ -126,7 +126,7 @@ agenda item and sending it as a pull request after the meeting. ## Consensus Seeking Process The TSC follows a -[Consensus Seeking](http://en.wikipedia.org/wiki/Consensus-seeking_decision-making) +[Consensus Seeking](https://en.wikipedia.org/wiki/Consensus-seeking_decision-making) decision making model. When an agenda item has appeared to reach a consensus, the moderator diff --git a/locale/fa/get-involved/index.md b/locale/fa/get-involved/index.md index 5fa99313c9df4..dd22e93f813ca 100644 --- a/locale/fa/get-involved/index.md +++ b/locale/fa/get-involved/index.md @@ -8,7 +8,7 @@ layout: contribute.hbs ## Community Discussion - The [GitHub issues list](https://github.com/nodejs/node/issues) is the place for discussion of Node.js core features. -- For real-time chat about Node development go to `irc.freenode.net` in the `#node.js` channel with an [IRC client](http://en.wikipedia.org/wiki/Comparison_of_Internet_Relay_Chat_clients) or connect in your web browser to the channel using [freenode's WebChat](http://webchat.freenode.net/?channels=node.js). +- For real-time chat about Node development go to `irc.freenode.net` in the `#node.js` channel with an [IRC client](https://en.wikipedia.org/wiki/Comparison_of_Internet_Relay_Chat_clients) or connect in your web browser to the channel using [freenode's WebChat](https://webchat.freenode.net/#node.js). - The official Node.js Twitter account is [nodejs](https://twitter.com/nodejs). - [Node.js Everywhere](https://newsletter.nodejs.org) is the official Node.js Monthly Newsletter. - [Node.js Collection](https://medium.com/the-node-js-collection) is a collection of community-curated content on Medium. @@ -17,7 +17,7 @@ layout: contribute.hbs ## Learning -- [Official API reference documentation](/api) details the Node API. +- [Official API reference documentation](/api/) details the Node API. - [NodeSchool.io](http://nodeschool.io) will teach you Node.js concepts via interactive command-line games. - [Stack Overflow Node.js tag](http://stackoverflow.com/questions/tagged/node.js) collects new information every day. - [The DEV Community Node.js tag](https://dev.to/t/node) is a place to share Node.js projects, articles and tutorials as well as start discussions and ask for feedback on Node.js-related topics. Developers of all skill-levels are welcome to take part. diff --git a/locale/fa/knowledge/cryptography/how-to-use-crypto-module.md b/locale/fa/knowledge/cryptography/how-to-use-crypto-module.md index 83e73a12d56b3..4efabad9380ea 100644 --- a/locale/fa/knowledge/cryptography/how-to-use-crypto-module.md +++ b/locale/fa/knowledge/cryptography/how-to-use-crypto-module.md @@ -8,9 +8,9 @@ difficulty: 3 layout: knowledge-post.hbs --- -The [crypto](https://nodejs.org/docs/v0.4.10/api/crypto.html) module is a wrapper for [OpenSSL](http://en.wikipedia.org/wiki/Openssl) cryptographic functions. It supports calculating hashes, authentication with HMAC, ciphers, and more! +The [crypto](https://nodejs.org/docs/v0.4.10/api/crypto.html) module is a wrapper for [OpenSSL](https://en.wikipedia.org/wiki/Openssl) cryptographic functions. It supports calculating hashes, authentication with HMAC, ciphers, and more! -The crypto module is mostly useful as a tool for implementing [cryptographic protocols](http://en.wikipedia.org/wiki/Cryptographic_protocol) such as [TLS](http://en.wikipedia.org/wiki/Transport_Layer_Security) and [https](http://en.wikipedia.org/wiki/Https). For most users, Node's built-in [tls module](https://nodejs.org/docs/v0.4.10/api/tls.html) and [https module](https://nodejs.org/docs/v0.4.10/api/https.html) should more than suffice. However, for the user that only wants to use small parts of what's needed for full-scale cryptography or is crazy/desperate enough to implement a protocol using OpenSSL and Node: Read on. +The crypto module is mostly useful as a tool for implementing [cryptographic protocols](https://en.wikipedia.org/wiki/Cryptographic_protocol) such as [TLS](https://en.wikipedia.org/wiki/Transport_Layer_Security) and [https](https://en.wikipedia.org/wiki/Https). For most users, Node's built-in [tls module](https://nodejs.org/docs/v0.4.10/api/tls.html) and [https module](https://nodejs.org/docs/v0.4.10/api/https.html) should more than suffice. However, for the user that only wants to use small parts of what's needed for full-scale cryptography or is crazy/desperate enough to implement a protocol using OpenSSL and Node: Read on. ## Hashes @@ -30,8 +30,8 @@ A hash is a fixed-length string of bits that is procedurally and deterministiall The hashes that work with crypto are dependent on what your version of OpenSSL supports. If you have a new enough version of OpenSSL, you can get a list of hash types your OpenSSL supports by typing `openssl list-message-digest-algorithms` into the command line. For older versions, simply type `openssl list-message-digest-commands` instead! Some of the most common hash types are: -* [sha1](http://en.wikipedia.org/wiki/Sha1) -* [md5](http://en.wikipedia.org/wiki/Md5). +* [sha1](https://en.wikipedia.org/wiki/Sha1) +* [md5](https://en.wikipedia.org/wiki/Md5). ### How To Calculate Hashes with Crypto @@ -62,7 +62,7 @@ Ciphers allow you to encode and decode messages given a password. ### Cipher Algorithms That Work With Crypto -Like crypto's hash algorithms, the cyphers that work with crypto are dependent on what your version of OpenSSL supports. You can get a list of hash types your OpenSSL supports by typing `openssl list-cipher-commands` into the command line for older versions, or `openssl list-cipher-algorithms` for newer versions of OpenSSL. OpenSSL supports *many* ciphers; A good and popular one is [AES192](http://en.wikipedia.org/wiki/Aes192). +Like crypto's hash algorithms, the cyphers that work with crypto are dependent on what your version of OpenSSL supports. You can get a list of hash types your OpenSSL supports by typing `openssl list-cipher-commands` into the command line for older versions, or `openssl list-cipher-algorithms` for newer versions of OpenSSL. OpenSSL supports *many* ciphers; A good and popular one is [AES192](https://en.wikipedia.org/wiki/Aes192). ### How To Use Cipher Algorithms with Crypto: diff --git a/locale/fa/knowledge/cryptography/how-to-use-the-tls-module.md b/locale/fa/knowledge/cryptography/how-to-use-the-tls-module.md index e40e09e5804f2..689d5d5d3a9f4 100644 --- a/locale/fa/knowledge/cryptography/how-to-use-the-tls-module.md +++ b/locale/fa/knowledge/cryptography/how-to-use-the-tls-module.md @@ -12,13 +12,13 @@ layout: knowledge-post.hbs ## What is TLS? -[Transport Layer Security](http://en.wikipedia.org/wiki/Transport_Layer_Security) (or TSL) is the successor to Secure Sockets Layer (or SSL). It, along with SSL, are the de-facto standard cryptographic protocols for secure communications over the web. TSL encrypts communications on top of a network transport layer (typically tcp), and uses public-key cryptography to encrypt messages. +[Transport Layer Security](https://en.wikipedia.org/wiki/Transport_Layer_Security) (or TSL) is the successor to Secure Sockets Layer (or SSL). It, along with SSL, are the de-facto standard cryptographic protocols for secure communications over the web. TSL encrypts communications on top of a network transport layer (typically tcp), and uses public-key cryptography to encrypt messages. ### Public-Key Cryptography In public-key cryptography, each peer has two keys: A public key, and a private key. The public key is shared with everyone, and the private key is (naturally) kept secret. In order to encrypt a message, a computer requires its private key and the recipient's public key. Then, in order to decrypt the message, the recipient requires its *own* private key and the *sender*'s public key. -In TLS connections, the public key is called a *[certificate](http://en.wikipedia.org/wiki/Digital_certificate)*. This is because it's "[signed](http://en.wikipedia.org/wiki/Digital_signature)" to prove that the public key belongs to its owner. TLS certificates may either be signed by a third-party certificate authority (CA), or they may be [self-signed](http://en.wikipedia.org/wiki/Self-signed_certificate). In the case of Certificate Authorities, Mozilla keeps [a list of trusted root CAs](http://mxr.mozilla.org/mozilla/source/security/nss/lib/ckfw/builtins/certdata.txt) that are generally agreed upon by most web browsers. These root CAs may then issue certificates to other signing authorities, which in turn sign certificates for the general public. +In TLS connections, the public key is called a *[certificate](https://en.wikipedia.org/wiki/Digital_certificate)*. This is because it's "[signed](https://en.wikipedia.org/wiki/Digital_signature)" to prove that the public key belongs to its owner. TLS certificates may either be signed by a third-party certificate authority (CA), or they may be [self-signed](https://en.wikipedia.org/wiki/Self-signed_certificate). In the case of Certificate Authorities, Mozilla keeps [a list of trusted root CAs](http://mxr.mozilla.org/mozilla/source/security/nss/lib/ckfw/builtins/certdata.txt) that are generally agreed upon by most web browsers. These root CAs may then issue certificates to other signing authorities, which in turn sign certificates for the general public. ### History of TLS/SSL Support in Node.JS @@ -28,7 +28,7 @@ TLS support in node is relatively new. The first stable version of node.js to su ### tls.createServer -In most ways, the tls module's server api is similar to that of the net module. Besides the fact that it's for encrypted connections, the major difference is that the options object passed to `tls.connect` or `tls.createServer` needs to include information on both the private key and the certificate, in [pem format](http://en.wikipedia.org/wiki/X.509#Certificate_filename_extensions). Here's an example of a tls server: +In most ways, the tls module's server api is similar to that of the net module. Besides the fact that it's for encrypted connections, the major difference is that the options object passed to `tls.connect` or `tls.createServer` needs to include information on both the private key and the certificate, in [pem format](https://en.wikipedia.org/wiki/X.509#Certificate_filename_extensions). Here's an example of a tls server: var tls = require('tls'), fs = require('fs'), diff --git a/locale/fa/security.md b/locale/fa/security.md index 41b5d2f09837e..e1932c1a04b2e 100644 --- a/locale/fa/security.md +++ b/locale/fa/security.md @@ -59,7 +59,7 @@ title: امنیت اعلان‌های امنیتی به روش‌های زیر توزیع خواهند شد. - [گروه گوگل https://groups.google.com/group/nodejs-sec](https://groups.google.com/group/nodejs-sec) -- [بلاگ https://nodejs.org/en/blog](https://nodejs.org/en/blog) +- [بلاگ https://nodejs.org/en/blog/](https://nodejs.org/en/blog/) ## نظرات بر روی این سیاست diff --git a/locale/fa/site.json b/locale/fa/site.json index 91ea8b7f7ba75..f5286f03a91aa 100644 --- a/locale/fa/site.json +++ b/locale/fa/site.json @@ -94,12 +94,12 @@ "text": "ES6 و فراتر" }, "api-lts": { - "link": "/dist/latest-%ver-major%/docs/api", + "link": "/dist/latest-%ver-major%/docs/api/", "subtext": "LTS", "text": "%ver% API" }, "api-current": { - "link": "/dist/latest-%ver-major%/docs/api", + "link": "/dist/latest-%ver-major%/docs/api/", "text": "%ver% API" }, "guides": { diff --git a/locale/fr/about/governance.md b/locale/fr/about/governance.md index 2d7c0822477be..0cf739c2ed4eb 100644 --- a/locale/fr/about/governance.md +++ b/locale/fr/about/governance.md @@ -132,7 +132,7 @@ chaque réunion. ## Processus de Recherche de Consensus Le TSC suit un modèle décisionnaire de -[Recherche de Consensus](http://en.wikipedia.org/wiki/Consensus-seeking_decision-making) +[Recherche de Consensus](https://en.wikipedia.org/wiki/Consensus-seeking_decision-making) (en anglais). Quand un objet du programme a atteint un consensus, le modérateur diff --git a/locale/fr/get-involved/index.md b/locale/fr/get-involved/index.md index c06654c1a80e4..5353eca4c3fc7 100644 --- a/locale/fr/get-involved/index.md +++ b/locale/fr/get-involved/index.md @@ -9,7 +9,7 @@ layout: contribute.hbs - La [liste des tickets GitHub](https://github.com/nodejs/node/issues) est le bon endroit pour discuter des fonctionnalités cœurs de Node.js. -- Pour une discussion temps réel à propos du développement Node, allez sur `irc.freenode.net` dans le canal `#node.js` avec un [client IRC](https://fr.wikipedia.org/wiki/Liste_de_clients_IRC) ou connectez vous depuis votre navigateur web en utilisant [le WebChat de freenode](http://webchat.freenode.net/?channels=node.js) (en anglais). +- Pour une discussion temps réel à propos du développement Node, allez sur `irc.freenode.net` dans le canal `#node.js` avec un [client IRC](https://fr.wikipedia.org/wiki/Liste_de_clients_IRC) ou connectez vous depuis votre navigateur web en utilisant [le WebChat de freenode](https://webchat.freenode.net/#node.js) (en anglais). - Le compte Twitter officiel de Node.js est [nodejs](https://twitter.com/nodejs) (en anglais). @@ -24,7 +24,7 @@ layout: contribute.hbs ## Apprentissage -- [La documentation officielle de l'API de référence](/api) détaille l'API Node (en anglais). +- [La documentation officielle de l'API de référence](/api/) détaille l'API Node (en anglais). - [NodeSchool.io](https://nodeschool.io/fr-fr/) vous apprendra les concepts de Node.js avec des jeux interactifs en ligne de commande. diff --git a/locale/fr/security.md b/locale/fr/security.md index b5e613d76c8a9..cbb71622e18b4 100644 --- a/locale/fr/security.md +++ b/locale/fr/security.md @@ -48,7 +48,7 @@ Voici la politique de divulgation des failles de sécurité pour Node.js : Les alertes de sécurité sont relayées sur les canaux suivants. -- [https://groups.google.com/group/nodejs-sec](https://groups.google.com/group/nodejs-sec) +- - [https://nodejs.org/fr/blog](https://nodejs.org/fr/blog) ## Commentaires à propos de cette politique de sécurité diff --git a/locale/fr/site.json b/locale/fr/site.json index ad54331b624c2..5936ed30a8cc7 100644 --- a/locale/fr/site.json +++ b/locale/fr/site.json @@ -85,12 +85,12 @@ "text": "ES6 et au-delà" }, "api-lts": { - "link": "/dist/latest-%ver-major%/docs/api", + "link": "/dist/latest-%ver-major%/docs/api/", "subtext": "LTS", "text": "%ver% API" }, "api-current": { - "link": "/dist/latest-%ver-major%/docs/api", + "link": "/dist/latest-%ver-major%/docs/api/", "text": "%ver% API" }, "guides": { diff --git a/locale/gl/security.md b/locale/gl/security.md index 2bc26a176e7f5..6b63f4a2f4b1e 100644 --- a/locale/gl/security.md +++ b/locale/gl/security.md @@ -52,8 +52,8 @@ consistente. As notificacións de seguridade serán distribuídas usando os seguintes medios. -- [https://groups.google.com/group/nodejs-sec](https://groups.google.com/group/nodejs-sec) -- [https://nodejs.org/en/blog](https://nodejs.org/en/blog) +- +- ## Comentarios sobre esta política diff --git a/locale/gl/site.json b/locale/gl/site.json index 1928ead55b091..6c095f2f27607 100644 --- a/locale/gl/site.json +++ b/locale/gl/site.json @@ -87,12 +87,12 @@ "text": "ES6 e máis aló" }, "api-lts": { - "link": "/dist/latest-%ver-major%/docs/api", + "link": "/dist/latest-%ver-major%/docs/api/", "subtext": "LTS", "text": "%ver% API" }, "api-current": { - "link": "/dist/latest-%ver-major%/docs/api", + "link": "/dist/latest-%ver-major%/docs/api/", "text": "%ver% API" }, "guides": { diff --git a/locale/it/about/governance.md b/locale/it/about/governance.md index 035f6e3ce3370..24581f3780a94 100644 --- a/locale/it/about/governance.md +++ b/locale/it/about/governance.md @@ -30,7 +30,7 @@ extending the Node.js community. [COLLABORATOR_GUIDE.md]: https://github.com/nodejs/node/blob/master/COLLABORATOR_GUIDE.md [Community Committee (CommComm)]: https://github.com/nodejs/community-committee/blob/master/Community-Committee-Charter.md -[Consensus Seeking]: http://en.wikipedia.org/wiki/Consensus-seeking_decision-making +[Consensus Seeking]: https://en.wikipedia.org/wiki/Consensus-seeking_decision-making [README.md]: https://github.com/nodejs/node/blob/master/README.md#current-project-team-members [Technical Steering Committee (TSC)]: https://github.com/nodejs/TSC/blob/master/TSC-Charter.md [TSC]: https://github.com/nodejs/TSC diff --git a/locale/it/get-involved/index.md b/locale/it/get-involved/index.md index b4998e5b49f42..6476d6dbc6254 100644 --- a/locale/it/get-involved/index.md +++ b/locale/it/get-involved/index.md @@ -7,7 +7,7 @@ layout: contribute.hbs ## Community Discussion - The [GitHub issues list](https://github.com/nodejs/node/issues) is the place for discussion of Node.js core features. -- For real-time chat about Node.js development go to `irc.freenode.net` in the `#node.js` channel with an [IRC client](http://en.wikipedia.org/wiki/Comparison_of_Internet_Relay_Chat_clients) or connect in your web browser to the channel using [freenode's WebChat](http://webchat.freenode.net/?channels=node.js). +- For real-time chat about Node.js development go to `irc.freenode.net` in the `#node.js` channel with an [IRC client](https://en.wikipedia.org/wiki/Comparison_of_Internet_Relay_Chat_clients) or connect in your web browser to the channel using [freenode's WebChat](https://webchat.freenode.net/#node.js). - The official Node.js Twitter account is [nodejs](https://twitter.com/nodejs). - The [Node.js Foundation calendar](https://nodejs.org/calendar) with all public team meetings. - [Node.js Everywhere](https://newsletter.nodejs.org) is the official Node.js Monthly Newsletter. @@ -17,7 +17,7 @@ layout: contribute.hbs ## Learning -- [Official API reference documentation](/api) details the Node.js API. +- [Official API reference documentation](/api/) details the Node.js API. - [NodeSchool.io](http://nodeschool.io) will teach you Node.js concepts via interactive command-line games. - [Stack Overflow Node.js tag](http://stackoverflow.com/questions/tagged/node.js) collects new information every day. - [The DEV Community Node.js tag](https://dev.to/t/node) is a place to share Node.js projects, articles and tutorials as well as start discussions and ask for feedback on Node.js-related topics. Developers of all skill-levels are welcome to take part. diff --git a/locale/it/security.md b/locale/it/security.md index 177d2d41b8235..f623023b5c57e 100644 --- a/locale/it/security.md +++ b/locale/it/security.md @@ -48,8 +48,8 @@ Queste fix non sono pubblicate nel repository ma piuttosto mantenute localmente Le notifiche di sicurezza verranno distribuite nei seguenti modi. -- [https://groups.google.com/group/nodejs-sec](https://groups.google.com/group/nodejs-sec) -- [https://nodejs.org/en/blog](https://nodejs.org/en/blog) +- +- ## Commenti su questa Politica diff --git a/locale/it/site.json b/locale/it/site.json index 0a5bfa56ded78..012f220f66ba8 100644 --- a/locale/it/site.json +++ b/locale/it/site.json @@ -78,12 +78,12 @@ "text": "ES6 e oltre" }, "api-lts": { - "link": "/dist/latest-%ver-major%/docs/api", + "link": "/dist/latest-%ver-major%/docs/api/", "subtext": "LTS", "text": "%ver% API" }, "api-current": { - "link": "/dist/latest-%ver-major%/docs/api", + "link": "/dist/latest-%ver-major%/docs/api/", "text": "%ver% API" }, "guides": { diff --git a/locale/ja/get-involved/index.md b/locale/ja/get-involved/index.md index cf7216b11f9c1..119545fae0014 100644 --- a/locale/ja/get-involved/index.md +++ b/locale/ja/get-involved/index.md @@ -8,7 +8,7 @@ layout: contribute.hbs ## Community Discussion - The [GitHub issues list](https://github.com/nodejs/node/issues) is the place for discussion of Node.js core features. -- For real-time chat about Node.js development go to `irc.freenode.net` in the `#node.js` channel with an [IRC client](http://en.wikipedia.org/wiki/Comparison_of_Internet_Relay_Chat_clients) or connect in your web browser to the channel using [freenode's WebChat](http://webchat.freenode.net/?channels=node.js). +- For real-time chat about Node.js development go to `irc.freenode.net` in the `#node.js` channel with an [IRC client](https://en.wikipedia.org/wiki/Comparison_of_Internet_Relay_Chat_clients) or connect in your web browser to the channel using [freenode's WebChat](https://webchat.freenode.net/#node.js). - The official Node.js Twitter account is [nodejs](https://twitter.com/nodejs). - The [Node.js Foundation calendar](https://nodejs.org/calendar) with all public team meetings. - [Node.js Everywhere](https://newsletter.nodejs.org) is the official Node.js Monthly Newsletter. @@ -22,7 +22,7 @@ layout: contribute.hbs ## コミュニティディスカッション - [GitHub issues リスト](https://github.com/nodejs/node/issues) は、Node.js のコア機能に関する議論の場です。 -- Node.js 開発についてのリアルタイムチャットは、[IRC クライアント](http://en.wikipedia.org/wiki/Comparison_of_Internet_Relay_Chat_clients) を使って `#node.js` チャンネルで `irc.freenode.net` に行くか、または [freenode's WebChat](http://webchat.freenode.net/?channels=node.js) を使ってあなたの Web ブラウザでそのチャンネルに接続してください。 +- Node.js 開発についてのリアルタイムチャットは、[IRC クライアント](https://en.wikipedia.org/wiki/Comparison_of_Internet_Relay_Chat_clients) を使って `#node.js` チャンネルで `irc.freenode.net` に行くか、または [freenode's WebChat](https://webchat.freenode.net/#node.js) を使ってあなたの Web ブラウザでそのチャンネルに接続してください。 - Node.js 公式 Twitter アカウントは [nodejs](https://twitter.com/nodejs) です。 - [Node.js Foundation calendar](https://nodejs.org/calendar) とすべての公開チームミーティング。 - [Node.js Everywhere](https://newsletter.nodejs.org) は、公式の Node.js マンスリーニュースレターです。 @@ -32,7 +32,7 @@ layout: contribute.hbs ## 学習 -- [公式 API リファレンスドキュメント](/api) は、Node.js API の詳細を説明しています。 +- [公式 API リファレンスドキュメント](/api/) は、Node.js API の詳細を説明しています。 - [NodeSchool.io](http://nodeschool.io) はインタラクティブなコマンドラインゲームを介して Node.js の概念を教えます。 - [Stack Overflow Node.js tag](http://stackoverflow.com/questions/tagged/node.js) は、毎日新しい情報を収集します。 - [The DEV Community Node.js tag](https://dev.to/t/node) は、Node.js プロジェクト、記事、チュートリアルを共有したり、ディスカッションを開始したり、Node.js 関連のトピックについてのフィードバックを求めたりする場所です。スキルレベルに関係なくすべての開発者が参加できます。 diff --git a/locale/ja/security.md b/locale/ja/security.md index cb83fd387d48f..d223fd80f893a 100644 --- a/locale/ja/security.md +++ b/locale/ja/security.md @@ -108,16 +108,16 @@ Node.js における、情報開示のポリシーをここに記します。 Security notifications will be distributed via the following methods. -- [https://groups.google.com/group/nodejs-sec](https://groups.google.com/group/nodejs-sec) -- [https://nodejs.org/en/blog](https://nodejs.org/en/blog) +- +- --> ## セキュリティリポートを受け取る セキュリティリポートは、以下のサイトを介して報告されます。 -- [https://groups.google.com/group/nodejs-sec](https://groups.google.com/group/nodejs-sec) -- [https://nodejs.org/en/blog](https://nodejs.org/en/blog) +- +- ## 합의점을 찾는 과정 -TSC는 [합의점 찾기](http://en.wikipedia.org/wiki/Consensus-seeking_decision-making) 의사결정 모델을 따릅니다. +TSC는 [합의점 찾기](https://en.wikipedia.org/wiki/Consensus-seeking_decision-making) 의사결정 모델을 따릅니다. 의제가 합의점을 찾았을 때 중재자는 합의점에 대한 반대의견을 받기 위한 마지막 요청으로 "반대하는 사람 있습니까?"라고 물을 것입니다. diff --git a/locale/ko/get-involved/index.md b/locale/ko/get-involved/index.md index 88c57a51efe40..6a0d0820aeddc 100644 --- a/locale/ko/get-involved/index.md +++ b/locale/ko/get-involved/index.md @@ -11,7 +11,7 @@ layout: contribute.hbs ## Community Discussion - The [GitHub issues list](https://github.com/nodejs/node/issues) is the place for discussion of Node.js core features. -- For real-time chat about Node.js development go to `irc.freenode.net` in the `#node.js` channel with an [IRC client](http://en.wikipedia.org/wiki/Comparison_of_Internet_Relay_Chat_clients) or connect in your web browser to the channel using [freenode's WebChat](http://webchat.freenode.net/?channels=node.js). +- For real-time chat about Node.js development go to `irc.freenode.net` in the `#node.js` channel with an [IRC client](https://en.wikipedia.org/wiki/Comparison_of_Internet_Relay_Chat_clients) or connect in your web browser to the channel using [freenode's WebChat](https://webchat.freenode.net/#node.js). - The official Node.js Twitter account is [nodejs](https://twitter.com/nodejs). - The [Node.js Foundation calendar](https://nodejs.org/calendar) with all public team meetings. - [Node.js Everywhere](https://newsletter.nodejs.org) is the official Node.js Monthly Newsletter. @@ -21,7 +21,7 @@ layout: contribute.hbs ## 커뮤니티 논의 - [GitHub 이슈 목록](https://github.com/nodejs/node/issues)에서 Node.js 코어 기능에 대한 논의가 이루어집니다. -- Node.js 개발에 대해 실시간으로 이야기하고 싶다면 [IRC 클라이언트](http://en.wikipedia.org/wiki/Comparison_of_Internet_Relay_Chat_clients)나 [freenode의 웹챗](http://webchat.freenode.net/?channels=node.js)을 이용해 `irc.freenode.net`의 `#node.js` 채널에 가보세요. +- Node.js 개발에 대해 실시간으로 이야기하고 싶다면 [IRC 클라이언트](https://en.wikipedia.org/wiki/Comparison_of_Internet_Relay_Chat_clients)나 [freenode의 웹챗](https://webchat.freenode.net/#node.js)을 이용해 `irc.freenode.net`의 `#node.js` 채널에 가보세요. - Node.js의 공식 트위터 계정은 [nodejs](https://twitter.com/nodejs)입니다. - [Node.js 재단 캘린더](https://nodejs.org/calendar)에 모든 공개 팀 미팅 일정이 포함되어 있습니다. - [Node.js Everywhere](https://newsletter.nodejs.org)는 공식 Node.js 월간 뉴스레터입니다. @@ -32,7 +32,7 @@ layout: contribute.hbs ## 알아보기 -- [공식 API 레퍼런스 문서](/api)는 Node.js API에 대해 설명합니다. +- [공식 API 레퍼런스 문서](/api/)는 Node.js API에 대해 설명합니다. - [NodeSchool.io](http://nodeschool.io)는 대화형 명령행 게임을 통해 Node.js 개념에 대해 알려줍니다. - [Stack Overflow Node.js 태그](http://stackoverflow.com/questions/tagged/node.js)에는 매일 새로운 정보가 쌓입니다. - [The DEV Community Node.js 태그](https://dev.to/t/node)는 Node.js와 관련된 주제에 대해 논의하거나 의견을 묻기에도 좋고, Node.js 프로젝트, 글, 튜토리얼을 공유하기에도 좋은 장소입니다. 개발자라면 모두 환영합니다. diff --git a/locale/ko/security.md b/locale/ko/security.md index f68bc72d78eaf..31eab02b9683b 100644 --- a/locale/ko/security.md +++ b/locale/ko/security.md @@ -126,7 +126,7 @@ release process above to ensure that the disclosure is handled in a consistent m Security notifications will be distributed via the following methods. - -- +- --> ## 보안 업데이트 받기 @@ -134,7 +134,7 @@ Security notifications will be distributed via the following methods. 다음 방법으로 보안 공지를 합니다. - -- +-