Greetings,
So recently, just a matter of hours actually, the platform feedback root category was dissolved into two: bug reports and feature requests. (Let us have a moment of silence and leave our condolences for the previous category). Anyways, this is a nice addition as it sorts features vs bugs, however, #platform-feedback:developer-hub is incorrectly “shoved” into one of those categories where in reality the category should accept both features and bugs.
Plus the inconsistency widens where the category guideline states:
This category is for reporting issues and requesting new content and features for the Roblox Developer Hub, which is the place to find technical documentation and tutorials on Roblox development.
Currently, both the name “Developer Hub Issues” and its deliberate placement in the #platform-feedback category contradicts it allowing feature requests. This can incorrectly convey that it is only meant for bugs while the category guideline says the opposite.
Solution(s)
There are several ways to solve this:
- (Not the best method) Have another category for developer hub features. I don’t particularly like this since the “features” part is very niche.
- Place the dev hub category outside of the root category and rename it to “Developer Hub Feedback” or something. This is a much better method for many reasons:
- The DevHub is very unique to the other engine, studio, or platform features/bugs category, so it makes sense to separate it
- Including it as its own category means it can be categorized both as a feature and bug report category without actually choosing one of them
- The name itself doesn’t force it to be only “issues,” but rather UX and features as well
Thank you for reading,
And have a great day!