Now, I do believe this explanation is a core part of what people miss that ends up making Git/GitHub feel more daunting than it is: it can be explained quickly, simply, and it makes a big difference in whether someone understands or just runs commands.It was just in the wrong place.

For a book like this, "deliver on your promise as soon as humanly possible" means the time from first word to cloning the repo and seeing the fun web shrine on your laptop must be as short as possible. Plus, if the reader hasn't seen GitHub in action, the explanation has nothing to really "latch on" yet.

And so... off to the extra chapter on "multiple remotes" it goes! I keep going back and forth on whether this issue can reasonably cover e.g. "forking a repo" (which would slot well with "multiple remotes"), but... well, there's a reason "plan extra chapters is unchecked. I'll keep pondering.

Other bits: one big "make sure you've done the prework" upfront (not throughout) for less interruptions, the middle problem I thought I had (convoluted example) was likely a different one (example needs repositioning)... but overall the clone → push → branch → merge → conflicts narrative WORKS! ✨

Next up, I'll be reorganizing chapter 1.

------ ✨ AND THAT"S ALL ✨ ----

If you're interested in knowing when this guide goes on sale (sometimes this year 👀) sign up to be notified 👉 https://www.fujoweb.dev/volume-0 👈 (TBPolished) and follow @fujowebdev for updates!

In the meantime, I'll keep posting throughout this rearranging as we get ready to set up our second beta 💪

As my favorite book on writing non-fiction (https://www.usefulbooks.com/learn/forgo-frontmatter) says, it's important to "deliver on your promise as soon as humanly possible": this means drop the reader in the middle of the action then get yourself out of their way.

I knew from feedback + gut feel that this GitHub issue was doing a poor job.

Re-reading it *definitely* confirmed my suspicions. I had already started moving some of the setup from the book into our free learning platform (https://learn.fujoweb.dev/), but there was more to do. One big culprit was spending too much time upfront explaining remotes and the "hub" model.