<!doctype html>
< html >
< head >
< meta charset = "utf-8" >
< style >
ul {
padding: 0;
margin: 0;
}
< / style >
< script src = "../sh_main.js" > < / script >
< script src = "../sh_javascript.min.js" > < / script >
< link type = "image/x-icon" rel = "icon" href = "../favicon.ico" >
< link type = "image/x-icon" rel = "shortcut icon" href = "../favicon.ico" >
< link type = "text/css" rel = "stylesheet" href = "../pipe.css" >
< link type = "text/css" rel = "stylesheet" href = "../sh_vim-dark.css" >
< link rel = "alternate"
type="application/rss+xml"
title="node blog"
href="http://feeds.feedburner.com/nodejs/123123123">
< title > node.js< / title >
< / head >
< body >
< div id = "intro" >
< a href = "/" title = "Go back to the home page" >
< img id = "logo" src = "../logo.png" alt = "node.js" >
< / a >
< / div >
< div id = "content" class = "clearfix" >
< div id = "column1" class = "interior" >
< p > Node's most valuable feature is the friendly and colorful community of developers. There are many places where this group congregates on the internet. This page attempts to highlight the best forums.< / p >
< h2 > Periodicals< / h2 >
< p > < a
href="http://planetnodejs.com">Planet Node< / a > is an
aggregator of Node developer blogs. < a
href="http://nodeup.com/">NodeUp< / a >
is a podcast covering the latest Node news in the
community. < / p >
< h2 > Docs< / h2 >
< p >
Besides the < a href = "http://nodejs.org/docs/latest/api" > official API
docs< / a > there are a number of sites new users should be
aware of. < A href = "http://docs.nodejitsu.com/" > docs.nodejitsu.com< / A >
answers many of the common problems people come across.
< a href = "http://howtonode.org/" > How To Node< / a > has a
growing number of useful tutorials.
The < a href = "http://stackoverflow.com/questions/tagged/node.js" > Stack
Overflow node.js tag< / a > is collecting new information
every day.
< h2 > GitHub< / h2 >
< p > All development takes place at < a
href="http://github.com/joyent/node">http://github.com/joyent/node< / a > .
The comments on commit messages are often source of heated
discussion regarding core development. The < a
href="http://github.com/joyent/node/wiki">GitHub Node
wiki< / a > is full of useful links for newcomers. Don't
miss < a
href="https://github.com/joyent/node/wiki/Projects,-Applications,-and-Companies-Using-Node">Projects,
Applications, and Companies Using Node< / a > or the < a
href="https://github.com/joyent/node/wiki/modules">very
long list of Node modules< / a > , many of which are
published in the < a href = "http://search.npmjs.org/" > npm
registry< / a > .< / p >
< p > < a href = "http://notinventedhe.re/on/2011-7-26" > < img
src="not-invented-here.png" width="100%">< / a > Bugs
should be reported to < a
href="https://github.com/joyent/node/issues">https://github.com/joyent/node/issues< / a > .
Fixes to the code are welcome! Please see our < a
href="https://github.com/joyent/node/wiki/Contributing">contirbuting
guidelines< / a > for information on how to submit a
patch.< / p >
< h2 > Mailing Lists< / h2 >
< p > The < a
href="http://groups.google.com/group/nodejs">user
mailing list< / a > is used for announcements, discussion,
and flame wars about Node. The < a
href="http://groups.google.com/group/nodejs-dev">internal
development mailing list< / a > is used for discussion of
internal design and feature proposals.< / p >
< h2 > IRC< / h2 >
< p > For real-time chat about Node development go to
< code > irc.freenode.net< / code > in the < code > #node.js< / code >
channel with an < a href = "http://www.mirc.com" > IRC< / a > < a
href="http://colloquy.info/">client< / a > or connect in
your web browser to the channel using < a
href="http://webchat.freenode.net/?channels=node.js">freenode's
WebChat< / a > . Felix Geisendörfer keeps < a
href="http://nodejs.debuggable.com/">logs of the
channel< / a > for those who miss a day.< / p >
< h2 > Conferences< / h2 >
< p > < a href = "http://www.nodeconf.com/" > NodeConf< / a >
conferences are the main event in the United States; they
are organized by < a href = "http://www.mikealrogers.com/" > Mikeal Rogers< / a > .
< a href = "http://nodefest.jp/" > NodeFest (東京Node学園祭)< / a >
is organized by the < a href = "http://nodejs.jp" > Node.js
Japan user group< / a > . < a
href="http://nodecamp.de/">NodeCamp.de< / a > in Cologne,
Germany is organized by < a href = "railslove.de" > Rails
Love< / a > . An < a href = "http://nodejsconf.it/" > Italian
Node.js Conference< / a > exists as well. < a
href="http://nodesummit.com/">Node Summit< / a > is a
conference in San Francisco focusing on the adoption of
Node in larger companies. < a
href="http://jsconf.com/">JSConf< / a > organizes the main
JavaScript conferences.< / p >
< h2 > Localized Sites< / h2 >
< p > < code > nodejs.org< / code > does not maintain any
translations into other languages. However there are
community websites in various languages with mailing lists
and translations of the website.< / p >
< p > < a href = "http://nodejs.ru/" > nodejs.ru< / a > Russian blog.
< br >
< a href = "http://nodejs.ir" > nodejs.ir< / a > Iran group in Persian
< br >
< a href = "http://nodejs.jp/" > nodejs.jp< / a > Japan user group
< br >
< a href = "http://cnodejs.org" > CNodeJS.org< / a > Chinese community
< br >
< a href = "http://nodejs.co.il" > nodejs.co.il< / a > Israeli wiki
< br >
< a href = "http://nodejs.hk" > HKNoJ< / a > Hong Kong community
< br >
< a href = "http://nodejs.tw" > nodejs.tw< / a > Taiwan community< / p >
< p > < a href = "/" > Go back to the home page< / a > < / p >
< / div >
< div id = "column2" class = "interior" >
< / div >
< / div >
< div id = "footer" >
< p > Copyright < a href = "http://joyent.com" > Joyent, Inc< / a > , Node.js
is a < a href = "trademark-policy.pdf" > trademark of Joyent, Inc< / a > .
< / div >
< script >
var gaJsHost = (("https:" == document.location.protocol) ?
"https://ssl." : "http://www.");
document.write(unescape("%3Cscript src='" + gaJsHost + "google-analytics.com/ga.js' type='text/javascript'%3E%3C/script%3E"));
< / script >
< script >
try {
var pageTracker = _gat._getTracker("UA-10874194-2");
pageTracker._trackPageview();
} catch(err) {}
< / script >
< / body >
< / html >
