You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For what version of Nuxt UI are you suggesting this?
v2.x
Description
Feature Request: Rich Text Editor Component
Description
I would like to request a Rich Text Editor component to be added to Nuxt UI. This component will allow users to input and format rich text content easily, with support for common formatting options such as bold, italic, headers, lists, and more.
Benefits
Streamlined development for users who need rich text editing features.
Consistency in design and functionality with other Nuxt UI components.
Proposed Solution
Integrate a rich text editor library (e.g., Quill.js, TipTap) as a Nuxt UI component. The component should provide flexibility for customization and ease of use.
Alternatives
For now, users can manually integrate third-party editors, but having a built-in component would significantly improve the development experience.
Additional context
No response
The text was updated successfully, but these errors were encountered:
This has already been discussed in #1889 and #791 and was closed as not planned but now that I think of it, this could have its place inside Nuxt UI Pro v3 which has all the typography done already to use inside the editor.
For what version of Nuxt UI are you suggesting this?
v2.x
Description
Feature Request: Rich Text Editor Component
Description
I would like to request a Rich Text Editor component to be added to Nuxt UI. This component will allow users to input and format rich text content easily, with support for common formatting options such as bold, italic, headers, lists, and more.
Benefits
Proposed Solution
Integrate a rich text editor library (e.g., Quill.js, TipTap) as a Nuxt UI component. The component should provide flexibility for customization and ease of use.
Alternatives
For now, users can manually integrate third-party editors, but having a built-in component would significantly improve the development experience.
Additional context
No response
The text was updated successfully, but these errors were encountered: