You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Why
Interviews with kpack users (n=4), particularly those who teach kpack to others, have expressed frustration at the overloaded use of the name 'image' being used to describe the core custom resource produced by kpack. Today, "image" means a container image in industry standard terminology. In order to alert new users that an image in kpack is a new concept (not a container image), we should differentiate or clarify the name of the image resource in kpack in order to help new users understand the purpose of kpack and get going quickly.
What
Find and replace "image" with "image resource" on each of the following docs pages whenever the concept is referenced or introduced. kp CLI examples that include kp image need not be replaced since image will remain the command name (CLI issue here).
Why
Interviews with kpack users (n=4), particularly those who teach kpack to others, have expressed frustration at the overloaded use of the name 'image' being used to describe the core custom resource produced by kpack. Today, "image" means a container image in industry standard terminology. In order to alert new users that an image in kpack is a new concept (not a container image), we should differentiate or clarify the name of the image resource in kpack in order to help new users understand the purpose of kpack and get going quickly.
What
Find and replace "image" with "image resource" on each of the following docs pages whenever the concept is referenced or introduced. kp CLI examples that include
kp image
need not be replaced sinceimage
will remain the command name (CLI issue here).Install kpack
Get started with the tutorial
Check out the documentation on kpack concepts:
Interact with kpack using kpack CLI
Tailing logs with the kpack log utility
Documentation on Local Development
The text was updated successfully, but these errors were encountered: