Add local deployment docs

[hola-soy-milk]

This condenses the minikube deployment journey into a Local Deployment tutorial.

I'm unsure how much to have in here, such as manually getting an editor token. I find it helpful for getting to know Compute, but maybe it's not relevant to local deployment?

Thank you for any feedback!

[github-actions[bot]]

10 total issues, 1 error, and 9 warnings found for docs.suborbital.dev

Details

ERROR WCAG2AA.Principle1.Guideline1_4.1_4_3.G18.Fail ```html Search ``` This element has insufficient contrast at this conformance level. Expected a contrast ratio of at least 4.5:1, but text in this element has a contrast ratio of 2.27:1. Recommendation: change text colour to #000610. ---
WARNING WCAG2AA.Principle1.Guideline1_3.1_3_1.H48 ```html

``` If this element contains a navigation section, it is recommended that it be marked up as a list. ---
WARNING WCAG2AA.Principle1.Guideline1_3.1_3_1.H48 ```html

...

``` If this element contains a navigation section, it is recommended that it be marked up as a list. ---
WARNING WCAG2AA.Principle1.Guideline1_3.1_3_1.H48 ```html

...

``` If this element contains a navigation section, it is recommended that it be marked up as a list. ---
WARNING WCAG2AA.Principle1.Guideline1_3.1_3_1.H48 ```html

``` If this element contains a navigation section, it is recommended that it be marked up as a list. ---
WARNING WCAG2AA.Principle1.Guideline1_3.1_3_1.H48 ```html

``` If this element contains a navigation section, it is recommended that it be marked up as a list. ---
WARNING WCAG2AA.Principle1.Guideline1_3.1_3_1.H48 ```html

Skip to main content ``` This element has "position: fixed". This may require scrolling in two dimensions, which is considered a failure of this Success Criterion. ---
WARNING WCAG2AA.Principle1.Guideline1_4.1_4_3_F24.F24.FGColour ```html / ``` Check that this element has an inherited background colour or image to complement the corresponding inline foreground colour. ---
WARNING WCAG2AA.Principle1.Guideline1_4.1_4_3_F24.F24.FGColour ```html / ``` Check that this element has an inherited background colour or image to complement the corresponding inline foreground colour. ---

---

📝 docs | :octocat: repo | 🙋🏽‍♀️ issues | 🏪 marketplace | A11yWatch

[flaki]

I'm unsure how much to have in here, such as manually getting an editor token. I find it helpful for getting to know Compute, but maybe it's not relevant to local deployment?

Dunno, I kinda feel like that may be its own docs page (and you could link it here)? I shall admit I'm not entirely sure where such a page would position itself on the Documentation <-> Tutorial axis...

[hola-soy-milk]

I'm unsure how much to have in here, such as manually getting an editor token. I find it helpful for getting to know Compute, but maybe it's not relevant to local deployment?

Dunno, I kinda feel like that may be its own docs page (and you could link it here)? I shall admit I'm not entirely sure where such a page would position itself on the Documentation <-> Tutorial axis...

Thank you! I'm kinda leaning this way too, and would love to hear what the rest think, please!

[LauraLangdon]

Ooh, this is my first time navigating future merge conflicts! On my branch where I'm updating the Compute docs, I've created a subcategory Compute -> Deploying Compute, and this doc would belong in there. But if I'm reading this correctly, your PR here would create Compute -> Local Deployment -> Local Deployment. What's the protocol in this sort of situation? Like we can just merge this and then I can move the doc in my subcategory on my branch, but I just thought I'd check to see if there's a different established procedure. ☺️

[github-actions[bot]]

10 total issues, 1 error, and 9 warnings found for docs.suborbital.dev

Details

ERROR WCAG2AA.Principle1.Guideline1_4.1_4_3.G18.Fail ```html Search ``` This element has insufficient contrast at this conformance level. Expected a contrast ratio of at least 4.5:1, but text in this element has a contrast ratio of 2.27:1. Recommendation: change text colour to #000610. ---
WARNING WCAG2AA.Principle1.Guideline1_3.1_3_1.H48 ```html

``` If this element contains a navigation section, it is recommended that it be marked up as a list. ---
WARNING WCAG2AA.Principle1.Guideline1_3.1_3_1.H48 ```html

...

``` If this element contains a navigation section, it is recommended that it be marked up as a list. ---
WARNING WCAG2AA.Principle1.Guideline1_3.1_3_1.H48 ```html

...

``` If this element contains a navigation section, it is recommended that it be marked up as a list. ---
WARNING WCAG2AA.Principle1.Guideline1_3.1_3_1.H48 ```html

``` If this element contains a navigation section, it is recommended that it be marked up as a list. ---
WARNING WCAG2AA.Principle1.Guideline1_3.1_3_1.H48 ```html

``` If this element contains a navigation section, it is recommended that it be marked up as a list. ---
WARNING WCAG2AA.Principle1.Guideline1_3.1_3_1.H48 ```html

Skip to main content ``` This element has "position: fixed". This may require scrolling in two dimensions, which is considered a failure of this Success Criterion. ---
WARNING WCAG2AA.Principle1.Guideline1_4.1_4_3_F24.F24.FGColour ```html / ``` Check that this element has an inherited background colour or image to complement the corresponding inline foreground colour. ---
WARNING WCAG2AA.Principle1.Guideline1_4.1_4_3_F24.F24.FGColour ```html / ``` Check that this element has an inherited background colour or image to complement the corresponding inline foreground colour. ---

