[docs] Update expo-dev-client and EAS Update guide to add info about Extensions tab

[amandeepmittal]

Why

Closes ENG-11705

How

This PR updates the Use expo-dev-client with EAS Update guide by:

• Adding info on what Extensions tab is and how it can be used to preview an update in a development build
• Move the Construct a specific URL into its own section
• Update introduction to match the contents of the guide and explain what this guide does for the reader
• Change title of "More" section to "Example" since it only provides a link to the GitHub example
• Change the title of this doc to "Load a published update with expo-dev-client and EAS Update" to match the contents of the guide
• Link to publish update guide from [docs] Add publish an update guide and other changes #27665 when it mentions about publishing an update
• Update BoxLink description to use inline code syntax highlight for the library name

Test Plan

Run docs locally and visit: http://localhost:3002/eas-update/expo-dev-client/ or see Preview: http://docs.expo.dev-pr-27772.s3-website-us-east-1.amazonaws.com/eas-update/expo-dev-client/.

Checklist

• Documentation is up to date to reflect these changes (eg: https://docs.expo.dev and README.md).
• Conforms with the Documentation Writing Style Guide
• This diff will work correctly for npx expo prebuild & EAS Build (eg: updated a module plugin).

[linear]

ENG-11705 Documentation needed for understanding the updates extension in dev client

[expo-bot]

📘 Your docs preview website is ready!

[quinlanj]

This example will construct a URL to show the latest update mapped by the preview channel. There's a bunch of different usecases you can build based on our www routes. Might also be worth saying you can get the update preview from the website like here . @jonsamp is currently working to revamp that page, where we'll want to eventually show you a preview QR for a single update group instead of the platform-specific QR we have right now. So we are eventually going to show something like exp+my-slug://u.expo.dev/:appId/group/:groupId. For context, the update group id can be obtained from the website here:

[amandeepmittal]

This example will construct a URL to show the latest update mapped by the preview channel.

Thanks for catching that! I've fixed it by changing it to development. In the table below, we're also explaining that the channel name is development.

here's a bunch of different usecases you can build based on our www routes.

Should we explain those use cases here?

Might also be worth saying you can get the update preview from the website like here .

Since we do not cover those steps, I've added a section for this:

@jonsamp is currently working to revamp that page, where we'll want to eventually show you a preview QR for a single update group instead of the platform-specific QR we have right now. So we are eventually going to show something like exp+my-slug://u.expo.dev/:appId/group/:groupId. For context, the update group id can be obtained from the website here:

Shall I wait for Jon to revamp this page to add those instructions on this page? I can create a follow up task for this.

[quinlanj]

Should we explain those use cases here?

No need, just wanted to float the www routes as an fyi (very few people know of it's existence)!

Your revisions look good, thank you!