-
Notifications
You must be signed in to change notification settings - Fork 51
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feature/virtual sitemap #119
Conversation
Codecov ReportPatch and project coverage have no change.
❗ Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more. Additional details and impacted files@@ Coverage Diff @@
## master #119 +/- ##
=======================================
Coverage 89.02% 89.02%
=======================================
Files 2 2
Lines 82 82
Branches 32 32
=======================================
Hits 73 73
Misses 9 9
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
We are considering discontinuing the use of this library because we have been hit with multiple SEO penalties as a result of the sitemap malfunctioning without our knowledge. However, this new feature seems to be a game-changer. Can you provide an approximate release date for it? |
No, #97. |
What does it do?
Implements a "virtual sitemap".
Prior to this PR the sitemap files were written to the public folder of your Strapi app.
Though this PR introduces a new public API endpoint that will serve a sitemap that is cached in the database.
Why is it needed?
It allows you to use this plugin even if you're not able to write to the file-system.
Also it opens up possibilities for better caching, chunking and
How to test it?
Related issue(s)/PR(s)
#84, #89, #106, #97