All broken links are now fixed, thank you!

Sorry if these notes aren't timely etc. Not sure how much reshuffling you're looking at. I think there are opportunities to simplify the narrative. Right now it's written a bit as if these are two very different things and you have to make painful tradeoffs between them. It doesn't quite come through in the text how they compose.

I think it may be nicer to explain client components as a way to "layer on" functionality. E.g. show replacing <div> with <ShowMore> or something. So that it feels like you're adding interactivity to your existing "skeleton" of server logic. Thus also starting with showing the composition pattern, and then showing leaves. Just an idea.

⚠️ No Changeset found

Latest commit: 361410b

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.

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

Good feedback, thank you @gaearon. It's hard to strike a balance between nuance and conciseness.

I intentionally kept it high-level, as it's part of the Getting Started section. But I'd love to explain the special cases in the future, perhaps in a deep dive.

Hopefully, these recent updates will help fight the sentiment that it is not a trade-off?

This is looking quite a bit better to me, thanks!