Node.js has a new website(nodejs.org)
nodejs.org
Node.js has a new website
http://nodejs.org
13 comments
the code blocks on the front are kinda painful to read, they need some padding/margin and/or border to differentiate them between the paragraphs, the rest is nice though!
Ugh, this design sucks.
I like the colors :D
Font is too small.
The missing left hand nav kindof stinks.
Yeah... the fact that the only navigation links, aside from download, are below the fold completely destroys the usability of the site.
It's not a website. It's a landing page for people who are looking into node.js.
Huh? It has links to documentation, about, jobs, a blog... that seems like a website to me. Moreover, what use is a "landing page" for a technical tool that doesn't immediately get you the information you need to actually use it?
I don't really understand the value in the distinction you're trying to make.
I don't really understand the value in the distinction you're trying to make.
I think that is a bit of a misnomer. A landing page is like this - http://files.www.newmediacampaigns.com/posts/randoms/netflix...
IE a (typically) single page, completly above the fold, alternative to the official page of the site used as the page people see when they come via an ad or offer.
This is just a typical homepage for a computer language (listing accolades, testimonials, downloads, hello world, etc). It is much more featured filled than a landing page.
It just has poorer navigation than before.
IE a (typically) single page, completly above the fold, alternative to the official page of the site used as the page people see when they come via an ad or offer.
This is just a typical homepage for a computer language (listing accolades, testimonials, downloads, hello world, etc). It is much more featured filled than a landing page.
It just has poorer navigation than before.
a minor rant but it would've been nice to see blog.nodejs.org powered by nodejs
A blog engine is the type of CRUD app that node is not well suited for. Just because they could write it in node, doesn't mean that they should.
Why wouldn't node be suited for a "CRUD app"? I think it's not using node simply because what they have already works perfectly fine, there's no need to change it to a node powered system. Most of the main developers are also concentrating on actually developing node and probably have no time to do the switch.
"""Why wouldn't node be suited for a "CRUD app"? """
Because all the design decisions for node.js weren't about making CRUD apps.
Because all the design decisions for node.js weren't about making CRUD apps.
I'm just wondering what design decisions exactly? How is Express or the other node.js frameworks any different from building an MVC app in Flask or some other conventionless framework?
It's a solved problem. No need to reinvent the wheel in node.js. My company has also recently dropped our custom blog (C#) and are going with WordPress (PHP).
Great! Now everybody who wants to have information about Node.js has to scroll a shit load down and search for an oddly placed menubar on the right side..
Because who would expect a menubar with vital information such as docs above the fold?
But at least it's more visually attractive then the last version.
Because who would expect a menubar with vital information such as docs above the fold?
But at least it's more visually attractive then the last version.
Not related to redesign (or is it?) but it would seem Microsoft is showing surprising interest to node.
Not too surprising; given Microsoft's recent crush on JavaScript. W8 will allow for first-class JS desktop apps; only makes sense to enable JS on the server at well. Using node vs. some sort of Chakra-based system is a bit surprising given MS's history; but "embracing" node now is easier than trying to convert existing node devs to something totally new (or risking newly-minted desktop JS devs using *nix servers)
Exactly, historically MS suffered from bad case of not-invented-here syndrome, so that they embrace google's V8 is what's surprising. It's good for everyone though, kudos to MS.
I liked it when the 6-line web server code was the first thing you saw. This is what originally sucked me in to node.js. You think, "Woah! A web server in JavaScript, and it's that simple."
I guess I can scroll down to the docs, but it would be nice if nodejs.org/docs redirected to the most recent version and linked to older ones. A memorable URL for docs is nice. e.g. docs.jquery.com
When I go to a new project's site I want to see: 1. An example. 2. Getting Started. 3. Full Docs.
"In the industry" is not really the first thing I need to know. That's something that's nice to see, and belongs more at the bottom of the homepage, IMO.
I guess I can scroll down to the docs, but it would be nice if nodejs.org/docs redirected to the most recent version and linked to older ones. A memorable URL for docs is nice. e.g. docs.jquery.com
When I go to a new project's site I want to see: 1. An example. 2. Getting Started. 3. Full Docs.
"In the industry" is not really the first thing I need to know. That's something that's nice to see, and belongs more at the bottom of the homepage, IMO.
I think the "In the industry" sections shows the user that Node is something awesome and stable, which is reassuring to new developers. Chances are if you're hitting the homepage you're a new-comer to Node, existing developers may be likely first hitting the site in the API docs from a Google search.
I think it would be beneficial to spend more time answering the questions "What is Node?", "Why would I want to use it?" on the front page than using so much of it to feature social proof from Microsoft et al first.
I've followed node since it was announced but I still found myself searching the entire page to find an FAQs/About Us section. It was harder than it should be.
just my 2c
I've followed node since it was announced but I still found myself searching the entire page to find an FAQs/About Us section. It was harder than it should be.
just my 2c
They should move the "NODE.JS IN THE INDUSTRY" section to the bottom.
The old website was as beautiful and simple as nodejs itself. There was a code example on the front page, near the top, which seemed to say: "once you see it, you'll love it."
The new website seems overly proud of big name users. I guess this is Joyent's marketing department at work.
The old website was as beautiful and simple as nodejs itself. There was a code example on the front page, near the top, which seemed to say: "once you see it, you'll love it."
The new website seems overly proud of big name users. I guess this is Joyent's marketing department at work.
UX could be improved by not using small dark text on a dark background and a main navigation below the fold on the right side.
The site seems to be catering to two completely different audiences. There's the corporate deciders who will be reassured by the "social proof" logos of Microsoft et al. And there's the 1337 script kiddies who will feel at home with an unreadable color scheme. It seems like many node.js-related sites have this type of unusable color scheme, much like the Flash sites of yesteryear.
The site seems to be catering to two completely different audiences. There's the corporate deciders who will be reassured by the "social proof" logos of Microsoft et al. And there's the 1337 script kiddies who will feel at home with an unreadable color scheme. It seems like many node.js-related sites have this type of unusable color scheme, much like the Flash sites of yesteryear.