#1 Nuxt.js Writing Adventure! 🚀✨
Crafting Code and Prose
I’m delighted to share this exciting news with you! I’m officially announcing my venture into writing a comprehensive guide titled “Nuxt Your Everyday Vue.js” ✨ 👈 This title may very well change by the time I finish. But nonetheless, this is going to be a Nuxt.js book 📗
Nuxter’s Corner
I want this Nuxt book to be what I wish I had when I started off with Nuxt back in 2017 and hope to cover topics that Nuxt beginners may encounter on the job - in the real world. So, if you are thinking about topics such as Headless CMS, E-commerce and Authentication alike - then yes, this book might be for you.
At the same time, I want to include the fundamentals of Nuxt.js - where we learn Nuxt basics in regards to what happens during runtime and build-time vs client-side and server-side, auto-imports and aliases, Vue vs Nuxt, Nuxt and TypeScript, app config vs environment variables to name a few.
I published this 👇 diagram a while ago and it has been a guiding light for me when I am planning the Nuxt Fundamentals part of this book.
With this in mind, here’s the high-level parts of the book that I am pondering over these days:
Nuxt Fundamentals
Nuxt Customisation Touchpoints
Backend Nuxt (Nitro)
Frontend Development - Common Parts
Nuxt By Examples
Deploying Nuxt
I think the most challenging part of writing Nuxt basics has been to make sure it does not read like a documentation! This applies to the book’s Table of Contents (TOC) as well. While I author the topics that I am sure of, I am also spending some time trying out different TOC structures to get the feel for this book - to see if it maintains a reader-friendly flow - to see if it makes sense in case readers skipped a few chapters in-between - to see what value it’ll add to the whole project.
Overtime, I will plan and share the detailed content structure of each part. Doing this will keep me accountable to complete this project as well.
Author’s Corner
This project isn’t just about Nuxt - it’s a journey into the world of technical book writing and self-publishing as well. Self-publishing aspect of this project makes it all the more exciting. At least for me 🤷♀️
I have chosen ASCII Doctor as a tool of my choice to author this book. As I am navigating the landscape of writing a technical book, I am learning a lot - from formatting book parts, chapters, pages to creating front and back book covers. Here’s the sneak peek of the initial cover designs I am tinkering with in Affinity Design.
ASCII Doctor is an open-source, Ruby-based text processor that parses the markdown and converts the output into a book-like PDF format. So I am also learning a bit of Ruby basics to customise certain aspects of the book.
I am starting this newsletter with a hope to share all that I am learning and the process of authoring a technical book. I am using Nuxt.js as the canvas for my exploration, hope this inspires you to write your own one day! When I have tangible results to share, I will share behind-the-scenes stories about how I achieved specific book features using ASCII Doctor.
🚀 How You Can Participate:
📚 Read Along: Subscribe to the newsletter to receive updates, diagrams, and behind-the-scenes content.
🤝 Community Interaction: Share topic suggestions for the book, questions, and insights here on NuxtDojo Substack.
🚀 Spread the Word: Let others know about NuxtDojo – share on social media and among your developer circles.
nuxtdojo.com
