Posted on 19/11/2021 06:38:43
Yes, it's maybe a huge change but it's a powerful one :)
See the Direct Path is today a module with limited capabilities.
a) You can't really use it for "SEO 301 redirect projects" where you can map out a you old URLs index by google to a new re-structured site
- The module is not acceting any matching URL patterns
- The module can't really be used for domains that Dynamicweb doesn't have websites for say you have a website www.co3.dk and you wan't to redirect any URL comming in on m.co3.dk to www.co3.dk/mobile
b) Today we use the IIS rewrite module for our "SEO 301 redirect projects" for the exact reason that it is in front of the Dynamicweb execution pipeline but it is manual work to add them to the server and for some customers we have even developed Redirect modules that can read URL redirects from spreadsheets.
A new Direct Path module or let's say a new Redirect Module (with some new features) that sits in front of the execution pipeline could benefit us in these ways:
- Being less dependant on DevOps that can access the server and setup up rules and rewrite maps
- Being able to import entire rewrite maps into the database table
- Being able to support redirect rules per domain instead of per Dynamicweb website
- Being able to support any URL patterns with regexthat the system doesn't even
- When editors delete Items (page based), pages, products etc., Dynamicweb CMS could ask if you want a redirect added to point to a new page
Let me hear you thoughts.