Guidelines

On this page, I’d like to introduce a few coding and content presentation rules that I’ll be following throughout this publication. These guidelines are designed to make the content clear, structured, and beneficial for your learning and development.

Here you can read a bit more about me and this blog as it is.

The Type of Content

This blog is meant to be a practical, hands-on journey into Vue & Nuxt - think of it as a seminar rather than just another tutorial series. I'll break things down step by step, starting with the basics and progressively diving into more advanced techniques and optimizations.

Don’t worry if something isn’t covered right away - this is all about building up knowledge gradually. Along the way, I’ll not only show you how things work but also why they exist and how they fit into the bigger picture.

TypeScript

Vue and Nuxt are fully built with TypeScript, and I’ll be using TS as much as possible throughout this publication. TypeScript brings structure, type safety, and a more professional coding experience, helping to catch bugs early and improve maintainability.

If you’re not using TypeScript daily, I encourage you to get familiar with it. But don’t worry - I’ll provide intermediate guides along the way, covering types, interfaces, and useful utilities to help you to understand and integrate TypeScript smoothly into your development workflow.

pnpm

I'll be using pnpm as the package manager here. It's fast, powerful, and makes managing repositories much easier. However, you can always use your preferred package manager, such as npm or Yarn - just adjust the commands accordingly.

Code Examples

Substack isn’t very generous when it comes to code presentation - its capabilities are quite limited. To keep things clear and readable, I’ll be providing code examples as images for better formatting. Additionally, I’ll include GitHub Gist links so you can easily copy the code.

For short commands and one-liners, I’ll sometimes use native code blocks instead of images, as it’s not always necessary to generate visuals for them. If you find any of these formats problematic, please let me know - I want to make sure the content is as accessible and convenient for you as possible!

Finally, I truly believe that the best way to learn something new is to write it from scratch rather than just copying code mindlessly. When you type things out yourself, you remember more, get a better feel for the syntax, and learn how to handle unexpected errors or issues along the way.

Try to follow along with the images and examples, and if needed, you can always check the source files that will be available. But most importantly - write the code yourself and make it your own!