Overriding routes with Views

Views can replace administrative pages with enhanced versions due to the way the route and module system works in Drupal. Modules are executed in order of the module's weight or alphabetical order if weights are the same. Naturally, in the English alphabet, the letter V comes toward the end of the alphabet. That means any route that Views provides will be added toward the end of the route discovery cycle.

If a view is created and it provides a route path, it will override any that exist on that path. There is no collision checking mechanism (and there was not one present in Views before merging into Drupal core) that prevents this.

This allows you to easily customize most existing routes, but, beware that you could easily have conflicting routes, and Views will normally override the other.