feat: add proxied sitemap example #136
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
theodesp
commented
Apr 8, 2025
theodesp
commented
Apr 8, 2025
examples/next/proxied-sitemap-apollo/example-app/src/pages/api/proxy-sitemap/[...slug].js
Show resolved
Hide resolved
theodesp
commented
Apr 8, 2025
...itemap-apollo/wp-env/plugins/custom-sitemap-url-adjustment/custom-sitemap-url-adjustment.php
Show resolved
Hide resolved
Co-authored-by: Huseyn Aghayev <[email protected]>
Co-authored-by: Huseyn Aghayev <[email protected]>
ahuseyn
previously approved these changes
Apr 15, 2025
colinmurphy
reviewed
Apr 15, 2025
ahuseyn
approved these changes
Apr 16, 2025
colinmurphy
approved these changes
Apr 16, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
This PR implements a solution for integrating WordPress XML sitemaps with a Next.js frontend. It allows WordPress sitemaps to be fetched, transformed, and proxied to a Next.js frontend. The domain replacement is handled by a custom WordPress plugin, which automatically adjusts the URLs before serving them through the Next.js application.
Reference
#48
Type of Change
✨ New feature (non-breaking change which adds functionality)
How Has This Been Tested?
The changes have been tested by:
Setting up the WordPress environment with XML sitemaps enabled and the custom plugin for replacing domain URLs.
Configuring a Next.js project to proxy and transform the sitemaps using the provided API route.
Verifying that requests for
/sitemap.xmland specific sitemaps (e.g.,/wp-sitemap-posts-post-1.xml) return the correctly transformed XML, with URLs pointing to the frontend domain (FRONTEND_URL).Testing in both local development (with FRONTEND_URL set to http://localhost:3000) and a custom environment by overriding the FRONTEND_URL.