add a new blog post for ORAS v0.15

[FeynmanZhou]

No description provided.

[FeynmanZhou]

Hi @SteveLasker @lachie83 @yizha1 @sajayantony @dtzar @oras-project/oras-maintainers

Could you pls help to review this blog post? The preview link is available here.

[SteveLasker]

Overall, looks great. A few nits on digest vs. tag, and consistency on the commands $, some links, and tweak on who submitted the OCI spec changes.
The only other thing I'd suggest is upleveling the oras blob commands in the doc as it went deep without context, and I'd suggest we could do a better experience for the manifest conversation scenario.
If you're just trying to upload/download blobs, that makes sense to round out the primitives in the cli, I just don't think the experience reads that well as blog content.

Keep up the great work, particularly as we get to kubecon.

[SteveLasker]

remove $ to be consistent with other commands, enabling users to copy/paste
Could we change the fetch to a tag? Is there a reason we wanted to be overly cryptic with a digest? Nice that digest is supported, but is it the primary scenario?

BTW, does oras support tag to digest discovery?

[FeynmanZhou]

remove $ to be consistent with other commands, enabling users to copy/paste

If there is an output in the command line, $ is supposed to be added at the beginning. If not, we don't need to add $.
This symbol is used to help readers distinguish between the input command and output.

Could we change the fetch to a tag? Is there a reason we wanted to be overly cryptic with a digest? Nice that digest is supported, but is it the primary scenario?

Yes. The reason we use digest here is that we want to specify the OS/ARCH of Linux/amd64 for this Docker image. Both digest and tag are supported, it depends on the user's requirement.

BTW, does oras support tag to digest discovery?

Do you mean oras tag [flags] <name>{:<tag>} <new_tag@<digest>> ? Can you clarify this question? Thanks.

[SteveLasker]

I think I understand the delineation you're trying to make with $, but it's really confusing to see. Some commands I can just copy/paste, others will have the $ which I can't paste. I'd suggest KISSing it (Keep It Silly Simple)

For the hello-word digest, can you just use the platform architecture tag(hello-world:linux): https://hub.docker.com/_/hello-world/tags
Saying you support digests as well is great. This is another example of keeping it crisp and simple, showing a tag.

[FeynmanZhou]

The platform architecture tag(hello-world:linux) is not worked with oras manifest fetch after testing it.

[sajayantony]

Recommend using the alias everywhere since we want the blog post to showcase the ease of use. The long commands are present in the official documentation and I hopefully we will be moving to the short commands as the actual command in 0.16 anyway.

[SteveLasker]

I think I understand the delineation you're trying to make with $, but it's really confusing to see. Some commands I can just copy/paste, others will have the $ which I can't paste. I'd suggest KISSing it (Keep It Silly Simple)

For the hello-word digest, can you just use the platform architecture tag(hello-world:linux): https://hub.docker.com/_/hello-world/tags
Saying you support digests as well is great. This is another example of keeping it crisp and simple, showing a tag.

[FeynmanZhou]

Updated according to the comments above

[lachie83]

/lgtm

[SteveLasker]

Kudos to publishing:
@FeynmanZhou, the ordering in the TOC is a bit confusing for which is the newest. Suggest a quick fix to put the latest at the top.

This section has some redundant words as well:

In ORAS CLI 0.16 and ORAS-go v2.0.0-rc.4, we'll add support for the OCI artifact spec will be the most significant plan and is targeted to be released at the end of October.