Use of non UID type field about strapi-plugin-sitemap

[boazpoolman]

Hey @SalahAdDin

In strapi-plugin-sitemap ^2.0.0 you can use URL patterns.
In the pattern you can inject dynamic values.
Those can be ID's, UID's or any other field type.

See documentation here:
https://github.com/boazpoolman/strapi-plugin-sitemap#-url-pattern

[boazpoolman]

I think the best approach here would be to set a 'URL pattern' for each collection type you add to the sitemap.
This would be a text field in which you can inject some dynamic values based on the fields of the collection type.
Doing this, we could remove the 'area' field, as you can just add a prefix in the URL pattern field, which will simplify the form all together.

Example value:
/[langcode]/some-prefix/[some-category-field]/[some-uid-field]

I'm not sure as to which field types we should allow here other than id and uid fields. Seems like it would be handy to allow a relationship field like category, but how will we then specify which field of the category type we should use in the URL? Something to think about.

[boazpoolman]

Regarding the inclusion of relationship fields in the URL I'd suggest for now at least we also only allow the ID and UID type fields of the relationship. This way we will ensure the URL will consist only of fields which are actually usable in a URL (no spaces e.g.).

[boazpoolman]

This is now in the develop branch, will be released with the next minor/major release.
You are able to test this like so:

yarn add boazpoolman/strapi-plugin-sitemap#develop
npm install boazpoolman/strapi-plugin-sitemap#develop

[boazpoolman]

Released in v2.0.0 for the Strapi v4 version of strapi-plugin-sitemap.

[SalahAdDin]

@boazpoolman so, right now we can use slug for create the sitemap, right?