Build quiverjs.org with Quiver

[soareschen]

Right now quiverjs.org redirects to this GitHub repository. I don't want to build a website for Quiver yet, because currently Quiver is still too low-level to build a full website.

The base Quiver component system has been completed. With that users can easily create handlers to serve HTTP requests, but that is the same as being able to write a HTTP handler in Node. To build a website user still have to go through the process of implementing the entire website on their own.

I can of course build a website quickly using Quiver now, but the result code would likely look similar to the typical Node.js code we have today. The website code would not be elegant and is full of boilerplate code that is non-reusable.

One of Quiver's philosophy is to build websites with reusable components. In other words I should not only can build a website by writing my own components, but also build a website by simply recombining other people's components. And whatever components I have implemented for one website should easily be reused when building another website.

Following that philosophy is much harder than simply writing a monolithic website with bunch of hardly-reusable Quiver components, at least for now. I don't want to show bad example to people with an official website full of crappy code. That's why I am not building a website with Quiver until the core components are implement.

Once Core components such as templating (#5), authentication (#6), and client-side asset compilation(#7) are completed, building websites should be much easier by then. At that point only we can start to build an official website for Quiver.