docs: add blogs section with curated CNCF and nttlabs posts

[singhvishalkr]

Summary

Addresses #4818 -- adds the curated blogs section Akihiro suggested when #4817 landed.

Creates website/content/en/docs/blogs/_index.md, modelled directly on the talks/_index.md structure (year-bucketed ## headings, ### per entry, one-line description, "Read the [post on ...]" link). Weight is 451 so the section appears right under Talks (450) in the sidebar.

Seed content

Four well-known posts to start with; easy to grow from here:

• 2022 -- nttlabs / Medium: Lima is now a CNCF project (@AkihiroSuda, Sandbox entry)
• 2025 -- CNCF blog: Lima becomes a CNCF incubating project
• 2025 -- CNCF blog: Lima v2.0: New features for secure AI workflows
• 2026 -- CNCF blog: Lima v2.1: macOS guests and enhanced AI agent safety

If you prefer a different initial set (e.g. include Rancher Desktop / Colima coverage, or a specific author's post) happy to swap.

Checklist

• DCO signed-off
• Structure mirrors talks/_index.md
• No new nav wiring needed -- Hugo picks it up from the _index.md weight

Closes #4818.

[AkihiroSuda]

https://github.com/lima-vm/lima/discussions/categories/show-and-tell is more appropriate

[AkihiroSuda]

You can also add:

• https://medium.com/nttlabs/containerd-and-lima-39e0b64d2a59
• https://medium.com/nttlabs/accelerating-llama-on-lima-with-wasi-nn-rpc-06b84bcbbe5c
• https://medium.com/nttlabs/containerd-v2-0-nerdctl-v2-0-lima-v1-0-93026b5839f8
• https://medium.com/nttlabs/containerd-v2-1-nerdctl-v2-1-and-lima-v1-1-74400ee87c2c
• https://www.cncf.io/blog/2024/10/10/lima-completes-fuzzing-audit/

[unsuman]

Some others:
https://cloud.tencent.com.cn/developer/article/2425111?from=15425&frompage=seopage
https://medium.com/@lizrice/exposing-loadbalancer-services-running-on-kind-in-lima-vms-4d58cd4b5e12
https://jvns.ca/blog/2023/07/10/lima--a-nice-way-to-run-linux-vms-on-mac/
https://blog.wayanjim.my.id/en/posts/setup-k3s-single-node-gitops-dengan-flux
https://cloudsecburrito.com/lima-linux-on-macos-without-the-ceremony
https://medium.com/@lysharing/why-i-chose-limactl-461840c476ad

[singhvishalkr]

Thanks for the steer, @AkihiroSuda — agreed that a Show-and-tell thread fits this kind of curated list much better than a docs page, since it grows with community contributions rather than being frozen at merge time.

Moved the content (plus your five NTT Labs / CNCF additions) to a new discussion thread here: #4864

Closing this PR. The docs/blogs directory and any sidebar weight changes are reverted implicitly by the close.

[singhvishalkr]

Thanks @unsuman — great list! I've added all six links to the Show-and-tell discussion so they're discoverable there: #4864 (comment)

Feel free to reply in that thread directly with any future finds and I'll fold them in.

[AkihiroSuda]

Thanks for the steer, @AkihiroSuda — agreed that a Show-and-tell thread fits this kind of curated list much better than a docs page, since it grows with community contributions rather than being frozen at merge time.

My suggestion was just to replace a link to https://github.com/lima-vm/lima/issues with https://github.com/lima-vm/lima/discussions/categories/show-and-tell though.

I have no strong opinion whether we should collect blogs in the web site or in the GitHub Discussions, but probably we should make sure that the GitHub Discussion thread is linked from the web site, otherwise visitors can't find it.

[singhvishalkr]

Apologies @AkihiroSuda -- I misread your first review and closed this too quickly. Re-reading now: your line-6 comment was specifically "replace the /issues link with discussions/categories/show-and-tell", not "delete the page". Reopening with the actual requested change applied on b900c08.

What's on this push:

• Replaced the trailing "Suggestions welcome via GitHub issues" line with a pointer to the Show-and-tell discussion category, and also to the Community blogs and write-ups about Lima thread specifically, so your "make sure the GitHub Discussion thread is linked from the web site" ask is covered from the opposite direction too -- visitors land on the docs page, see the link, and can follow it into the growing crowd-sourced list.

• Folded in all five of your nttlabs / CNCF additions from the line-1 review comment, year-bucketed against the published dates I verified:

  • 2021 -- containerd & Lima (Sep 2021, nttlabs)
  • 2024 -- Accelerating Llama on Lima, with WASI-NN RPC (Jun 2024, nttlabs)
  • 2024 -- Lima completes fuzzing audit (Oct 2024, CNCF)
  • 2024 -- containerd v2.0, nerdctl v2.0, Lima v1.0 (nttlabs)
  • 2025 -- containerd v2.1, nerdctl v2.1, Lima v1.1 (nttlabs)

• Folded in @unsuman's community finds. jvns.ca's URL carries its date (Jul 2023) so it gets a proper year bucket; the five other posts don't surface a publish date reliably, so they go into a "More community posts" section at the bottom -- I'd rather list them honestly without a fabricated year than invent one.

Discussion #4864 stays up regardless; the docs page links to it explicitly so contributors have a clear place to drop new finds, and I'll continue folding well-known ones onto this page as they accumulate there.

Happy to iterate if you'd prefer a different split (e.g. keep only the CNCF/nttlabs set on the docs page and push everything else entirely to the discussion, or drop the "More community posts" bucket in favour of a single "See the Show-and-tell thread for community write-ups" line).

[AkihiroSuda]

Thanks