Streamline README.md

[imjasonh]

Rendered

Recent feedback (1, 2) indicate that it's not clear enough that ko is a useful option for simply building container images, separate from its Kubernetes support.

This reorders README.md to start with installation options, then highlight ko publish first, then sidetrack into configuration options, then mention Kubernetes support (ko resolve -> ko apply -> ko delete), and end with an FAQ.

It's about 60% as many lines and half as many characters as the current README.

[codecov-io]

Codecov Report

Merging #318 (2976743) into main (a6442e6) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main     #318   +/-   ##
=======================================
  Coverage   38.07%   38.07%           
=======================================
  Files          33       33           
  Lines        1513     1513           
=======================================
  Hits          576      576           
  Misses        844      844           
  Partials       93       93           

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update a6442e6...2976743. Read the comment docs.

[tstromberg]

Talk about a huge refactor! This new version seems to cover all the important getting-started bases, and isn't nearly as intimidating. Users like myself will no longer have an excuse to shy away from ko.

[jonjohnsonjr]

Overall, love the smoother on-ramp.

Some thoughts:

1. I'd keep the aknowledgements, since it's useful for someone interesting in digging into this stuff more.
2. Maybe we should stick source <(ko completion) somewhere?

[afrittoli]

This looks great, thank you!
It might be worth mentioning somewhere that the -f param supports input from stdin through the syntax -f -. This is useful for instance to do something like

kustomize build config | ko resolve -f -

[imjasonh]

kustomize build config | ko resolve -f -

Ooh fun, added as an FAQ

[imjasonh]

1. I'd keep the acknowledgements, since it's useful for someone interesting in digging into this stuff more.
2. Maybe we should stick source <(ko completion) somewhere?

Done and done!

[n3wscott]

/lgtm

[jonjohnsonjr]

LGTM, curious if @mattmoor has any feedback

[patflynn]

You rock Jason! This is exactly the information I needed when I was trying to use Ko to containerize an app to deploy to Cloud Run a while back. I love the format, and all the content around static resources is a huge help. Would have saved me a bundle of time!

[patflynn]

I wish this example had been there two weeks ago!

[n3wscott]

yeah, it is a pretty good pattern: https://github.com/knative-party/site/blob/main/site.go