Hey @nirvdrum,

We had talked in Atlanta on heading up a docs reorg / rewrite and creating a blog.

We can do that pretty easily with jekyll and in this repo. Thoughts on how we should tackle this?

/Nat

/cc @geemus

While working on #56 I discovered a lot of noise in the jekyll output, because js files not being referenced correctly in subdirectories. I haven't looked at what they do (one of them has an html comment "remove in production -- I don't use yui, so don't know what this implications are).

This occurs on github pages, e.g. console snap from http://fog.io/about/getting_started.html

But console is emtpy on http://fog.io/

Currently inline codeblocks are being rendered as blocks:

from: http://fog.io/about/getting_started.html#credentials

Re: fog/fog#3405 - I noticed the OpenVZ is missing at http://fog.io/about/provider_documentation.html.

What are your requirements for documentation? I didn't build the driver - @jedi4ever did - but I can quite believe Patrick is extremely busy and that this may not be a priority for him.

I don't have any experience with fog.io, and not much with OpenVZ. What's the minimum I need to do to get the documentation to an acceptable point as a PR?

I suppose just adding OpenVZ to that matrix is a start, but would that suffice?

Thanks kindly,
Martin.

Per discussion in fog/fog#3504, contributing guidelines should move from fog.io to the CONTRIBUTING.md guide in the GitHub repository, with a reference to that document on fog.io.

Right now the footer on http://fog.io has this,

Home
Contributing
Press
Supported Services
Users

The "users" link redirects to a page of projects using fog. I think it would be more accurate to change Users to Projects using Fog.

Home
Contributing
Press
Supported Services
Projects user Fog

Get a suggestion.

Hi, please see my comment on

fog/fog@61ff93a

I'm more than happy to submit a pull request with changes to the Storage page that adds endpoint to the options hash as described in the comment. Being relatively new to the game, thought I would raise an issue first and ask whether this is appropriate.