Lots of bugs

1. Link to the website in the README
2. the background image on the blog has a white line, looks bad
3. the font in the header for NW.js looks terrible, either change it to something better, or use this image
4. Implement a "Quick Start" page, like this
5. On the blog page there is a a white center background. On the Downloads page it is missing.
6. In your package.json have a postinstall that runs bower install this will remove a step in the instructions (#24)
7. To run the site locally you should only have to do npm install and npm start. This is pretty standard practice now. (#25)
8. The footer on the Downloads page doesn't reach the bottom of the screen. Looks bad
9. Release an API for others to use for releases and downloads. Something like this.
10. Search on the documentation flat out doesn't work.
11. Stop using Metal smith and handlebars and just use regular old HTML/CSS/JS and I'll fix your entire site. I already did it once, that framework is just too ugly to bother looking at. Your site has stagnated because you've limited access to working on it to the 3 people who would ever want to use that set up. Keep it simple.

Add additional pages like:

• "Showcase" or "Spotlight" to show apps that have been made with NW.js
• "Tutorials" or "References" for links to NW.js specific videos, blogs, books, libraries, frameworks, boiler plates.
• "About" page. A few paragraphs about the people working on the project.
• "History" page. A full history of the project, how it started and all the changes it's gone through along the way.
• "FAQ": The most important Frequently Asked Questions.

Split the request into focused issues before starting, then inspect the README, package.json, blog, Downloads page, documentation search, and the referenced API example. There is no single completion condition here; each extracted issue should define its own pages, behavior, and acceptance criteria.