Missing information on how to setup Lambda @Edge for SPA's

**Describe the content issue**:
One of the fundamental limitations of Single Page Apps is that they always return the same meta data to crawler's that don't render the page fully (ie. Facebook, X, etc)

The only way that works for large complicated websites is to setup a lambda @edge function that redirects to the function based on the client header...so you end up returning a dynamically created html file if from Facebook, but everyone else gets the static page from s3...this allows you to still have a fast website hosted in the CDN, but redirect specific clients to the function...where you can pull the needed data...

There is no information on the site on how to do this, it seems like there should be some docs on how to set this up.

The alternative of running a server rendered app is problematic for those who want the benefit of a SPA...

**URL page where content issue is**: