It’s a little difficult without full screenshots to know what’s going on, and what you are binding.
You would typically pass the url parameters via a $GET to then run the a DB Query to get an output, e.g. like ‘CardDescription’ - this would then render in the browser.
It looks like you are binding the query parameter from the query manager - is this not working when you render in a browser, or with dynamic data turned on?
Without knowing your use case:
I have url parameters setup like you do in routing, I then setup the parameters in the query manager. In the server connect file, I add these as $GET then I click on the server connect in the AC and add the Query Parameters in there from the URL.
With that data, I then run queries on the server side, and bind that data to the page.
It’s worth noting - I had lots of issues with a similar url parameter structure - but I don’t know if it would be the same for you.
E.g. /:lang/:type is seen merely as :param1/:param2 by Wappler, so if you swap around :lang and :type, it makes no difference.