A boilerplate namespace can work fine, e.g. (after NS_BOILERPLATE and NS_BOILERPLATE_TALK have been defined), instead of
* Generic page|Template:Generic page
have
* Generic page|Boilerplate:Generic page
A boilerplate namespace can work fine, e.g. (after NS_BOILERPLATE and NS_BOILERPLATE_TALK have been defined), instead of
* Generic page|Template:Generic page
have
* Generic page|Boilerplate:Generic page
What is your use case? Do you have so many boilerplates? I'm asking because a lot of extenasions define namespaces, and their numbers tend to collide over time, so if there's no real need, I'd rather not define a new namespace.
Only that it seems tidier to me. I've a handful of boilerplates but many templates. I suspected there might be a reason for caution.
It's not that much of an problem, I'm just not sure it's worth it. Since both Special:Boilerplates and Special:PrefixIndex allow you to find all of your boilerplates, the current setup isn't really messy.