Redesign website to show existing solution first and petition on the side

since on 29.11.2018 one of the major players in Serverless world started to support native Ruby (AWS Lambda)

I think the serverless-ruby.org website should serve more as an informative website to show existing solutions + petition on the side, rather than petition as the main website purpose

### Reasons

Back in March there was few hacky solutions to do FaaS now there is starting to be several solid ways for Ruby developer to do FaaS.

Once AWS introduce something, other providers will try to catch up quickly (e.g. Microsoft functions )

I still want to keep the petition but main topic of the website will be some resources with nice icons to technologies at the top and petition on the side.

### Plan:

* keep the petition but don't make it main theme of the website
* landing page will point to existing solutions with better descriptions and links to guides
* maybe even discussion forum ( :thinking: would you like this ? )

Start with the current website landing page and petition flow, then review how existing Ruby serverless solutions and guides are presented. Done means the landing page leads with informative solution links and descriptions, while the petition remains available as a secondary element.

Written by the indexing model from the issue text.