New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Rebranding and homepage #538
Comments
We decided to rebrand to Nuxt UI as it's a module for Nuxt. However, as it's developed by NuxtLabs we decided to keep it under There are indeed breaking changes in minor releases but for specific things, as it's a UI library I don't feel confortable incrementing the major version when changing a key in the |
Thanks for clarifying, makes sense 😀 |
Hi @benjamincanac, happy to see the rebranding, thank you :-) Meanwhile, if you happen to have the idea to have a dedicated twitter account for nuxt ui, please dm on twitter, I have locked-in the |
@TechAkayy At the opposite of my last comment, we finally did change to Thanks for letting me know, it is not planned to have a dedicated Twitter account yet but might happen some day! |
With the upcoming rebranding from Nuxtlabs UI to Nuxt UI (e9b23ad), it will be nice & consistent to have the homepage as ui.nuxt.com (nuxt redirect rules to the rescue?), so that everyone can refer to the component library as Nuxt UI and find the docs at ui.nuxt.com? I see nuxtui.com domain is taken.
Though Im not sure if its possible to be a subdomain of nuxt, I might be missing something here.
It is understandable that the npm package can't be @nuxt/ui (seems to be used already) and has to stay as @nuxthq/ui to avoid breakage. Or is this still a possibility as it's quite early in the evolution of this component library (at least after it's open-sourced)?
Also, are we following semver? I see breaking changes introduced in minor releases.
Thank you.
The text was updated successfully, but these errors were encountered: