In #4908 @philsward suggested that there was a need to implement the same feature to include taxonomy terms:
Taxonomies are used for a lot more than tagging content; for example they can be used as select lists. This means that currently, any taxonomies that you don't want to be indexed, have to be added as a disallow to the robots file. ... The architect could opt to remove the path field so there is no "public" alias.
In #100 we introduced a "Hide path display" checkbox in the "Display settings" tab when configuring a content type:

The Drupal version of the contrib module that offers this functionality already supports more entities:
Supported entities
This project includes sub modules that are responsible to add this behavior to different entities. The currently supported entities are:
- Nodes
- Taxonomy terms
- Users
- Files
- Field collection
- Profile 2
- Bean
You'll only need to enable the modules that you wish to add the functionality for. More entities are likely to be supported in the future. If you have a suggestion, submit a feature request using the issue queue.
I think that we should extend this feature in core to support more entities, at least taxonomy terms.
Recent comments
I think this is the best gift you can give designers—just design, create a new distribution, and get creative with Backdrop.
Add 'recipe' project type to Backdrop
@yorkshirepudding thank you for the additional info on improving discoverability and a handy way to keep a list of projects for reuse.
Why not add a Github star?
It is a good point @izmeez and when I was researching repo discoverability I found that GitHub search does prioritise matches with more stars. This is what I was researching for:...
Why not add a Github star?