chore: adjust

Author: antfu

docs/app/components/global/PostAuthor.vue

@@ -15,7 +15,7 @@ withDefaults(defineProps<{
     :href="href"
     target="_blank"
     rel="noopener noreferrer"
-    class="not-prose my-6 inline-flex items-center gap-3 rounded-lg text-inherit no-underline transition-opacity hover:opacity-80"
+    class="not-prose mt-6 inline-flex items-center gap-3 rounded-lg text-inherit no-underline transition-opacity hover:opacity-80"
   >
     <img
       src="https://github.com/antfu.png?size=96"

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

@@ -10,6 +10,9 @@ author: Anthony Fu
 ::post-author{author="Anthony Fu" handle="@antfu" href="https://github.com/antfu"}
 ::
 
+> [!NOTE]
+> This page is still working in progress and not yet announced. Please don't share it outside yet.
+
 Over the years, we have built quite a few DevTools: [UnoCSS Inspector](https://unocss.dev/tools/inspector#inspector), [Vite Plugin Inspect](https://github.com/antfu-collective/vite-plugin-inspect), [Vitest UI](https://vitest.dev/guide/ui), [Nuxt DevTools](https://github.com/nuxt/devtools), [ESLint Config Inspector](https://github.com/eslint/config-inspector), and [Node Modules Inspector](https://github.com/antfu/node-modules-inspector), among others.
 
 They look quite different, but fundamentally they all try to do the same thing: make implicit state visible. Instead of guessing why a CSS utility was generated, how a module was transformed, or which configuration applies to a file, we can see the process directly and interact with it.