- The Vue Instance
- Template Syntax
- Computed Properties and Watchers
- Class and Style Bindings
- Conditional Rendering
- List Rendering
- Event Handling
- Form Input Bindings
- Reactivity in Depth
- Transition Effects
- Transitioning State
- Render Functions
- Custom Directives
- Single File Components
- Production Deployment Tips
- State Management
- Unit Testing
- Server-Side Rendering
- TypeScript Support
- Migration from Vue 1.x
- Migration from Vue Router 0.7.x
- Migration from Vuex 0.6.x to 1.0
- Comparison with Other Frameworks
- Join the Vue.js Community!
Join the Vue.js Community!
Vue’s community is growing incredibly fast and if you’re reading this, there’s a good chance you’re ready to join it. So… welcome!
Now we’ll answer both what the community can do for you and what you can do for the community.
- Forum: The best place to ask questions and get answers about Vue and its ecosystem.
- Gitter Channel: A place for devs to meet and chat. You can ask questions here too, but the forum is the better platform, since the discussions are threaded.
- Github: If you have a bug to report or feature to request, that’s what the GitHub issues are for. We also welcome pull requests!
- The Awesome Vue Page: See what other awesome resources have been published by other awesome people.
- The “Show and Tell” Subforum: Another great place to check out what others have built with and for the growing Vue ecosystem.
As with any project, there are rules to contributing. To ensure that we can help you or accept your pull request as quickly as possible, please read the contributing guide.
After that, you’ll be ready to contribute to Vue’s core repositories:
…as well as many smaller official companion libraries.
Apart from answering questions and sharing resources in the forum and Gitter channel, there are a few other less obvious ways to share and expand what you know:
- Develop learning materials. It’s often said that the best way to learn is to teach. If there’s something interesting you’re doing with Vue, strengthen your expertise by writing a blog post, developing a workshop, or even just publishing a gist that you share on social media.
- Watch a repo you care about. This will send you notifications whenever there’s activity in that repository, giving you insider knowledge about ongoing discussions and upcoming features. It’s a fantastic way to build expertise so that you’re eventually able to help address issues and pull requests.
Vue has already spread across the globe, with even the core team in at least half a dozen timezones. The forum includes 7 languages and counting and many of our docs have actively-maintained translations. We’re very proud of Vue’s international reach, but we can do even better.
I hope that right now, you’re reading this sentence in your preferred language. If not, would you like to help us get there?
If so, please feel free to fork the repo for these docs or for any other officially maintained documentation, then start translating. Once you’ve made some progress, open an issue or pull request in the main repo and we’ll put out a call for more contributors to help you out.