-
Notifications
You must be signed in to change notification settings - Fork 30
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
Merge with Nuxt Simple Robots #116
Comments
Hey @ricardogobbosouza you seem to be the sole maintainer at the moment, would you review this when you have a chance, would be great to have your input! cc: @Atinux |
Hey @harlan-zw. I tried to migrate to As I can tell, I think it is a great idea to get single official module, but it should not be merged as is, first it needs to support all features of |
All google directives are supported. I'm open to adding others if you want to make an issue for what's missing, but I wouldn't encourage end users to use them |
I want to actively avoid adding rules in robots.txt that don't do anything, this is part of the validation feature. |
I am happy with this change in order to bring consistency to the Nuxt community 👍 |
This issue is to discuss the possibility of merging with the nuxt-simple-robots module. This is not meant to imply intent, I'll only go ahead with merging if the current maintainers and team give approval for me to do so.
Why Merge
I built the nuxt-simple-robots package as I felt the feature set for this module didn't meet my needs, specifically around modules integrating with it (i.e sitemap module).
The nuxt-simple-robots module offers many important features for end users and module integrations. Some of the ones I think that most useful:
For a comparison in usage:
Having multiple modules in the ecosystem that are tackling the same issue is good in my opinion, it gives the end user choice and encourages innovation. However, given that this robots module is "official" and it's one of the most downloaded for Nuxt, I feel we should be providing a single choice that provides delightful DX out of the box.
What Does Merging Look Like
Who WIll Maintain v4 Onwards?
I'd like to take over the the primary maintainer as I have most context on how the code is working, but would be amazing to have help in continuing to maintain the module.
The text was updated successfully, but these errors were encountered: