docs(guides/single-fetch): add some recommended steps

[michenly]

Some recommended docs changes.

Feel free to edit on top of if as you see fix 🙏

[changeset-bot]

⚠️ No Changeset found

Latest commit: d0e4da4

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[remix-cla-bot]

Hi @michenly,

Welcome, and thank you for contributing to Remix!

Before we consider your pull request, we ask that you sign our Contributor License Agreement (CLA). We require this only once.

You may review the CLA and sign it by adding your name to contributors.yml.

Once the CLA is signed, the CLA Signed label will be added to the pull request.

If you have already signed the CLA and received this response in error, or if you have any questions, please contact us at hello@remix.run.

Thanks!

- The Remix team

[remix-cla-bot]

Thank you for signing the Contributor License Agreement. Let's get this merged! 🥳

[brookslybrand]

Thank you @michenly!

[brophdawg11]

I worry putting this section first will give the wrong impression - that folks need to make all these changes before they can enable single fetch because the order in which they'll read the doc is Breaking Changes -> Enabling.

Technically, I think the only thing they need to do to start using it is the fetch polyfill update. the rest of the "breaking changes" should be almost 100% backwards compatible and able to fixed incrementally after enabling the feature.

[brookslybrand]

Yeah, that's a good point, I agree. It also follows the flow in the overview

Remix introduced support for "Single Fetch"...

Enabling Single Fetch is incredibly simple...

Please also read through the Breaking Changes...

[brookslybrand]

Technically, I think the only thing they need to do to start using it is the fetch polyfill update. the rest of the "breaking changes" should be almost 100% backwards compatible and able to fixed incrementally after enabling the feature.

I agree, it's more about awareness of how it's effecting your code. The "Deprecated headers export" might be the only exception. You're right, it's not breaking, but if people are heavily using a CDN it's good to know how Single Fetch effects that piece.

[brophdawg11]

ah yeah good call - headers also needs to be updated to adopt

[brophdawg11]

Maybe we can more clearly delineate the breaking changes as "up front" and "iteratively after the fact"

[michenly]

If there is a concern I am 👍 with moving the block down. I originally move it up because the overview made a point of reading through underline changes and it had made sense to me that folk should understand what had really changed under the hood before using it.

[brophdawg11]

I can take a stab at this sometime today

[brophdawg11]

OK, I moved the breaking changes section back below and separated them by "up front" and "over time". Let me know if there's any last feedback and I'll get this merged today! Thanks!