score-labspace blog post

content/blog/_index.md

@@ -1,4 +1,4 @@
 ---
 title: Blog
-featured_post: score-at-kubecon-eu-2026-in-amsterdam
+featured_post: score-labspace
 ---

content/blog/score-labspace/index.md

@@ -0,0 +1,126 @@
+---
+title: "Announcing the Score Labspace: learn Score hands-on, in minutes"
+date: 2026-10-26
+summary: "Announcing the new Score Labspace: a guided, hands-on lab to learn about Score and its score-compose and score-k8s implementations and their features."
+image: score-labspace.png
+author: mathieu-benoit
+---
+🎉 Today we're announcing the **Score Labspace**, a brand new hands-on lab to learn about Score and its `score-compose` and `score-k8s` implementations and their features by actually running them! 🎉
+
+## Why a lab?
+
+Since the beginning, one of the most frequent pieces of feedback we hear from the community is: *"I get the idea behind Score, but I'd like to try it before setting everything up."*
+
+We've already worked on that front with the [Score documentation](https://docs.score.dev/) and, more recently, with the [Score Examples Hub](https://score.dev/blog/score-examples-hub-announcement/). The Score Labspace goes one step further: it's a guided learning experience where the instructions and a ready-to-use terminal live side by side, with all the tools **already installed** for you.
+
+No need to install `score-compose`, `score-k8s`, `kubectl` or `kind` on your machine. If you have Docker with Compose, you're ready to go.
+
+## Run it in one command
+
+```bash
+docker compose -f oci://scorespec/score-labspace:latest up
+```
+
+Then open [http://localhost:3030](http://localhost:3030) and follow the instructions in your browser.
+
+## What will you learn?
+
+The lab is split into seven short modules, each building on the previous one:
+
+1. **Introduction to Score**: what Score is, and how it separates *Abstraction* for Developers from *Standardization* for Platform Engineers.
+2. **The Score Specification**: how to write a `score.yaml` file, from the simplest workload to a realistic one with a PostgreSQL database, DNS and a route.
+3. **Getting started with `score-compose`**: turn that same `score.yaml` into a `compose.yaml` and run it locally with Docker Compose.
+4. **Getting started with `score-k8s`**: take the *exact same* `score.yaml`, generate Kubernetes manifests and deploy them to a local `kind` cluster.
+5. **Advanced scenario with `score-compose`**: customize the output.
+6. **Advanced scenario with `score-k8s`**: customize the output, Kubernetes edition.
+7. **Next steps**: where to go from here.
+
+### One Score file, two platforms
+
+The heart of the lab is the "aha" moment: you write a single, platform-agnostic Score file...
+
+```yaml
+apiVersion: score.dev/v1b1
+metadata:
+  name: hello-world
+  annotations:
+    tags: "nodejs,http,website,javascript"
+containers:
+  hello-world:
+    image: .
+    variables:
+      PORT: "3000"
+      MESSAGE: "Hello, World!"
+      DB_DATABASE: ${resources.db.name}
+      DB_USER: ${resources.db.username}
+      DB_PASSWORD: ${resources.db.password}
+      DB_HOST: ${resources.db.host}
+      DB_PORT: ${resources.db.port}
+resources:
+  db:
+    type: postgres
+  dns:
+    type: dns
+  route:
+    type: route
+    params:
+      host: ${resources.dns.host}
+      path: /
+      port: 8080
+service:
+  ports:
+    www:
+      port: 8080
+      targetPort: 3000
+```
+
+...and then deploy it twice, without changing a single line:
+
+```bash
+# With Docker Compose
+score-compose init
+score-compose generate score.yaml --image scorespec/sample-score-app:latest
+docker compose up -d
+
+# With Kubernetes
+score-k8s init
+score-k8s generate score.yaml --image scorespec/sample-score-app:latest
+kubectl apply -f manifests.yaml
+```
+
+### Going further: patch templates and provisioners
+
+The two advanced modules are where Platform Engineers will feel at home. You'll learn how to:
+
+- **Override properties** of the Score file at generation time with `--override-property`.
+- **Customize the generated output** with [patch templates](https://docs.score.dev/docs/score-implementation/score-compose/patch-templates/), for example to enforce a secure, unprivileged posture (`read_only`, non-root `user`, dropped capabilities for Compose; `securityContext` and a dedicated `ServiceAccount` for Kubernetes). You'll also see how to load community patchers from the [Examples Hub](https://docs.score.dev/examples/patch-templates).
+- **Define your own resource types** with [resource provisioners](https://docs.score.dev/docs/score-implementation/score-compose/resources-provisioners/): start from zero provisioners, watch `generate` fail with `resource 'dns.default#hello-world.dns' is not supported by any provisioner`, then bring your own `dns` provisioner and fix it step by step.
+- Use platform-specific options like `--build` (Compose) or `--namespace`, `--generate-namespace` and `--format kyaml` (Kubernetes).
+
+By the end, you'll have a concrete picture of how Developers describe *what* they need, while Platform Engineers decide *how* it's delivered.
+
+## Open source and open to contributions
+
+The Score Labspace lives in [score-spec/score-labspace](https://github.com/score-spec/score-labspace). Each module is a simple Markdown file, so improving an explanation or adding a new scenario is a pull request away.
+
+It's built with [Docker Labspaces](https://github.com/dockersamples/labspace-starter), and Score is proudly part of the [Docker-Sponsored Open Source Program](https://score.dev/blog/docker-sponsored-open-source-program/). 🐳
+
+## What's next?
+
+Give the lab a try and tell us what you think! Is a scenario missing? Is a step unclear? Which implementation or resource type would you like to see covered next? Your feedback shapes the next modules.
+
+- Start the lab: [github.com/score-spec/score-labspace](https://github.com/score-spec/score-labspace)
+- Share feedback or ideas: [open an issue](https://github.com/score-spec/score-labspace/issues)
+- Join the conversation: [Score community](https://docs.score.dev/docs/community/)
+- Keep exploring: [Score Examples Hub](https://docs.score.dev/examples/)
+
+## Come and see it live at KubeCon NA 🎤
+
+Want a guided tour instead? The Score Maintainers will be **demoing the Score Labspace live at our Kiosk in the Project Pavilion** at [KubeCon + CloudNativeCon North America 2026](https://events.linuxfoundation.org/kubecon-cloudnativecon-north-america/) in Salt Lake City (November 9-12)!
+
+- 📍 **Where:** Project Pavilion, Hall 5 (Cosmic Canyon), Level 1, Salt Palace Convention Center, kiosk **#TBD**
+- 🕒 **When:** Pavilion hours are Tuesday 10:45 AM-7:00 PM, Wednesday 10:30 AM-5:00 PM and Thursday 10:30 AM-2:00 PM (demo times: **TBD**)
+
+Come say hi, run the lab with us, ask your questions about Score, and tell us what you'd like to see next. You can find the kiosk in the [Project Pavilion Kiosk Directory](https://events.linuxfoundation.org/kubecon-cloudnativecon-north-america/features-add-ons/project-engagement/#project-pavilion-kiosk-directory). We can't wait to meet you there!
+
+Let's Score it! 🎶