Add versioning to the docs

[artberger]

Addresses #422

Working locally based off my fork in Netlify here: https://app.netlify.com/projects/adb-inf-extension/deploys

The docs are versioned using a MkDocs plug-in called mike (GitHub project here). They are put on a docs branch.

Project updates that would be needed

docs branch

You have to do a one-time creation of a clean docs branch so that the mike tool can put the versioned docs on that branch.

Locally, I used the following commands to do that:

git checkout --orphan docs
git rm -rf .
git clean -fdx
git commit --allow-empty -m "Initial commit of docs"
git push origin docs

Netlify updates

In my Netlify account, I have the following settings. This way, Netlify builds based on changes to the docs branch. You don't need a specific build command because the HTML files are already built to the docs branch through the mike versioning.

Build & Deploy > Build settings

• Runtime: Not set
• Base directory: /
• Package directory: Not set
• Build command: Not set
• Publish directory: .

Build & Deploy > Branches and deploy contexts

• Production branch: docs

[netlify]

❌ Deploy Preview for gateway-api-inference-extension failed. Why did it fail? →

Name	Link
🔨 Latest commit	4a6789a
🔍 Latest deploy log	https://app.netlify.com/projects/gateway-api-inference-extension/deploys/683090b46ee5170008a09e34

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: artberger
Once this PR has been reviewed and has the lgtm label, please assign danehans for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[k8s-ci-robot]

Welcome @artberger!

It looks like this is your first PR to kubernetes-sigs/gateway-api-inference-extension 🎉. Please refer to our pull request process documentation to help your PR have a smooth ride to approval.

You will be prompted by a bot to use commands during the review process. Do not be afraid to follow the prompts! It is okay to experiment. Here is the bot commands documentation.

You can also check if kubernetes-sigs/gateway-api-inference-extension has its own contribution guidelines.

You may want to refer to our testing guide if you run into trouble with your tests not passing.

If you are having difficulty getting your pull request seen, please follow the recommended escalation practices. Also, for tips and tricks in the contribution process you may want to read the Kubernetes contributor cheat sheet. We want to make sure your contribution gets all the attention it needs!

Thank you, and welcome to Kubernetes. 😃

[k8s-ci-robot]

Hi @artberger. Thanks for your PR.

I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.