NodeCookbook.com

[Alex Brown]

anyone interested int these domain names?  I purchased them but have no time to do anything with them.

nodecookbook.com

nodecookbook.net

nodecookbook.org

They expire on 11/12/2011

I don't remember what it cost to register them and I don't know what it costs to transfer them. I'll accept any offer from "Give them to me now!" to "Here's a million dollars go retire."

[Stephen Belanger]

I'd offer you a million dollars, but I haven't beat Facebook yet. ;)

As I recall, TJ had started a node cookbook of sorts, perhaps he'll be interested. If not, I could host it myself.

--
You received this message because you are subscribed to the Google Groups "nodejs" group.
To post to this group, send email to nod...@googlegroups.com.
To unsubscribe from this group, send email to nodejs+un...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/nodejs?hl=en.

[Mikeal Rogers]

we're still breaking the API a lot, a some libraries that seem quite popular could be abandoned or pushed aside for new ones.

it's really early in the lifecycle of node and *any* documentation project is going to bear a heavy burden staying up to date.

[Stephen Belanger]

Well, sites like howtonode.org exist regardless. It can definitely be a challenge keeping up, but I think these kinds of resources are valuable and someone will have to carry the burden eventually. If no one else wants the task, I might take it. I eat-sleep-breathe node, so I've already got my head in the water anyway.

On Fri, Apr 8, 2011 at 10:22 AM, Mikeal Rogers <mikeal...@gmail.com> wrote:

we're still breaking the API a lot, a some libraries that seem quite popular could be abandoned or pushed aside for new ones.

it's really early in the lifecycle of node and *any* documentation project is going to bear a heavy burden staying up to date.

--

[Diogo Resende]

One of this domains would be perfect for a documentation project where
the node API could stay. Interesting would be other module developers
being able to post documentation too (moderated perhaps..).

[John Taber]

I think it's very much needed to strengthen the node user community - especially if easy to contribute and modify (I'm happy to contribute but not offended if others change my submissions for a better solution) - if api breaks well, if easy to modify then it just gets changed as necessary

1st step would be to pick a doc format - wiki ? 
2nd - outline some categories perhaps: db, server/sockets, ....
@stephan - please take the plunge of establishing it - then hopefully myself and others just start contributing

my vote for someone to contribute: how to: create a https login (with node as server)

ps: culling some posts on this list and stackoverflow would already provide a bunch of recipes

[Stephen Belanger]

Well, I'm currently working on an as-yet direction-less MVC framework. Perhaps this would be a good test for it. It has social login via Facebook, Twitter and LinkedIn, so perhaps I could use that to make it easily accessible while also helping to identify people that want to join as contributors. Adding Github OAuth would be even better. :)

What do you think of allowing any existing contributor to approve new ones? It'd allow it to grow relatively safely without too much admin burden on a select few people.

I'm seriously considering this, so if you have any great ideas on how this should work let me know.

[Alex Brown]

It's up to whoever takes them. I don't have the time to develop the site that was in my head so instead of sitting on the domains I figured I would give them to someone with spare time ;)

[Stephen Belanger]

Well, I don't have any money at the moment, but if no one else makes an offer I'll take them. :)

[phidelta]

How about this offer:

Keep them (I'll pick up the tab) and throw in a years low-end hosting.
Then we setup a wiki there and try to get an actual node-cookbook
started.

After that we'll see what we have a year from now and take it from
there. I do think that a better documentation site with examples, as
well as a better interface to list/search/view NPM packages would be a
good thing.

Regards, Philipp

[Stephen Belanger]

I've decided I am going to make a site for that, but I'm building it off a half-done system at the moment, so it's not going to be launching tomorrow. ;)

I might have something to show in a week or something like that. I'll be open sourcing the CouchDB ORM I'm making for it though, which should hopefully be done tomorrow.

[Diogo Resende]

On Sat, Apr 9, 2011 at 9:37 AM, Stephen Belanger <cyruz...@gmail.com> wrote:
> I've decided I am going to make a site for that, but I'm building it off a
> half-done system at the moment, so it's not going to be launching tomorrow.
> ;)
> I might have something to show in a week or something like that. I'll be
> open sourcing the CouchDB ORM I'm making for it though, which should
> hopefully be done tomorrow.

If you need any help, I'm available.

[Alex Brown]

I can do that. I don't mind paying for hosting or keeping up the domains I just don't have time to write articles or keep up with node. 

Which version of wiki would be a good one to use?

[Diogo Resende]

I think any wiki is good for now :)

[Guy Halford-Thompson]

MediaWiki?

On 11 April 2011 10:45, Diogo Resende <dio...@gmail.com> wrote:
> I think any wiki is good for now :)
>

> --
> You received this message because you are subscribed to the Google Groups "nodejs" group.
> To post to this group, send email to nod...@googlegroups.com.
> To unsubscribe from this group, send email to nodejs+un...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/nodejs?hl=en.
>
>

--
Guy Halford-Thompson - http://www.cach.me/blog

[Diogo Resende]

On Mon, Apr 11, 2011 at 2:41 PM, Guy Halford-Thompson <g...@cach.me> wrote:
> MediaWiki?

I think any wiki would be great. The only thing I think would be best
appropriate would be to have Markdown syntax (for simpler import from
github).

[Stephen Belanger]

+1 for Markdown, even though I hate it. >.>

--

[John Taber]

On 04/11/2011 11:32 AM, Stephen Belanger wrote:

+1 for Markdown, even though I hate it. >.>

good suggestion - I think markdown even makes more sense than wiki since it allows for easier submission.  Did the hosting thing get resolved so we can start submitting recipes ? 

[Morteza Milani]

Hi,

I'm working on a wiki project for node. I used Express as web framework, and Git as file storage. It supports file history tracking, github-twitter-google authentication and it will have a great user interface.

If you like, I can publish it on Github, so anyone interested can collaborate on it. and we can put it on this domains you offered. The benefit are:

1) written on Nodejs.
2) Database is not required.
3) Good interface for programmers ( take a look and get what you want! )
4) It will be easy to develop it later to support new features.

If you want the code, I can publish it ( I didn't do that because it is not in a state easy to understand what's going on, But I can do this in a few hours with a little documentation ).

Cheers!

[Bradley Meck]

I see docuwiki is up on nodecookbook, is it going to stay that way (and can we get markdown). If it is we can start writing stuff.

[Chad Eubanks]

Hi,

Check out guides.sproutcore.com.  We just started to use this with the SC Community and it has helped out greatly.  Perhaps we the Node community can start the motion for a guidelines project.

Thoughts?

Kind Regards,

Chad Eubanks

The Code Boutique

Sent from my iPad

On Apr 13, 2011, at 7:35 AM, Bradley Meck <bradle...@gmail.com> wrote:

I see docuwiki is up on nodecookbook, is it going to stay that way (and can we get markdown). If it is we can start writing stuff.

--

[Alex Brown]

I have put dokuwiki on nodecookbook.com. I've added the markdown plugin. Someone try it out and let me know if you can add pages.

[Alex Brown]

I changed the template to monobook. Let me know if there is a better template.

[mscdex]

On Apr 13, 6:58 pm, Alex Brown <abrow...@gmail.com> wrote:
> I changed the template to monobook. Let me know if there is a better
> template.

I'm curious, why is the modules list on the github wiki starting to be
duplicated here: http://nodecookbook.com/doku.php?id=protocols ?

[Bradley Meck]

those are going to be step by step tutorials on using them, rather than a listing. i havent had time to start pumping in code w/ explanations yet.