---

📝 docs | :octocat: repo | 🙋🏽‍♀️ issues | 🏪 marketplace | A11yWatch

[hola-soy-milk]

Ooh, this is my first time navigating future merge conflicts! On my branch where I'm updating the Compute docs, I've created a subcategory Compute -> Deploying Compute, and this doc would belong in there. But if I'm reading this correctly, your PR here would create Compute -> Local Deployment -> Local Deployment. What's the protocol in this sort of situation? Like we can just merge this and then I can move the doc in my subcategory on my branch, but I just thought I'd check to see if there's a different established procedure. ☺️

Seeing as we'll likely be merging your change first, I can adapt mine to fit this new structure! 😄 Thanks for catching this!

[github-actions[bot]]

10 total issues, 1 error, and 9 warnings found for docs.suborbital.dev

Details

ERROR WCAG2AA.Principle1.Guideline1_4.1_4_3.G18.Fail ```html Search ``` This element has insufficient contrast at this conformance level. Expected a contrast ratio of at least 4.5:1, but text in this element has a contrast ratio of 2.27:1. Recommendation: change text colour to #000610. ---
WARNING WCAG2AA.Principle1.Guideline1_3.1_3_1.H48 ```html

``` If this element contains a navigation section, it is recommended that it be marked up as a list. ---
WARNING WCAG2AA.Principle1.Guideline1_3.1_3_1.H48 ```html

...

``` If this element contains a navigation section, it is recommended that it be marked up as a list. ---
WARNING WCAG2AA.Principle1.Guideline1_3.1_3_1.H48 ```html

...

``` If this element contains a navigation section, it is recommended that it be marked up as a list. ---
WARNING WCAG2AA.Principle1.Guideline1_3.1_3_1.H48 ```html

``` If this element contains a navigation section, it is recommended that it be marked up as a list. ---
WARNING WCAG2AA.Principle1.Guideline1_3.1_3_1.H48 ```html

``` If this element contains a navigation section, it is recommended that it be marked up as a list. ---
WARNING WCAG2AA.Principle1.Guideline1_3.1_3_1.H48 ```html

Skip to main content ``` This element has "position: fixed". This may require scrolling in two dimensions, which is considered a failure of this Success Criterion. ---
WARNING WCAG2AA.Principle1.Guideline1_4.1_4_3_F24.F24.FGColour ```html / ``` Check that this element has an inherited background colour or image to complement the corresponding inline foreground colour. ---
WARNING WCAG2AA.Principle1.Guideline1_4.1_4_3_F24.F24.FGColour ```html / ``` Check that this element has an inherited background colour or image to complement the corresponding inline foreground colour. ---

---

📝 docs | :octocat: repo | 🙋🏽‍♀️ issues | 🏪 marketplace | A11yWatch

[LauraLangdon]

Ooh, this is my first time navigating future merge conflicts! On my branch where I'm updating the Compute docs, I've created a subcategory Compute -> Deploying Compute, and this doc would belong in there. But if I'm reading this correctly, your PR here would create Compute -> Local Deployment -> Local Deployment. What's the protocol in this sort of situation? Like we can just merge this and then I can move the doc in my subcategory on my branch, but I just thought I'd check to see if there's a different established procedure. ☺️

Seeing as we'll likely be merging your change first, I can adapt mine to fit this new structure! 😄 Thanks for catching this!

Cheers! LGMT!

[flaki]

@LauraLangdon is there a process for dealing with/pleasing the spell checker? "prefilled" vs "pre-filled" could probably be fixed but [N|n]grok and [M|m]inikube will probably need to be added to be "learned"?

[LauraLangdon]

@LauraLangdon is there a process for dealing with/pleasing the spell checker? "prefilled" vs "pre-filled" could probably be fixed but [N|n]grok and [M|m]inikube will probably need to be added to be "learned"?

Literally just adding both capitalization versions of both words to spelling.dic (apparently my phone's keyboard doesn't do back ticks 🙄).

