Add example app links to 5 high-impact docs pages

docs-templates/guides/dictionaries.mdx

@@ -319,6 +319,10 @@ function MixedApproach() {
 
 ## Next steps
 
+<Callout>
+  **See it in action:** Check out the [dictionary pattern example app](https://github.com/gt-examples/dictionary-pattern) for a working demo — [live preview](https://dictionary-pattern.generaltranslation.dev).
+</Callout>
+
 - [Languages Guide](__DOCS_PATH__/guides/languages) - Configure supported languages and locale settings
 - [Dynamic Content Guide](/docs/key-concepts/dynamic-content) - Handle runtime translation needs
 - API References:

docs-templates/guides/t.mdx

@@ -215,5 +215,9 @@ The CLI will error on dynamic content in [`<T>`](__DOCS_PATH__/api/components/t)
 
 ## Next steps
 
+<Callout>
+  **See it in action:** Check out the [`<T>` component basics example app](https://github.com/gt-examples/t-component-basics) for a working demo — [live preview](https://t-component-basics.generaltranslation.dev).
+</Callout>
+
 - [Variable Components Guide](__DOCS_PATH__/guides/variables) - Handle dynamic content within JSX translations
 - [Branching Components Guide](__DOCS_PATH__/guides/branches) - Add conditional logic to your translations

docs/en-US/next/guides/dictionaries.mdx

@@ -305,6 +305,10 @@ function MixedApproach() {
 
 ## Next steps
 
+<Callout>
+  **See it in action:** Check out the [dictionary pattern example app](https://github.com/gt-examples/dictionary-pattern) for a working demo — [live preview](https://dictionary-pattern.generaltranslation.dev).
+</Callout>
+
 - [Languages Guide](/docs/next/guides/languages) - Configure supported languages and locale settings
 - [Dynamic Content Guide](/docs/next/guides/dynamic-content) - Handle runtime translation needs
 - API References:

docs/en-US/next/guides/dynamic-content.mdx

@@ -148,6 +148,10 @@ Dynamic translation consumes API quota on every request. Use caching and error h
 
 ## Next steps
 
+<Callout>
+  **See it in action:** Check out the [dynamic content example app](https://github.com/gt-examples/dynamic-content-tx) for a working demo of `tx()` and `<Tx>` — [live preview](https://dynamic-content-tx.generaltranslation.dev).
+</Callout>
+
 - [Local Translation Guide](/docs/next/guides/local-tx) - Handle translations without API calls
 - [Middleware Guide](/docs/next/guides/middleware) - Language detection and routing
 - API References:

docs/en-US/next/guides/middleware.mdx

@@ -140,6 +140,10 @@ export const config = {
 
 ## Next steps
 
+<Callout>
+  **See it in action:** The [static site generation example app](https://github.com/gt-examples/static-site-generation) includes a full middleware setup with locale routing — [live preview](https://static-site-generation.generaltranslation.dev).
+</Callout>
+
 - [SSG Guide](/docs/next/guides/ssg) - Static generation with locale routing
 - [RTL Support](/docs/next/guides/rtl) - Right-to-left languages  
 - API References:

docs/en-US/next/guides/ssg.mdx

@@ -191,6 +191,10 @@ To fix this issue, make sure that all of your route segment files (so typically
 
 ## Further reading
 
+<Callout>
+  **See it in action:** Check out the [static site generation example app](https://github.com/gt-examples/static-site-generation) for a working demo — [live preview](https://static-site-generation.generaltranslation.dev).
+</Callout>
+
 - Check out the [middleware guide](/docs/next/guides/middleware) required for locale routing
 - Check out the [release notes](/blog/gt-next_v6_10_0) for migrating from legacy SSG pattern
-- See an example app [here](https://github.com/generaltranslation/gt/tree/main/examples/next-ssg)
+- See an example app in the monorepo [here](https://github.com/generaltranslation/gt/tree/main/examples/next-ssg)

docs/en-US/next/index.mdx

@@ -344,6 +344,10 @@ For production, you need to pre-translate content since runtime translation is d
 
 ## Next steps
 
+<Callout>
+  **See it in action:** Browse [working example apps](/docs/next/tutorials/examples) to see `gt-next` patterns in real projects, or jump straight to the [app catalog](https://app-catalog.generaltranslation.dev).
+</Callout>
+
 - [`<T>` Component Guide](/docs/next/guides/t) - Deep dive into the [`<T>`](/docs/next/api/components/t) component and JSX translation
 - [String Translation Guide](/docs/next/guides/strings) - Using [`useGT`](/docs/next/api/strings/use-gt) and [`getGT`](/docs/next/api/strings/get-gt)
 - [Variable Components](/docs/next/guides/variables) - Handle dynamic content with [`<Var>`](/docs/next/api/components/var), [`<Num>`](/docs/next/api/components/num), etc.

docs/en-US/next/introduction.mdx

@@ -238,6 +238,10 @@ See the [useTranslations API Reference](/docs/next/api/dictionary/use-translatio
 
 ## Next steps
 
+<Callout>
+  **See it in action:** Browse [working example apps](/docs/next/tutorials/examples) showcasing each pattern, or explore the full [app catalog](https://app-catalog.generaltranslation.dev).
+</Callout>
+
 - Learn about how to set up your Next.js project with the SDK: [Quickstart](/docs/next/tutorials/quickstart)
 - Learn about how to translate JSX content with the [`<T>`](/docs/next/api/components/t) component: [JSX Translation Guide](/docs/next/guides/t)
 - Learn about how to translate strings with the [`useGT`](/docs/next/api/strings/use-gt) hook: [String Translation Guide](/docs/next/guides/strings)