🚀 Feature Request: Expose `Prose*` Components in Nuxt UI with Shorter Aliases (`UH1`, `UP`, `UOl`, etc.)

[MrKaashee]

Package

v4.0.0-alpha.x

Description

✨ Overview

Nuxt UI + @nuxt/content provides beautifully styled prose components like:

• ProseH1, ProseH2, ...
• ProseP
• ProseOl, ProseUl
• ProseHr, ProseEm, etc.

💡 What I’m Proposing

I'd love to see these components:

1. ✅ Exposed in Nuxt UI directly – so we can use them even without @nuxt/content.
2. ✅ Aliased to cleaner, shorter component names that match Nuxt UI naming conventions.

🔄 Suggested Mapping

Current Name	Proposed Nuxt UI Alias
ProseH1	UH1
ProseH2	UH2
ProseP	UP
ProseOl	UOl
ProseUl	UUl
ProseHr	UHr
ProseEm	UEm

These would align perfectly with the existing pattern of UButton, UCard, UContainer, etc.

📦 Why This Matters

• 🧩 Consistency: Reuse the same design system across both prose and layout components.
• 🔁 Reusability: Apply these components in any page, not just markdown.
• 🧘‍♂️Cleaner Templates: Shorter names = easier to read/write.
• 💅 Design Coherence: Unified look and feel across content and UI components.

🧪 Example Use Case

<template>
  <div>
    <UH1>Welcome to Our Site</UH1>
    <UP>This paragraph uses Nuxt UI's prose styling.</UP>
    <UOl>
      <li>Beautiful Typography</li>
      <li>Consistent Spacing</li>
      <li>No Extra Setup</li>
    </UOl>
  </div>
</template>

Additional context

No response

[HugoRCD]

@MrKaashee You can already use prose components without @nuxt/content by forcing their imports into your nuxt.config.ts https://ui4.nuxt.com/docs/getting-started/installation/nuxt#content

However, I'm not sure about having 2 names for the same component, it could be confusing, and I think it's good to separate these components from the rest, since they were designed to be used with @nuxt/content