I can do that in a bit to save Ramón the hassle.

[github-actions[bot]]

10 total issues, 1 error, and 9 warnings found for docs.suborbital.dev

Details

ERROR WCAG2AA.Principle1.Guideline1_4.1_4_3.G18.Fail ```html Search ``` This element has insufficient contrast at this conformance level. Expected a contrast ratio of at least 4.5:1, but text in this element has a contrast ratio of 2.27:1. Recommendation: change text colour to #000610. ---
WARNING WCAG2AA.Principle1.Guideline1_3.1_3_1.H48 ```html

``` If this element contains a navigation section, it is recommended that it be marked up as a list. ---
WARNING WCAG2AA.Principle1.Guideline1_3.1_3_1.H48 ```html

...

``` If this element contains a navigation section, it is recommended that it be marked up as a list. ---
WARNING WCAG2AA.Principle1.Guideline1_3.1_3_1.H48 ```html

...

``` If this element contains a navigation section, it is recommended that it be marked up as a list. ---
WARNING WCAG2AA.Principle1.Guideline1_3.1_3_1.H48 ```html

``` If this element contains a navigation section, it is recommended that it be marked up as a list. ---
WARNING WCAG2AA.Principle1.Guideline1_3.1_3_1.H48 ```html

``` If this element contains a navigation section, it is recommended that it be marked up as a list. ---
WARNING WCAG2AA.Principle1.Guideline1_3.1_3_1.H48 ```html

Skip to main content ``` This element has "position: fixed". This may require scrolling in two dimensions, which is considered a failure of this Success Criterion. ---
WARNING WCAG2AA.Principle1.Guideline1_4.1_4_3_F24.F24.FGColour ```html / ``` Check that this element has an inherited background colour or image to complement the corresponding inline foreground colour. ---
WARNING WCAG2AA.Principle1.Guideline1_4.1_4_3_F24.F24.FGColour ```html / ``` Check that this element has an inherited background colour or image to complement the corresponding inline foreground colour. ---

---

📝 docs | :octocat: repo | 🙋🏽‍♀️ issues | 🏪 marketplace | A11yWatch

[github-actions[bot]]

10 total issues, 1 error, and 9 warnings found for docs.suborbital.dev

Details

ERROR WCAG2AA.Principle1.Guideline1_4.1_4_3.G18.Fail ```html Search ``` This element has insufficient contrast at this conformance level. Expected a contrast ratio of at least 4.5:1, but text in this element has a contrast ratio of 2.27:1. Recommendation: change text colour to #000610. ---
WARNING WCAG2AA.Principle1.Guideline1_3.1_3_1.H48 ```html

``` If this element contains a navigation section, it is recommended that it be marked up as a list. ---
WARNING WCAG2AA.Principle1.Guideline1_3.1_3_1.H48 ```html

...

``` If this element contains a navigation section, it is recommended that it be marked up as a list. ---
WARNING WCAG2AA.Principle1.Guideline1_3.1_3_1.H48 ```html

...

``` If this element contains a navigation section, it is recommended that it be marked up as a list. ---
WARNING WCAG2AA.Principle1.Guideline1_3.1_3_1.H48 ```html

``` If this element contains a navigation section, it is recommended that it be marked up as a list. ---
WARNING WCAG2AA.Principle1.Guideline1_3.1_3_1.H48 ```html

``` If this element contains a navigation section, it is recommended that it be marked up as a list. ---
WARNING WCAG2AA.Principle1.Guideline1_3.1_3_1.H48 ```html

Skip to main content ``` This element has "position: fixed". This may require scrolling in two dimensions, which is considered a failure of this Success Criterion. ---
WARNING WCAG2AA.Principle1.Guideline1_4.1_4_3_F24.F24.FGColour ```html / ``` Check that this element has an inherited background colour or image to complement the corresponding inline foreground colour. ---
WARNING WCAG2AA.Principle1.Guideline1_4.1_4_3_F24.F24.FGColour ```html / ``` Check that this element has an inherited background colour or image to complement the corresponding inline foreground colour. ---

---

📝 docs | :octocat: repo | 🙋🏽‍♀️ issues | 🏪 marketplace | A11yWatch

[hola-soy-milk]

Oooh! Thank you both for looking into this

[hola-soy-milk]

Thank you all for approving!

Not sure why the Github Pages build is failing, will investigate.

As discussed, once #155 is merged, I'll rebase and restructure this so it fits in nicely and will then merge 😄

[LauraLangdon]

Not sure why the Github Pages build is failing, will investigate.

I think it's all good, just that the check doesn't like it when it runs and there are no changes to the site content (like when I pushed my additions to the dictionary).

[hola-soy-milk]

Got it!! Thanks for clarifying