Nick delves into the intricacies of technical book writing with authors Adrienne Braganza Tacke and Dylan Hildenbrand. We talk about the process of working with a publisher, coming up with an outline, actually writing the book, and everything that comes after the book is finished.
Matched from the episode's transcript 👇
Dylan Hildenbrand: Very nice. Yeah, so I was also approached by a publisher. One of my earlier roles in web development was actually for an advertising agency building WordPress themes for their clients. Customers need websites, and they need to advertise, and so I was the one who was making the websites happen. When I started that, I realized I quickly needed to learn more about WordPress, because I had no experience with it at the time… And so I spun up an old Pentium 2 PC that I had hanging out in one of my closets, I threw a lightweight Ubuntu distro on there, and I put WordPress on it and I started tinkering and tinkering. And I’ve been tinkering on that same installation for 10 years now, and that’s where I write closingtags.com, which is my blog about web development. It’s mostly just content that any problems I come across and solutions I come up with, I say “Hey, this would be a great blog post”, because I’m constantly finding other people’s blog posts. It’s mostly there for documentation for myself, and I have comments enabled, which is great when people say “Hey, this really helped me. Thank you.”
And so I’d written a post about getting global CSS in SvelteKit. At the time, SvelteKit wasn’t out of beta yet, so we’re not even in SvelteKit 1.0, and there wasn’t a defined method for doing this outlined in the documentation yet. I’d come up with a relatively hacky strategy, and written about it, and it got a lot of traction. It’s one of my most viewed posts on the site to this day, even though it is now incorrect. I’ve put a little disclaimer at the top of the post saying “By the way, Rich Harris said don’t do it this way. Do it this way instead.” But it happened to land in GitHub issues where a lot of people were saying “Hey, how do I do this?”
[10:04] Somebody linked to it, and from there, a publisher came across it, and they reached out to me and said “Hey, we want a book about SvelteKit. Would you be interested in writing it?” And like Adrienne said, it seemed like “I don’t know, this seems a little bit scammy, because I got an email, and they’re like “You should write a book.” I was like “Yeah, that’s obviously a scam. Somebody doesn’t know what they’re asking…” But then I kind of dug into it a little bit more and realized “Oh, wait, this is how this publisher actually reaches out to people.” And so I kind of asked some questions, and I set up a call to make sure things were legit… It was totally legit, and the rest is history.