No problems, I can explain here. This was done since the intent was to allow the dashboard to be reused in alternate locations and domains where we don't know yet what the subdomain will be. It could be a domain identifier that isn't what the user wants the cosmetic display name to be. Having this map provides that flexibility. Rather than having to create multiple special exceptions in the parsing of a lone urlVal.

A small example of this already is "addons", where the legal/sanctioned term for cosmetic use appears to be "Add-ons" given the [Mozilla website](https://addons.mozilla.org/en-US/firefox). Hence the titleId "Add-ons". The same is true but in a different way for "ondemand", where grammatically the title is correct to say "On Demand".