Hi @mistyn8
I don’t think an IContentFinder is the correct approach here either, but that’s the choice @Eaglef90 has made and as I mentioned in his other thread, a view component would be more suitable.
https://forum.umbraco.com/t/give-document-node-custom-routes-but-keep-default-route/8547
My reply about separation of concerns was about avoiding parsing the URL in a template as that’s not rendering logic. If he wants to use an IContentFinder then the template still needs to know about the original URL if he wants to use those parameters. Obviously without seeing his code or knowing his requirements, we are just trying to give our best advice based on what is asked here.
No doubt we could debate all day about the right or wrong approach, but ultimately I think that is just going to muddy the waters even more for @Eaglef90 and make things even more confusing.
Justin