Create project website

[wagoodman]

We have started to outpace the simple "all documentation goes in the README.md" approach that we take today. We should create a website that encompasses at least:

• installation
• basic usage
• document use cases
• document of configuration options
• integration examples and links
• links to communication (slack / issues)
• details on our bi-weekly community meeting
• high-level roadmap

We should leave / reserve CONTRIBUTING.md, RELEASE.md, and DEVELOPING.md (in-progress) outside of the site (in the root of the repo).

[joshbressers]

I've added this as a good first issue. A newcomer to the project doesn't need to write all of this, but any documentation written is always a great introduction to the project and would be hugely useful to the community

[sudovishal]

is this still an active issue? What exactly is the task? You need a Whole website containing all those points above mentioned?