Setup docs to avoid bloating README

[mfridman]

I like this docs theme which works well with hugo.

https://getdoks.org/

[mfridman]

Other alternatives are:

• https://docusaurus.io/
• https://squidfunk.github.io/mkdocs-material/ (a material design theme for MkDocs

Going to evaluate some of these and send a PR. It'll be nice to have docs for goose to document:

• commands
• gotchas
• FAQ
• examples

[mfridman]

Tentatively setting up mkdocs - material. It's the easiest solution, looks great, is extensible, and has a good lighthouse score:

Docs found here (WIP): http://pressly.github.io/goose/

@VojtechVitek I have limited access to Settings. Can you flip the HTTPS?

https://docs.github.com/en/pages/getting-started-with-github-pages/securing-your-github-pages-site-with-https#enforcing-https-for-your-github-pages-site

[mfridman]

Add this example to docs. #176

[mfridman]

Add this answer to the docs. Mention it is specific to postgres:

#191 (comment)

[VojtechVitek]

@mfridman I'm sorry, first time I see these comments. Can you reach out on Golang Slack please?

[mfridman]

All good @VojtechVitek , asynchronous works 😄

The reason for a separate docs site is to capture the long-form items we've come across. I get asked about certain goose features and best practices, so just want to point at something.

[mfridman]

This is done. docs are live and can be found here...

https://pressly.github.io/goose/

wip, but we're iterating :)