Awalkthrough of the documentation of node on a small scale

plaintext HTTP plus checksums in the HTML page don't provide protection for the node.js binary distributions from tampering. Examples of other similar projects that provide https:

https://www.python.org/
https://www.ruby-lang.org/en/
https://golang.org/

The homepage (/) points to the x64 installer, but the link on /downloads (the one above the table of platforms/architectures) points to the x86 installer.

The links should be consistent.

http://nodejs.org/download/ links to a SHASUMS file that's served over HTTP with no signatures. It's possible to find the signatures by editing the file's URL, but you should have a direct link to SHASUMS.txt.asc so it's clear how to verify a download.

Reposted from nodejs/node-v0.x-archive#7571 at @trevnorris's request

Chris Williams built a web site that provides updates from the Node AB. The URL is http://nodeadvisoryboard.com. I propose we add a link to this web site from the home page of nodejs.org so it is easy to find.

On Chrome and Firefox, there is a "partially encrypted" warning when visiting download page. I find some png links are using http.

nodejs/node-v0.x-archive#14570

Unlike the rest of the images on the site, the Linux Foundation header is neither SVG nor high resolution. On high DPI screens, it looks poor compared to the rest of the content.

The contributing page has a link to the Wikipedia article on Git, but the ending ")" is cut off.

https://github.com/joyent/node-website/blob/52f8be7b55e3b4676cd6f8bee544412176ce61a8/doc/documentation/contributing/index.md

Looks to be the markdown compiler since the raw is correct.

markedjs/marked#366

top nav overflow on Firefox: http://cl.ly/image/0U2B1l3S2x0V

This is Firefox Aurora, 32.0a2 (2014-07-21) on Mac

The latest version shown on the homepage as well as on the download page and the target of the install link is 0.10.32, but it should be 0.10.33.

I visite the new site sometimes some page will return 404, such as the api, resource. about page

It would be great if nodejs.org were accessible over HTTPS - if not for the whole site, at least for the installer downloads. The only relatively secure alternative I can find is to checkout the source from github and build it myself.

Both links to Node.js and Joyent in the job page's header are broken.

I tested the website with sslyze

SCAN RESULTS FOR NODEJS.ORG:443 - 165.225.133.150:443

• Deflate Compression:
  OK - Compression disabled
• Session Renegotiation:
  Client-initiated Renegotiations: OK - Rejected
  Secure Renegotiation: OK - Supported
• OpenSSL Heartbleed:
  OK - Not vulnerable to Heartbleed
• Certificate - Content:
  SHA1 Fingerprint: 9f554d8b1d118a77e98b209bf412b91a0a62846f
  Common Name: nodejs.org
  Issuer: thawte DV SSL CA - G2
  Serial Number: 3B1458209F5222D2DEA6B16C2C48544C
  Not Before: Oct 17 00:00:00 2014 GMT
  Not After: Oct 17 23:59:59 2015 GMT
  Signature Algorithm: sha256WithRSAEncryption
  Key Size: 2048 bit
  Exponent: 65537 (0x10001)
  X509v3 Subject Alternative Name: {'DNS': ['nodejs.org']}
• Certificate - Trust:
  Hostname Validation: OK - Subject Alternative Name matches
  "Mozilla NSS - 08/2014" CA Store: OK - Certificate is trusted
  "Microsoft - 08/2014" CA Store: OK - Certificate is trusted
  "Apple - OS X 10.9.4" CA Store: OK - Certificate is trusted
  "Java 6 - Update 65" CA Store: OK - Certificate is trusted
  Certificate Chain Received: ['nodejs.org', 'thawte DV SSL CA - G2', 'thawte Primary Root CA']
• Certificate - OCSP Stapling:
  NOT SUPPORTED - Server did not send back an OCSP response.
• SSLV2 Cipher Suites:
  Server rejected all cipher suites.
• Session Resumption:
  With Session IDs: NOT SUPPORTED (0 successful, 5 failed, 0 errors, 5 total attempts).
  With TLS Session Tickets: OK - Supported
• TLSV1_2 Cipher Suites:
  Server rejected all cipher suites.
• TLSV1_1 Cipher Suites:
  Server rejected all cipher suites.
