[experimental]: PoC sitemap feature
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 1.6k
- Forks
- 155
- Avg merge
- 1d 18h
- Merged PRs (30d)
- 20
Description
New Faust should have a customizable sitemap feature. The data fetching strategy is yet to be determined. The options include paginated GraphQL requests, a proxied sitemap, or an approach involving the custom-sitemap-apollo from hwptoolkit.
Tasks:
- Provide a sitemap endpoint (e.g., /sitemap.xml) in Faust.
- Provide utilities to fetch published content (posts, pages, custom post types) from WPGraphQL.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the linked discussion and the three referenced examples: custom-sitemap-vanilla-wpgraphql, proxied-sitemap-apollo, and custom-sitemap-apollo. Determine the data-fetching approach and the Faust entry points involved, then verify that the resulting feature exposes a sitemap endpoint such as /sitemap.xml and provides utilities for published posts, pages, and custom post types.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- graphql, next.js, typescript
- Domain
- api, backend, web-dev
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100