Offer to help with the website

[amirmohsen]

Hey, I've started using nw.js and really enjoying it. I think the website definitely needs more work, but is probably low on your priorities. So if you are open to help, I am willing to help out with the website in any way I can. Let me know.

[dcohenb]

Hi Amir
Your help would be much appreciated
please take a look at the dev branch of the website. you can find there the design we are working on and the pages that are missing.
feel free to sumbit pull request for review

[amirmohsen]

Alright cool. Will do.

[amirmohsen]

Is the node server only for dev purposes or are you actually using it on the live server? The reason I ask is that it can definitely benefit from some improvements but I'll only spend the time on it if you are actually using it on the live server.

[dcohenb]

Yes it is used for Dev purposes. The idea was to make a builder that will
generate static HTML for simple static file server
On Mar 30, 2015 10:29 PM, "Amir Mohsen Abdolrazaghi" <
notifications@github.com> wrote:

Is the node server only for dev purposes or are you actually using it on
the live server? The reason I ask is that it can definitely benefit from
some improvements but I'll only spend the time on it if you are actually
using it on the live server.

—
Reply to this email directly or view it on GitHub
#8 (comment).

[amirmohsen]

Alright.

[amirmohsen]

So if we just want a static file generator, wouldn't it be easier to have a gulp task running with a watch? And on our dev machines, we can just run a simple static server like this one: https://www.npmjs.com/package/http-server
It also means you don't have to bother with manual routing. I just feel like a whole express application is a bit of a waste in this case. What do you think? Are you open to that idea?

[dcohenb]

A gulp task watcher could take a long time to generate all the pages on
every change
We wanted to take advantage of the ejs templating for quicker dev
On Mar 30, 2015 10:57 PM, "Amir Mohsen Abdolrazaghi" <
notifications@github.com> wrote:

So if we just want a static file generator, wouldn't it be easier to have
a gulp task running with a watch? And on our dev machines, we can just run
a simple static server like this one:
https://www.npmjs.com/package/http-server
It also means you don't have to bother with manual routing. I just feel
like a whole express application is a bit of a waste in this case. What do
you think? Are you open to that idea?

—
Reply to this email directly or view it on GitHub
#8 (comment).

[amirmohsen]

Well, a watch returns only the file that has changed so no need to regen all files on every change. In any case, the current server.js file doesn't actually generate any static files. It's just serving them. Or is there a plan to actually add the builder to it later? Sorry if I'm asking way too many questions. I just need to make sure what needs to be done so I don't end up wasting my time.

[dcohenb]

Yes, like I said before:
"The idea was to make a builder that will generate static HTML for simple
static file server"
But if you have a good idea and you wanna run with please go ahead
On Mar 30, 2015 11:14 PM, "Amir Mohsen Abdolrazaghi" <
notifications@github.com> wrote:

Well, a watch returns only the file that has changed so no need to regen
all files on every change. In any case, the current server.js file doesn't
actually generate any static files. It's just serving them. Or is there a
plan to actually add the builder to it later? Sorry if I'm asking way too
many questions. I just need to make sure what needs to be done so I don't
end up wasting my time.

—
Reply to this email directly or view it on GitHub
#8 (comment).

[amirmohsen]

Right. Gotcha!

[therebelrobot]

I'd love to chip in too! @amirmohsen @dcohenb, is there anything I can do to get the site up and running?

[rogerwang]

@therebelrobot I'm happy that you'd like to help. The core idea is that we can just writing blogs or update website by pushing to this repo. The rest is done automatically. I think nodejs.org is working like this and they open sourced their site fyi.

[samarsault]

I would love to contribute too !!

And if the idea is using a static file server, I would suggest trying jekyll. It can be hosted directly from github-pages with a custom domain. It supports liquid templates and is blog-ready.

Like, check http://samarjeet27.github.io/website for a demo and the gh-pages branch for the code.

[dcohenb]

@samarjeet27 is right, jekyll seems like the way to go

[samarsault]

@dcohenb should I submit a pull ? On which branch ?