[docs] Concept: secret quick-copy for links from search results (#23948)

# Why
I copy links from the docs dozens of times a day for support responses,
Discord, etc., and I'm sure I'm not the only

[docs] Concept: secret quick-copy for links from search results (#23948)

# Why
I copy links from the docs dozens of times a day for support responses,
Discord, etc., and I'm sure I'm not the only one. I typically memorize
what search results give me what links. I don't need to watch the search
result page load, except so that I can copy that link. So, I was
wondering... what if I didn't have to? What if I could get the link
without ever leaving the search results?

I'm not very confident this is right way to do it, so I wanted to ask
(in the form of the PR), does anybody else want this? And what would be
the right way to do it?

# How
I've been using Linux a lot lately, which is big on
copying-via-middle-click. Unfortunately, macOS doesn't have
middle-click, so, it would have to be right-click, so all I did was
suppress the context menu when right-clicking on a search result.

If it worked like this, IMO it'd be better with some actual feedback,
like a toast. Or it could be something like this copy feedback:

(just didn't want to go too far without feedback on the concept itself)

Is there another sort of secret shortcut that could work? Like a
keypress + click?

# Test Plan

<!--
Please describe how you tested this change and how a reviewer could
reproduce your test, especially if this PR does not include automated
tests! If possible, please also provide terminal output and/or
screenshots demonstrating your test/reproduction.
-->

# Checklist

<!--
Please check the appropriate items below if they apply to your diff.
This is required for changes to Expo modules.
-->

- [ ] Documentation is up to date to reflect these changes (eg:
https://docs.expo.dev and README.md).
- [ ] Conforms with the [Documentation Writing Style
Guide](https://github.com/expo/expo/blob/main/guides/Expo%20Documentation%20Writing%20Style%20Guide.md)
- [ ] This diff will work correctly for `npx expo prebuild` & EAS Build
(eg: updated a module plugin).

---------

Co-authored-by: Simek <[email protected]>

show more ...

[docs] Search: Expo docs results grouping (#23579)

[docs] Adds docs preview label (#20583)

# Why

We'd like the ability to add a label, then to have GitHub Actions build
the docs and deploy them on AWS S3, where we can preview them quickly
durin

[docs] Adds docs preview label (#20583)

# Why

We'd like the ability to add a label, then to have GitHub Actions build
the docs and deploy them on AWS S3, where we can preview them quickly
during PR review.

This PR adds a GitHub Action (GHA) that gets triggered when added the
"preview" label. The GHA exports/builds the docs and then uploads them
to AWS S3. Then, it comments on the PR with a link to the preview URL.
When merging a PR, another GHA runs to clean up and delete the bucket
that was created when adding the label.

Closes ENG-5683

# How

- Added a `AWS_BUCKET` field to our **deploy.sh** to specify the bucket
to deploy to.
- Edits the search inside the docs to replace `docs.expo.dev` with the
preview URL if the docs are hosted on an aws-style URL.

# Test plan

You should see the docs preview website on this PR! Go check it out.

Also, I opened another PR on top of this one where I confirmed both
pr-deploy and pr-destroy steps (on label add, remove, and merge). See
the screenshots in the comments on this PR:
https://github.com/expo/expo/pull/23545

show more ...