Create website

[pledbrook]

We should create a simple website for Lazybones with:

• A short description of what it is
• Perhaps a short screencast showing it in use
• Links to documentation
  • Getting started
  • Creating templates
• Details of how to contribute

[tbarker9]

This could be a ratpack site! Might as well pay homage to lazybone's origins.

[pledbrook]

Aye. @ldaley is also looking for a sample Ratpack site using AngularJS and MongoDB. Not sure if there is a use for MongoDB in this case, but it may be handy for a project template listing.

On the AngularJS front, that's something I'm interested in learning about, but I'm wondering whether it degrades nicely to a static HTML site if JS is disabled (for example). @robfletcher does it work like that?

[robfletcher]

It very much depends what you want to do with it but I'm inclined to think that anything that justifies the use of Angular is unlikely to degrade particularly well.

[tbarker9]

Since we are using static stuff for the website maybe we should just use git pages. I like the idea of using ratpack mind you... kind of demonstrates that we eat what we make (or whatever that phrase is), but might be easier to get contributions if we use git pages.

[cjstehno]

JBake and GitHub Pages play really nice together for static project information sites - Baking Your Blog with JBake, Groovy and GitHub. I'd be willing to take an initial stab at a site unless you know of someone else already working on it.

[cjstehno]

I have a simple starting point site implemented as a sub-project using JBake. I am on the fence about whether or not the site should build with the overall build or only when specifically requested. I am leaning towards having the site be outside the normal overall build... any thoughts or preferences? Publishing, would of course, require specific action.

[pledbrook]

I would give the site project a build target that generates the HTML, but I wouldn't link it to any of the other projects.