The router should support URLs that contain a hash (#example).

I haven't researched this extensively, but my initial intuition is that it should not use the hash when fetching/caching (which is the current behavior), but it should display it in the browser URL and move the scroll to the correct item once the client-side navigation has finished. It could also support smooth scroll.