• TLSV1 Cipher Suites:
  Preferred:
  DHE-RSA-AES256-SHA DH-1024 bits 256 bits HTTP 200 OK
  Accepted:
  DHE-RSA-AES256-SHA DH-1024 bits 256 bits HTTP 200 OK
  AES256-SHA - 256 bits HTTP 200 OK
  DHE-RSA-AES128-SHA DH-1024 bits 128 bits HTTP 200 OK
  AES128-SHA - 128 bits HTTP 200 OK
  EDH-RSA-DES-CBC3-SHA DH-1024 bits 112 bits HTTP 200 OK
  DES-CBC3-SHA - 112 bits HTTP 200 OK
• SSLV3 Cipher Suites:
  Preferred:
  DHE-RSA-AES256-SHA DH-1024 bits 256 bits HTTP 200 OK
  Accepted:
  DHE-RSA-AES256-SHA DH-1024 bits 256 bits HTTP 200 OK
  AES256-SHA - 256 bits HTTP 200 OK
  DHE-RSA-AES128-SHA DH-1024 bits 128 bits HTTP 200 OK
  AES128-SHA - 128 bits HTTP 200 OK
  EDH-RSA-DES-CBC3-SHA DH-1024 bits 112 bits HTTP 200 OK
  DES-CBC3-SHA - 112 bits HTTP 200 OK

Maybe this doc could help: https://bettercrypto.org/static/applied-crypto-hardening.pdf#subsection.2.1.3

I think many people would like the website to add a mailing list feature (not on Google Groups) in order to be notified of big events like software updates (especially those containing openssl updates). I really fear that there will be another "heartbleed". I now just check your website everyday, which is very inefficient.

