Hi,
for the sake of SEO. It is recommended that URL path params for a product
look like:
Example --
/../Category1/SubCategory2/SubSubCategory2/productDetails?name=SHOE123
Now, one stupid way of doing this could be to load every product in the
database by generating the link to it. However I feel thats too inefficient.
I'd simply like to define a Strategy /*/productDetails?name=SHOE123
... Where Wicket would not care what came before "productDetails" and
recognizes "productDetails" as the Page. The PATH PARAMS are merely a SEO
formality and not of consequence to the final Page loading.
Do I write my own strategy for this stuff or is there something Out of the
Box?
thanks
Software documentation is like sex: when it is good, it is very, very good; and when it is bad, it is still better than nothing!
for the sake of SEO. It is recommended that URL path params for a product
look like:
Example --
/../Category1/SubCategory2/SubSubCategory2/productDetails?name=SHOE123
Now, one stupid way of doing this could be to load every product in the
database by generating the link to it. However I feel thats too inefficient.
I'd simply like to define a Strategy /*/productDetails?name=SHOE123
... Where Wicket would not care what came before "productDetails" and
recognizes "productDetails" as the Page. The PATH PARAMS are merely a SEO
formality and not of consequence to the final Page loading.
Do I write my own strategy for this stuff or is there something Out of the
Box?
thanks
Software documentation is like sex: when it is good, it is very, very good; and when it is bad, it is still better than nothing!