Advance routing challanges with url rewrites handled by the cms

[antonioberetini]

We are building and appp using next with our own cms which is handling url rewrites history. As pages change a url path we store historical changes in the DB. The intent is to allow old url links to still be resolvable to the latest destination while passing propped redirect seo codes. We implemented this using custom router before the latest version came out. I am looking for someone who is will to port our logic to our of the box functionality on per project bases

Hit me up it's pretty urgent.