chore: Create list of Headless WP Issues

[moonmeister]

We want to create a living list of WP features that are difficult to use in a Headless architecture.

I'm sorry to the public who don't have access to some internal things. Feel free to comment on what you find hard in Headless WP. We'll put the final list here for all to see.

Issues List (WIP)

• Absolute URLs - WP Often embeds Absolute URLs in content that doesn't correctly point to a headless front-end
• Content Previews - WP Post Previews are broken cause WP is no longer in control of the front-end (ACF specifically is extra impossible)
• RSS Feeds - WP native RSS feeds are unusable by default in the front-end (adding /rss for every route doesn't just work).
• Lack of front-end control
  • SEO: SEO plugins don't embed the goods cause they can't control the front end and sitemaps are on the backend
  • Forms: lack of clarity and easy plug-n-play forms
  • Comments: they're hard implent
  • Redirects: plugins SEO/standalone redirects can't redirect
  • WP Head/Footer concepts don't exist in headless
• Content: WP Developers don't know where to turn for HWP docs and support.
• Menus: How to build Meus, Public/private with Location issues, FSE/Blocks mean Menus are technically a legacy feature
• Private Content: WP auth system lets plugins control content to specific users based on payment/membership/etc
• Application Access: some APIs could/should be authenticated but are often left public due to lack of auth methods
• Content Styling: Blocks especially provide a lot of power to layout content, but getting the styles/JS into the front-end app proves difficult.
  Media in Content: Media embedded in content often needs custom parsing to optimize with modern frameworks like NextImage. Is media slow-serving because it is not on specialty CDNs?
• Short Codes: Don't process in API responses
• Muli WP Sites: Whether Multisite or not managing a JS client working across multiple rest/graphql APIs can be difficult
• Opinionated Routing: Unlike most headless CMSes WP has opinions on how routing should work via Permalinks. Keeping this in sync with the JS front-end can be cumbersome. For example, creating a new post type using JS routing would require adding a new route to your front-end app. Relying on WP for routing means that new Post type can use an existing template.

Working Docs

• David Notes
• Colin Notes
• Iona Notes
• Current Faust Features