Storaged.org website rework

[vojtechtrefny]

This contains a blog (I added the latest blogpost from our old blog) and a simple site for each project. This also contains documentation from all projects so the existing gh-pages branches from libblockdev, blivet etc. will be removed after merging this and documentation updates will go through this project in the future.

See GH pages documentation for details how to test this locally.

Few screenshots:

[tbzatek]

I've got pretty hard time getting Jekyll to work, broken dependencies on two distros. This will be a nightmare to maintain.

[vojtechtrefny]

I've got pretty hard time getting Jekyll to work, broken dependencies on two distros. This will be a nightmare to maintain.

I hope we won't maintain it at all -- for us this should be just writing some markdown and hoping that everything automagically works on the GH side. So far, it seems to be working fine for other people.

[tbzatek]

Made it working locally at last. First thoughts:

• the root page shows blog only, I would prefer - in addition to the blog posts - at least have some introductory section above the blog posts - something about the "Storaged project" mission, just a few sentences and a list of projects in the group. Perhaps the first one or first two sentences of each project section?
• is it supposed to be "Storaged" or "storaged" or "StorageD" ?
• the UDisks page should mention its roots in the GNOME project, it is still our primary user through gvfs which contains lots of additional logic that is closely tied to UDisks logic - after all it was developed together by the original author. I like the paragraph on the current website (just replace Storaged with udisks):

The code has its origins in the [udisk](https://www.freedesktop.org/wiki/Software/udisks/) project which is being developed for the GNOME desktop environment needs. The focus of the Storaged is the D-Bus API suitable for wider audience than just the desktop applications.

• I would like to emphasise that libblockdev is a stateless API while blivet and udisks are stateful services
• UDisks primarily provides a daemon exposed by a D-Bus API and it should be emphasised - many users are facing udisksctl only and that in fact is just a small convenient tool with not utmost importance
• perhaps we shall revamp READMEs in the projects along with it?
• udiskctl --> udisksctl
• shall we highlight licenses of each project?

[vojtechtrefny]

Made it working locally at last. First thoughts:

* the root page shows blog only, I would prefer - in addition to the blog posts - at least have some introductory section above the blog posts - something about the "Storaged project" mission, just a few sentences and a list of projects in the group. Perhaps the first one or first two sentences of each project section?

The layout of the front page is limited by the theme. The short paragraph at the bottom is the best I can do without changing the theme. It is possible to adjust the theme, but that means more work.

* is it supposed to be "Storaged" or "storaged" or "StorageD" ?

No idea.

* the UDisks page should mention its roots in the GNOME project, it is still our primary user through gvfs which contains lots of additional logic that is closely tied to UDisks logic - after all it was developed together by the original author. I like the paragraph on the current website (just replace Storaged with udisks):

The code has its origins in the [udisk](https://www.freedesktop.org/wiki/Software/udisks/) project which is being developed for the GNOME desktop environment needs. The focus of the Storaged is the D-Bus API suitable for wider audience than just the desktop applications.

* I would like to emphasise that libblockdev is a stateless API while blivet and udisks are stateful services

* UDisks primarily provides a daemon exposed by a D-Bus API and it should be emphasised - many users are facing `udisksctl` only and that in fact is just a small convenient tool with not utmost importance

* perhaps we shall revamp READMEs in the projects along with it?

* _udiskctl_ --> _udisksctl_

If you agree, I'd merge this initial version and start changes like these in a separate PR. For the initial version, I just took the descriptions from our existing website and/or READMEs. It would be easier to make the changes (and review them) without all the other changes around.