docs: explanation about sitemaps in headless WordPress

[theodesp]

closes #50

[colinmurphy]

LGTM @theodesp 🚀 🚀 🚀

[moonmeister]

I like the overview and the introduction of the problem. I like how each solution has clear pros and cons. The three solutions need a little work. 1 is new to me, I haven't heard of it before, have you seen others do this method? I'm open to it but seems a little strange. The three methods documented in the RFC #17 that we need to comer here are:

1. Proxying the sitemap from the front end to the back end. - https://github.com/wpdecoupled/site/tree/main/src/routes/%5Bfile%3Dsitemap%5D
2. Generating a sitemap from GraphQL content (you cover this with 2/3...but static VS SSR is not a "separate" method...just a different rendering strategy. - https://github.com/wpengine/faustjs.org/blob/main/src/pages/wp-sitemap.xml/index.jsx
3. Fetching existing sitemaps and and parsing them into a new sitemap with any added framework routes (the current faust method)

[ahuseyn]

@theodesp @moonmeister, the problem with the 2. approach (WPGraphQL) is that WPGraphQL returns maximum 100 node per page. If you set first: 1000 it will only return the first 100. Details: https://www.wpgraphql.com/docs/known-limitations#pagination-limits

You can increase that limit but it may cause problems for the WP instances low on resources: https://www.wpgraphql.com/filters/graphql_connection_max_query_amount

[colinmurphy]

LGTM 🚀 🚀 🚀

[whoami-pwd]

Looks good!

[moonmeister]

looking really close. just had a couple clarifying questions needed on some of the code examples