I've read https://talk.observablehq.com/t/bug-report-local-anchor-link/ and https://talk.observablehq.com/t/in-page-links/ but blindly transferring the code snippets in to enable jump-to for internal links doesn't seem to be working. Any ideas?

If you facing these issues in Firefox likely due to their new Site Isolation feature. https://github.com/observablehq/feedback/issues/294

what links don't work? The ToC? Those links should already work.

No, an in-text hyperlink starting with #anchorname

And it's chrome that I was using. I want to cross-reference further sections in text using markdown.

Here's a workaround: ``` { const onclick = e => { if(e.target.tagName !== 'A') return; const href = e.target.getAttribute('href'); if(href.startsWith('#')) { const t = document.querySelector(href); if(!t) return; e.preventDefault(); t.scrollIntoView(); } }; document.body.addEventListener('click', onclick); invalidation.then(() => document.body.removeEventListener('click', onclick)); } ```

:) Thank you!!!

Is it possible for designers to (re-)deploy surveys to CloudFront?

The cannot redeploy the application code (e.g. adding a new component type), but they can publish a new version of a survey (reworded and reordered questions, change of titles).

Is it accurate that in this case, the 'public' bucket serves a similar role as a 'edge router' in a traditional server architecture? I.e., completing the handshake with the public encrypted end user credentials confirms user role and subsequently provides user application access according to assigned permissions?

normally I think of edge servers as terminating an SSL (HTTPS) connection nearer the user. So encryption is used, but not tied to a user usually. Also the idea of edge servers is you have lots of them, so traffic is terminated near the user, we do not multiple regions, except that many of our underlying AWS resources are already multi region. I feel like our public buckets provide credentials that allow user to initialize and authenticated session with auth-server. I would still say AWS is running the auth-server though (IAM). Where has this description come from? Is this for a security review?

Oh, no - it was a question from me in trying to understand the architecture. This clarifies. Thank you!