Mkdocs setup

[meatballhat]

What type of PR is this?

• cleanup
• documentation

What this PR does / why we need it:

Adds initial mkdocs material configuration and index doc so that a docs site may be hosted via GitHub Pages.

Which issue(s) this PR fixes:

Fixes #1343
Fixes #1380

Special notes for your reviewer:

There was some mention in #1343 about possibly using docusaurus, but I threw this together given that other maintainers are either already familiar with mkdocs or prefer it to docusaurus.

[meatballhat]

FYI out of band I've enabled GitHub Pages and added a CNAME record of:

cli.urfave.org. 3600 IN CNAME urfave.github.io.

[saintmalik]

FYI out of band I've enabled GitHub Pages and added a CNAME record of:

cli.urfave.org. 3600 IN CNAME urfave.github.io.

Great, nice, sorry it took me some days to respond, can i help out also?

[saintmalik]

Also noticed something: the pen editing button leads to a 404 page at the moment.

https://github.com/urvafe/cli/edit/main/docs/v2/index.md

[meatballhat]

@saintmalik What do you think of this PR? Reasonable enough as a first attempt?

[saintmalik]

Yeah, its pretty awesome, and makes life easy for everyone

[kolyshkin]

Hint: if you use git pull --rebase you can get rid of merge commits.

[meatballhat]

Hint: if you use git pull --rebase you can get rid of merge commits.

@kolyshkin yep I'm aware 😁 I realize the whole merge/rebase debate has a long history that I definitely don't want to engage in here. Suffice to say I'm in favor of adapting my preferences to what works for fellow contributors. Any chance you're up for opening a discussion if you'd like to see a rebase-centric set of workflows and norms?