The Vue.js teams announced and published an official Vue Cookbook to go along with the Guide. There are some differences between the aim of the guide and what the cookbook can do to expound on specific areas that are too verbose or don’t make sense in the context of the guide.
While the guide is a gentle introduction to Vue and it’s features, it cannot (nor should it) dive deeply into each and every topic around the Vue library.
This is where the cookbook comes in: a cookbook entry can have greater focus and greater depth on features. The cookbook can show more opinionated approaches to solving problems that grabs from various parts of Vue, combining them into a recipe for solving problems such as validation, consuming APIs with Axios, and others.
One of the coolest things about this project, IMO, is that we build up from small examples to more of a deep dive, but also cover alternative patterns! Web development choices frequently have tradeoffs, and we explore when and why you’d explore a different approach.
— Sarah Drasner (@sarah_edo) March 19, 2018
What Makes a Good Vue Cookbook Contribution?
According to the Cookbook introduction, this is what the Cookbook is all about:
The Cookbook gives developers examples to work off of that both cover common or interesting use cases, and also progressively explain more complex detail. Our goal is to move beyond a simple introductory example, and demonstrate concepts that are more widely applicable, as well as some caveats to the approach.
You can initiate a cookbook idea by submitting an issue on the vuejs/vuejs.org GitHub repository. Read through the Cookbook Contributions section to learn about the full process and outline you should follow once your idea is approved or inclusion in the cookbook.
Dive into the Cookbook and submit your ideas today!