I spend a fair amount of time looking at answers / questions specifically about Vue and the reoccurring trend is that more often then not questions are tagged using Vue 1.x tag which is <a href="https://stackoverflow.com/questions/tagged/vue.js" target="_blank">vue.js</a>.Whereas they actually meant to tag these questions as <a href="https://stackoverflow.com/questions/tagged/vuejs2" target="_blank">vuejs2</a>, as I post this the last three questions have both tags added inside <a href="https://stackoverflow.com/questions/tagged/vuejs2" target="_blank">vuejs2</a>:
I spend a fair amount of time looking at answers / questions specifically about Vue and the reoccurring trend is that more often then not questions are tagged using Vue 1.x tag which is vue.js.Whereas they actually meant to tag these questions as vuejs2, as I post this the last three questions have both tags added inside vuejs2:
This even has 2.0 in the title but still has only vue.js:
I could go on to post more but if you've answered questions in this tag more often then not one of the first actions you'll do when answering a question is to re-tag it with the correct tag or remove incorrect tagging. Another issue is when people post either 1.x or 2.x answers to either tag and or have to instantly clarify which version there actually using on occasion if the code snippets are not obvious.
I suppose I just wanted to highlight this and maybe open a conversation about how we might be able to change it so people are less likely to tag there questions incorrectly and to avoid providing incorrect answers.
The current guidelines for each tag are that all questions specifically targeted towards vue 1.x are tagged with vue.js and specifically vue 2.x questions are tagged as vuejs2. The wordage for both tags makes it sound like they are not supposed to co-exist whatsoever.
Related is this merge Merge tags: [vuejs] [vue.js] [vuejs2] [vue2] which left us with these two tags.
Related as it details the same symptoms I'm exsplaining here Retag the misused [vue.js]
Nuxt.js Content is a Git-based Headless CMS that allows you to fetch Markdown, JSON, YAML and CSV! in this video we look at how easy it is to setup. We also look at Nuxt auto-import components!
Responsive ecommerce template built with Vue.js and Nuxt.js
Nuxt js Laravel Authentication Tutorial Example. We use third-party package called Tymon to create json web token and sent back to the client for an auth.
In this article, Alexander Lichter (core Nuxt.js member) teaches you how to load third-party scripts in your Nuxt.js application. Both globally and on individual pages.