From 31d797c225d874cdc5d07e4b87d85ebbab2ef2e9 Mon Sep 17 00:00:00 2001
From: NullVoxPopuli <199018+NullVoxPopuli@users.noreply.github.com>
Date: Fri, 11 Jul 2025 14:13:43 -0400
Subject: [PATCH 1/4] Update template-tag-format.md

---
 guides/release/components/template-tag-format.md | 12 ++++++++++++
 1 file changed, 12 insertions(+)

diff --git a/guides/release/components/template-tag-format.md b/guides/release/components/template-tag-format.md
index 6754e4cfec..7b86cde3d7 100644
--- a/guides/release/components/template-tag-format.md
+++ b/guides/release/components/template-tag-format.md
@@ -259,6 +259,18 @@ export default CustomSelect;
 
 This can be a powerful refactoring technique to break up large components into smaller ones. (where it makes sense!)
 
+## Runtime compiler
+
+```gjs
+import { template } from '@ember/template-compilation';
+
+const hello = 'Greetings';
+
+export default template(`{{hello}}`, {
+  scope: () => ({ hello }),
+});
+```
+
 ## Testing
 
 Historically, Ember's integration tests have been written using the `hbs` tagged template literal. This is no longer necessary with the template tag format. Instead, use the `<template>` tag to define a template to render.

From e722e26e2a1ff16037db9a3dd6885db7560822b8 Mon Sep 17 00:00:00 2001
From: NullVoxPopuli <199018+NullVoxPopuli@users.noreply.github.com>
Date: Sat, 12 Jul 2025 19:58:11 -0400
Subject: [PATCH 2/4] Update template-tag-format.md

---
 .../release/components/template-tag-format.md | 27 ++++++++++++++++++-
 1 file changed, 26 insertions(+), 1 deletion(-)

diff --git a/guides/release/components/template-tag-format.md b/guides/release/components/template-tag-format.md
index 7b86cde3d7..117a3edf61 100644
--- a/guides/release/components/template-tag-format.md
+++ b/guides/release/components/template-tag-format.md
@@ -261,8 +261,10 @@ This can be a powerful refactoring technique to break up large components into s
 
 ## Runtime compiler
 
+Creating a template-only component via the runtime compiler:
+
 ```gjs
-import { template } from '@ember/template-compilation';
+import { template } from '@ember/template-compilation/runtime';
 
 const hello = 'Greetings';
 
@@ -271,6 +273,29 @@ export default template(`{{hello}}`, {
 });
 ```
 
+And a class-component:
+
+```gjs
+import { template } from "@ember/template-compiler";
+class Example extends Component {
+  static {
+    template(
+      "Hello {{message}}",
+      {
+        component: this,
+        scope: () => ({ message }),
+      },
+    );
+  }
+
+}
+```
+
+Omitting the `/runtime` at the end of the import allows ahead-of-time compilation to occur on components created with `template()`
+
+
+
+
 ## Testing
 
 Historically, Ember's integration tests have been written using the `hbs` tagged template literal. This is no longer necessary with the template tag format. Instead, use the `<template>` tag to define a template to render.

From 4d9154ee8a7904b78d38decebf2eae3a15fde482 Mon Sep 17 00:00:00 2001
From: NullVoxPopuli <199018+NullVoxPopuli@users.noreply.github.com>
Date: Sun, 13 Jul 2025 10:59:22 -0400
Subject: [PATCH 3/4] Update template-tag-format.md

---
 guides/release/components/template-tag-format.md | 13 ++++++++-----
 1 file changed, 8 insertions(+), 5 deletions(-)

diff --git a/guides/release/components/template-tag-format.md b/guides/release/components/template-tag-format.md
index 117a3edf61..490ce7a23f 100644
--- a/guides/release/components/template-tag-format.md
+++ b/guides/release/components/template-tag-format.md
@@ -259,12 +259,14 @@ export default CustomSelect;
 
 This can be a powerful refactoring technique to break up large components into smaller ones. (where it makes sense!)
 
-## Runtime compiler
+## Low-level format
+
+All of template-tag format can be represented in it's pure-javascript form using `template` from either `@ember/template-compiler` or `@ember/template-compiler/runtime`.
 
 Creating a template-only component via the runtime compiler:
 
 ```gjs
-import { template } from '@ember/template-compilation/runtime';
+import { template } from '@ember/template-compiler/runtime';
 
 const hello = 'Greetings';
 
@@ -277,6 +279,9 @@ And a class-component:
 
 ```gjs
 import { template } from "@ember/template-compiler";
+
+const message = "Hello there";
+
 class Example extends Component {
   static {
     template(
@@ -291,9 +296,7 @@ class Example extends Component {
 }
 ```
 
-Omitting the `/runtime` at the end of the import allows ahead-of-time compilation to occur on components created with `template()`
-
-
+If in an environment with compilation, omitting the `/runtime` at the end of the import allows ahead-of-time compilation to occur on components created with `template()` for better runtime performance.
 
 
 ## Testing

From b34e60a2abac34a57761d99ea1aa72496acd738f Mon Sep 17 00:00:00 2001
From: NullVoxPopuli <199018+NullVoxPopuli@users.noreply.github.com>
Date: Fri, 18 Jul 2025 14:38:24 -0400
Subject: [PATCH 4/4] Update template-tag-format.md

---
 guides/release/components/template-tag-format.md | 8 ++++++++
 1 file changed, 8 insertions(+)

diff --git a/guides/release/components/template-tag-format.md b/guides/release/components/template-tag-format.md
index 490ce7a23f..b90a4c9907 100644
--- a/guides/release/components/template-tag-format.md
+++ b/guides/release/components/template-tag-format.md
@@ -298,6 +298,14 @@ class Example extends Component {
 
 If in an environment with compilation, omitting the `/runtime` at the end of the import allows ahead-of-time compilation to occur on components created with `template()` for better runtime performance.
 
+Without specifying `/runtime`, there are additional restrictions required for the argument passed to `template()`:
+- it must be a string literal
+
+With the `/runtime`, the argument passed to `template()` can be an extpression, for example:
+```js
+/* someValue could be f rom anywhere */ 
+export default default template(someValue);
+```
 
 ## Testing