The list of libraries maintained and managed by the Node.js team in the contributing page (https://nodejs.org/documentation/contributing/) still mentions libuv and the link still points to joyent's organisation (https://github.com/joyent/libuv) while it should point to the libuv one (https://github.com/libuv/libuv).

Just spotted a minor grammatical error in the updated footer: its vs. it's

Recently, I uploaded an outdated version of the website by running make release in my local repository without having pulled the master branch beforehand.

Luckily, it was easily fixed by pulling the master branch and running make website website-upload, but the problem is sometimes not obvious to notice.

It seems it could be handy if the website deployment process would prompt the user whenever what's deployed is not the tip of joyent/node-website's master branch.

On the footer of the http://www.nodejs.org/industry/ page, the "View license" links sends to https://raw.githubusercontent.com/joyent/node/__VERSION__/LICENSE , without an actual version number

On page http://nodejs.org/api/process.html there is no API stability information (see http://nodejs.org/api/child_process.html for a page having the stability information available)

I would like to create a web page that communicates more information about the Node.js Foundation and the status of the work to stand it up. I would like this to be linked from the home page of nodejs.org. Here is an introduction that I propose and some sections that can link to content that is being generated. Comments welcome.

Web page for Foundation

A group of organizations is coming together to create a neutral foundation for Node.js. The goal is to accelerate the development and adoption of Node through a community-driven, neutral steward. The foundation will have two organizations in it. The first is the Technical Steering Committee that will provide technical leadership of the project. The second is the Board of Directors that will provide services including funding, financial management, community development, marketing, and legal management. We strive to further the success of Node by delivering distinct value to the users of Node, creating a level playing field that supports a vibrant ecosystem of product and service vendors, and attracting and developing an energized community of contributors.

Sections:

Blogs

Overall work plan with dates

Overview deck

FAQ

Intro to Foundation Members

• Joyent
• IBM
• Microsoft
• Fidelity
• Apigee
• SAP
• PayPal

Foundation documents

• by-laws
• membership agreement
• TSC charter
• Governance docs

From nodejs/node-v0.x-archive#8517:

This's disaster. Words are not readable, can copy link to current page from browser address bar. Please revert you last changes.

Screenshot from FF32

Opening this issue for tracking. At Todd Benzies request, I am currently working to make a number of short-term updates to the website for the Foundation announce on 2015-06-16. These include:

1. Removing the "Sponsored by Joyent" branding on the various pages
2. Adding the usual Linux Foundation boilerplate header/footer
3. Adding the [email protected] and [email protected] contact points
4. Updating the Trademark Guidelines to reflect the Foundation's license to use the Node.js trademark
5. Adding an information request form for Foundation membership.
6. Updating the initial list of Foundation members.

These changes will need to go live on Tuesday, June 16th. However, as I'm going to be on vacation that day, I'll need someone else to actually review and land the changes. This is a time sensitive update and the actual list of Foundation members is confidential until the announce actually happens so the PR cannot be posted and landed until June 16th. I'll will open the PR Tuesday morning immediately before I head out the door.

/cc @joyent/node-collaborators @mikeal @misterdjules @rvagg @Fishrock123

http://nodejs.org/api/tracing.html

from: https://github.com/joyent/node-website/pull/72/files#r23943271

• do we have some informations regarding that in the repo?

this link returns:

{"code":"ResourceNotFound","message":"/html/nightlies.html"}

How can I rsync from http://nodejs.org/dist/ ?

Hey I don't know if folks pay attention to stuff like this, but the docs don't render right on Centos with Chrome or Firefox:

The first letters are getting obscured...

It appears to be the #column1.interior { width: 749px; }

If I change it locally to width: 740px it appears to fix everything.

placeholder information under util.format(format, [...]) on nodejs.org website API doc has
% - single percent sign
(http://nodejs.org/api/util.html#util_util_format_format)

Please fix it to match the correct information as shown in the node API markdown.
%% - single percent sign
(https://github.com/joyent/node/blob/master/doc/api/util.markdown)

from nodejs/node-v0.x-archive#4321:

following folders links form http://nodejs.org/docs/, like to http://nodejs.org/docs/latest/ or http://nodejs.org/docs/v0.8.15/

[actually] leads to http://nodejs.org/ homepage render

i presume there should be a redirect from /docs/:version/ to /docs/:version/api/

For instance, if you navigate here and click on any version folder greater than 0.8 or so, you are redirected to the full site. This might not end up being a huge issue, but it might be confusing for some.

All content on the node.js website should redirect to the https:// version - except everything at /dist/

We currently copy templates and slightly modify them in order to change the navigation items.

We already have some code for hightlighning in the footer: https://github.com/joyent/node-website/blob/master/doc/about/advisory-board/template.html#L102 we can add some other code for modifying the subpoints of the navigation.

Another solution would be to create a helper which would prebake all that in the basic markup automatically.

This affects currently the advisory board template in about and the core-team-page

see also #80

Relates to #36

When clicking View as JSON in any of the API documentation pages, the JSON data is not positioned correctly and it's hard to view as per the screenshot below.

I'm using Google Chrome v37.0.2062.122 on Mac OS X v10.9.2

I think the new Github ribbon is very ugly.

Hi there,
I'm on a Chrome 33 and this is how the website looks like:

Besides the already reported ugly ribbon #5, the "download" and "api" links are weird.

Currently, the blog is built in such a way that it requires elements from nodejs.org using a fully qualified domain name. These elements should instead be duplicated in the blog output folder so that they can be referred to with relative or absolute URLs specific to the subdomain in question.

This will help drastically with local testing when making design changes.

Hello,

I noticed nodejs.org's current design is not responsive. Has there been any discussion around making it responsive? I would be willing to help if you think this would be useful.

Zach

More details at nodejs/node-v0.x-archive#8907.

Seems the SSL certificate is not valid for the subdomain blog.nodejs.org

Example: https://blog.nodejs.org/2015/01/20/node-v0-11-15-unstable/

Hi,

This is a request to add nodeJSguru under the Learning section of Community page. There is a link to How To Node but this is not being maintained actively anymore. At nodeJSguru we intend to work on the learning side of node.js as well as build a community of practitioners with job boards and discussion forums. A link on nodejs.org would help us immensely.

Thanks.

I'm aware that there are many such web based REPLs out there, but would it not be fun to have a http://try.nodejs.org ❓

Update //CC @isaacs

Currently, the main site build script requires individual pages to be built. This should behave more like the blog build, that bases the content off markdown files that then use specific templates with support for embedding partials so the site build can be more DRY. Haml front matter in each page would be used to specify which template to use.

Bonus: allow Jade for the templates. Not essential.

I don't know if you updated the nodejs site, but it doesn't show all the information on mobile no more.

Raquel Vélez's list of beginner references at https://github.com/rockbot/node-for-beginners should be included in the community page at nodejs.org/community/ or elsewhere at nodejs.org.

I am currently testing the https redirects, and I am not sure if I spotted a bug in the current nginx.conf:

http://doc.nodejs.org/v0.10.3 redirects me to https://nodejs.org/docs/v0.10.3/ but it should be https://nodejs.org/docs/v0.10.3/api/

code: https://github.com/joyent/node-website/blob/master/conf/nginx.conf#L126-130

There is a major visibility error in the documentation page of the nodejs website, the div tag has been adjusted to the left and it is difficult for the users to read it, change the width from 749 px to 739px in style.css (line no:368).