docs: add more examples to blog post

Author: antfu

docs/content/9.posts/1.pluggable-extensible-playful-devtools.md

@@ -324,29 +324,51 @@ export default defineConfig({
 
 The adapter turns an existing devframe into a Vite plugin. The `devtools.setup` entry lets Vite plugins use the same context directly. This makes adoption incremental: tools can start where they are and still participate in the shared ecosystem.
 
+### Nuxt DevTools
+
+The new [Nuxt DevTools](https://github.com/nuxt/devtools) v4 builds on top of both Devframe and Vite DevTools. It now would inherits the ecosystem of both of them.
+
+<figure class="my-4">
+  <img src="/images/devframe/nuxt-devtools-v4.png" class="rounded-lg border border-default shadow-lg" alt="Nuxt DevTools v4" />
+  <figcaption class="text-center text-sm text-muted mt-2">Nuxt DevTools v4</figcaption>
+</figure>
+
+Here are the stacking layers to demonstrate this better:
+
 ::dev-tools-stack
 ::
 
-## Inheriting the Ecosystem
+[Vue DevTools](https://devtools.vuejs.org/) is also migrating to the Vite DevTools foundation. Vue capabilities such as component and reactivity inspection can then coexist with Vite-native capabilities and framework-neutral devframes in the same DevTools host.
 
-Framework-specific layers keep their own look and can be much richer because they understand their framework's conventions and runtime. The infrastructure stays shared while the final experience remains specific.
+In a way, the story has come full circle: the wish that started with Nuxt DevTools now returns with a concrete foundation underneath. Nuxt DevTools v4 is expected to ship with Nuxt v5 and will also be available as a manual opt-in for Nuxt 4.
 
-[Vue DevTools](https://devtools.vuejs.org/) is migrating to the Vite DevTools foundation. Vue capabilities such as component and reactivity inspection can then coexist with Vite-native capabilities and framework-neutral devframes in the same DevTools host.
+### Next.js DevTools (Prototype)
 
-The new [Nuxt DevTools](https://github.com/nuxt/devtools) v4 builds on top of both. It inherits Vite DevTools and Vue DevTools, then adds Nuxt-specific knowledge: pages, modules, auto-imports, server APIs, runtime state, and contributions from the Nuxt module ecosystem.
+We are also experimenting with the integrations of bringing Devframes to Next.js DevTools, and internally, we have a working prototype to have Devframes Hub working inside Next.js DevTools without any modifications to the installed devframe plugins.
 
-In a way, the story has come full circle: the wish that started with Nuxt DevTools now returns with a concrete foundation underneath. Nuxt DevTools v4 is expected to ship with Nuxt v5 and will also be available as a manual opt-in for Nuxt 4.
+<figure class="my-4">
+  <video
+   class="rounded-lg border border-default shadow-lg" 
+   alt="Next.js DevTools with Devframes prototype" autoplay muted loop>
+    <source src="/images/devframe/nextjs-devtools-with-devframes-demo.mp4" type="video/mp4">
+    <img src="/images/devframe/nextjs-devtools-with-devframes-demo.png"  alt="Next.js DevTools with Devframes prototype" >
+  </video>
+  <figcaption class="text-center text-sm text-muted mt-2">Next.js DevTools with Devframes prototype<br><span class="italic opacity-50">(this is an internal prototype, it's not yet available and does not represent the final state)</span></figcaption>
+</figure>
 
-Devframe itself remains independent of Vite and any framework. A future framework-specific DevTools host can mount the same hub and devframes, then add its own knowledge and presentation on top of the shared foundation.
+
+## Inheriting the Ecosystem
+
+Framework-specific layers keep their own look and can be much richer because they understand their framework's conventions and runtime. The infrastructure stays shared while the final experience remains specific.
+
+Devframe itself remains independent of Vite and any framework. A future framework-specific DevTools host can mount the same hub and devframes, then add its own knowledge and presentation on top of the shared foundation:
 
 ::devframe-ecosystem-map
 ::
 
 ## Build Your Own DevTools
 
-Devframe supports framework authors and established tooling teams as well as project-specific DevTools and one-off visualizations.
-
-With built-in coding-agent skills and a growing collection of real-world examples, we are exploring a future where you might ask a coding agent:
+Devframe supports framework authors and established tooling teams as well as project-specific DevTools and one-off visualizations. With built-in coding-agent skills and a growing collection of real-world examples, we are exploring a future where you might ask a coding agent:
 
 > "Build me a one-off devframe to visualize my app's network request flow and highlight the bottlenecks."