And so on, with a limit of 2000 results per sitemap.
Remove users if no or all sportstacks from the user are draft from the sitemap.
Implement route guards in SvelteKit to control access to users and sportstacks. If all user sportstacks status is draft, redirect users to a 404 page or a relevant message.
If a user is deleted, all sportstacks related to that user should change their status to draft and remove them from the sitemaps.
===
Use the table:
articles_update
An event should run with the sitemaps process whenever an article is created or update, this way the sportstacks and user sitemap status will be reviewed.
### Important:
Add a cycle to the cancelation user request from the user to change the Sportstacks status. This is done at the present time in the profile section.
Does a duplicate issue exist?
🤔 Is feature request related to a problem? Please describe the problem.
No response
📝 Feature Request Description
📝 Feature Request Description
Sitemap and Visibility Management:
Dynamically update the users and sportstacks sitemaps.
Users:
https://sitemap.betarena.com/static/sitemaps/author/user/user-0.xml
Sportstacks:
https://sitemap.betarena.com/static/sitemaps/author/sportstack/sportstack-0.xml
And so on, with a limit of 2000 results per sitemap.
Remove users if no or all sportstacks from the user are draft from the sitemap.
Implement route guards in SvelteKit to control access to users and sportstacks. If all user sportstacks status is draft, redirect users to a 404 page or a relevant message.
If a user is deleted, all sportstacks related to that user should change their status to draft and remove them from the sitemaps.
===
Use the table:
articles_updateAn event should run with the sitemaps process whenever an article is created or update, this way the sportstacks and user sitemap status will be reviewed.
### Important:
Add a cycle to the cancelation user request from the user to change the Sportstacks status. This is done at the present time in the profile section.
➕ Further context and resources (cummulative)
No response