The official documentation for Vue.js is divided into several parts, spread across multiple websites covering different topics or core libraries such as Vuex, Vue-Router or SSR guides. All these pages have offline support and can be installed on a mobile phone.
The guide is commonly praised as one of the main reasons why new developers find Vue.js easy to pick up. It's usually the starting point for a developer interested in learning Vue.
If you need more details on specific features, use the robust search system or browse the API documentation.
Single File Components
However if you want to use
.vue files while learning, read the Single File Components chapter first and then start the guide from the beginning.
Remember to read the Reactivity in Depth chapter which provides ways to deal with some caveats of Vue.js reactivity system, related to working with arrays and objects. This will all be solved in Vue 3 release.
The Style Guide is a project meant to provide official best practices guidelines on how to write Vue.js code. It covers only the core library, without Vue-Router or Vuex.
It contains a few sets of rules to follow, based on their priority, with the Essential set considered a bare minimum to use in production. It's still recommended to at least know the other rules even if you don't plan to use them.
The Style Guide is accompanied by an ESLint plugin that allows you to enforce the use of specific guidelines. It comes out of the box with most of Vue related scaffolding tools, including Vue CLI.
While the role of the guide is to teach you how to use individual features of Vue API, the cookbook gathers curated recipes for common tasks and use cases.
It consists of separate chapters that focus on particular concepts, such as form validation or working with external API. It's still a work in progress and you're welcome to help with new recipes.
You're supposed to know the guide's content before you dive into the cookbook, the recipes may also assume knowledge of some build tools or packages from the wider Vue ecosystem.
Other than small code examples from the official website, there is also an example Github repository with a Hackernews clone that you can check to see how to write a real Vue.js application. It uses Vue-Router, Vuex, Server Side Rendering and API integration with Firebase.
If that is not enough for you, there's also a semi-official Vue-Enterprise-Boilerplate project, written by Chris Fritz, that showcases how you can use Vue.js in large scale applications. You can use it as a base for your new project too.
Other than the guides, there's also a repository with official roadmap, presenting the plans for the upcoming releases of core libraries. Like all plans, it's bound to change sometimes, so don't treat it as obligatory.
Vue core team has recently adopted RFCs (request for comments) as the main way of managing substantial changes to the core libraries of Vue ecosystem. Each RFC Pull Request is a great place for the author to properly explain their motivations, and gather feedback from users and core team. It is, then, a fantastic tool to be aware of possible new features and breaking changes, and also to understand the reasoning behind some decisions.