Propose new functionalities for Decidim software
#DecidimRoadmap Designing Decidim together
Is your feature request related to a problem? A clear and concise description of what the problem is.
Client get frustrated that we don't have a simple way to generate an .xml sitemap for Decidim websites. It's recommended for SEO.
Describe the solution you'd like
On a multi-tenant Decidim instance I may not want to generate a sitemap for all orgs as some maybe used for private purposes (ex: "Force users to authenticate before access organization")
As a system admin, I'd like to have a config flag in /system in the org edit form to choose to generate an .xml sitemap for the org I'm editing.
We could use an existing gem like https://www.ruby-toolbox.com/projects/sitemap_generator to generate the site map.
The sitemap generator would need to exclude :
- /admin and /system links
- Private spaces links
The sitemap needs to be be
- frequently updated → a cron job can run periodically
- and sent to search engines → We need to decide if we leave the responsibility to the admin of the org or if we try to ease up the process a little bit for them. We could use this gem https://www.ruby-toolbox.com/projects/pingr so that the pinging to search engine is automated
Describe alternatives you've considered
At this stage I'm wondering :
- if this feature could be of interest to the rest of the community. If not we can always make a module;
- what's the best way to generate a xml sitemap for a Decidim site;
Additional context
Add any other context or screenshots about the feature request here.
Does this issue could impact on users private data?
No
Funded by
Possible funding by Lausanne
Report inappropriate content
Is this content inappropriate?
Comment details
You are seeing a single comment
You can check the rest of the comments here.
I would see this useful feature to have in Decidim.
Regarding the questions, right now I believe there is no simple way to generate the sitemap automatically as Decidim does not centrally store anywhere the records that can be referred to in public URLs. Probably each component and each participatory space would have to implement the sitemap link generation specifically to that component/space + all static pages, so it would require changes in all components. You could potentially parse through all the URLs available in Decidim but you wouldn't cover individual resources (e.g. all proposal IDs) doing it like that.
Also instances that do not allow public access can have publicly available pages which could be included in the Sitemap. Of course, most of the resources should not be added to the sitemap.xml on those sites.
Loading comments ...