Closed Paillat-dev closed 4 months ago
Hallo @Paillat-dev,
thanks for the feature request.
The plugin is ready to write own plugin or callback to generate a tree of the used resources.
verbose: true
options to display all processed resources in terminal outputmanifest
. Easily you can adapt it to generate a sitemap.xml
.Тo be honest, the last time I generated a sitemap.xml
was more than 15 years ago ;-)
Who use it today?
I mean I would answer myself, but more seriously, it is still somewhat relevant for search engines, and cand speed up indexation quite a bit when it's used, at least from what I noticed. I'll see what I can do with that and maybe reply here, or even open a pr. Thanks for the info!
The only thing that is not contained in the list are static resources that have not been processed and links to pages. But it can by crawled and tricky cached using the sources option.
@Paillat-dev can be closed the issue or you have questions for topic?
@webdiscus I didn't do it in the end. You can close if you want.
Feature request
What is motivation or use case for adding/changing the behaviour? Having an option to have the plugin generate dynamically a sitemap.xml file containing all files / all files matching some criteria.
Describe the solution you'd like I don't really have any syntax idea.
Describe alternatives you've considered Just doing it manually, it's okay as long as there aren't too many pages.