Hi,

Would you be interested in a PR adding Quasar Framework to the content under Component Frameworks?

Scott

What is left to do on page

• Page Structure
• Static file hosting
  • Firebase
  • Surge
  • Now
• Traditional Hosting
  • Heroku
  • Digital Ocean

What exists on the page

• Rough page skeleton
• Content

Content is mostly added, we are missing short explanations for:

• Scotch
• FE Masters
• Codecourse
• Tutsplus
• Pluralsight

I noticed that the guide doesn't show the card on Twitter. It would be nice if it did.

It would be lovely to have the logo show up when we link to chapters on social media or chat platforms. This is how it works at the moment.

https://twitter.com/gustojs/status/1263486612392075271

Most of the "How to learn Vue" page is done, but the Coming from other technology section is really lacking.

If anyone, that has professional experience in the mentioned technologies there can contribute, please do. I would otherwise have a very hard time filtering out the proper info.

FE Frameworks

• Angular
• AngularJS (Angular 1.x)
• React
• Polymer
• No framework - jQuery

BE Frameworks

• Express
• Koa
• Adonis
• Laravel
• Ruby
• Django
• .Net

I am not sure how this will look on pages with only tutorial links.

We should reorganize the sidebar to make it a bit easier to scan. Add another level of navigation.

On the static site generators page, there are more SSG's listed than are show in the Summary(TLDR) section. The other SSG's listed further down the page either need to be added to the existing categories, or put in their own

This page should give links to the most popular i18n solutions as well as links to tutorials and so on.

• Vue-i18n
• Vuex-i18n
• Vue-i18next

Others to be added.

We're leaving VueJobs section for Israel and Jilson, so the content inside is temporary.

We did a lot of changes to the structure of Job Market chapter, so some of the stuff lost its original place. These are some random paragraphs that were previously written and can be incorporated or rephrased when needed:

Compared to React and Angular, Vue is entirely Open Source and community driven. On the other hand, the framework has shown an incredible growth in both popularity and adoption on the past year with no signs of slowing down.

The lack of a large company backing Vue is the First thing companies point at when being offered Vue for their projects. Compared to React and Angular, Vue is entirely Open Source and community driven,
with big decisions being made by the whole community. The framework has shown an incredible growth in both popularity and adoption on the past year with no signs of slowing down.

Vue's progressive nature means it can be embedded to both fresh projects and those that are already in production, written with various other javascript libraries in mind.

It has a very live and evolving social community, where people constantly share technical posts, ask questions, share ideas and organize meetups.

Among the many smaller companies, Vue.js is used in big companies like Gitlab, Adobe, Alibaba and more. Check Montreal's article on [State of Vue 2017]() where they go into much more detail on how and why those large companies chose Vue for their projects.

I wasn't really sure how to title this.

We're working on a project for Vue Land (the bot) and we need some data relating to popular libraries and frameworks for one of the commands (library/framework lookup).

@gustojs and I were talking about it an hour or so ago in #library-maintainers and he mentioned that you fine folks over here may also need some similar data for the Vue Community project, most notably the descriptions? But I'd wager a guess that you'll also at a minimum need the website/repository URLs, the taglines and the icons.

cause if somebody wants to write library descriptions, we've got a ton of descriptions to write about on vue-community, contributions welcome 😉 - gusto

The issue we have is that using Vue Community as a data source presents a problem simply because it's Markdown. We have the exact same issue with the @vuejs/awesome-vue repository.

Ideally we need something more structured like JSON or YAML or Markdown(+FrontMatter).

It's relatively easy to transform those formats into Markdown but the opposite can certainly prove quite troublesome (depending on how well-structured the Markdown is, of course). It would also be possible for you to have a component e.g. <library name="saber" /> that abstracts away the JSON-data-loading aspect of things.

So the question is - would you be open to using JSON as a data source for certain things? Or if not JSON then Markdown with FrontMatter? Something more structured?

If so we would be able to pool our efforts across the two projects (perhaps in a third repository e.g. vue-data, if preferable to you).

Plus it would be useful for anyone else who wants to make apps/tools relating to Vue and its ecosystem- not just Elfayer's vue-land-bot and your vue-community!

I realise that Markdown is ideal for your project, mostly because even non-programmers such as designers can contribute easily. But that's why I mentioned Markdown+FrontMatter as a potential compromise.

Thoughts?

The data I started compiling for the bot looks something like this, by the way:

{
  "name": "Vuetify",
  "tagline": "Material Design Component Framework.",
  "tags": ["ui", "framework", "material", "design", "component", "library"],
  "icon": "vuetify.png",
  "colour": "#7BC6FF",
  "url": {
    "site": "https://vuetifyjs.com/en/",
    "repo": "https://github.com/vuetifyjs/vuetify"
  },
  "fields": [
    "Vuetify is a semantic component framework for Vue. It aims to provide clean, semantic and reusable components that make building your application a breeze.",
    "Build amazing applications with the power of Vue, Material Design and a massive library of beautifully crafted components and features. Built according to Google's Material Design Spec, Vuetify components feature an easy-to-remember semantic design that shifts remembering complex classes and markup, to type-as-you speak properties that have simple and clear names.",
    "Harness the power of the Vuetify community and get help 24/7 from the development team and our talented community members across the world. Become a backer and get access to dedicated support from the team."
  ],
  "author": {
    "name": "John Leider",
    "url": "https://github.com/johnleider",
    "avatar": "johnleider.png"
  }
}

(The fields are, for now, taken from the websites/repositories of the libraries but I'm open to contributing brand new copy if that was your intent).

It could be nice to have some way to mark the stub chapters in the menu, that require more contributions. Like the "help wanted" in the issues.

For now I put it here for discussion. Perhaps "help wanted" in the issues is enough.

A list of best learning resources for testing Vue Apps or modern FE in general.

• https://github.com/NoriSte/ui-testing-best-practices - A collection of best practices and tips when testing UI.
• https://lmiller1990.github.io/vue-testing-handbook/ - A short and focused guide on testing Vue apps with Vue Test Utils.
• https://vue-test-utils.vuejs.org/guides/ - the official Vue Test Utils guides. They are full of tips
• https://jrsinclair.com/articles/2016/gentle-introduction-to-javascript-tdd-intro/ - a very nicely written introduction to testing in general
• https://www.manning.com/books/testing-vue-js-applications - One of the first books about testing Vue applications, written by the Vue Test Utils author.
• https://afontcu.dev/ - A very well written blog, full of testing tips.

Quotes are super useful and look cool, but the light grey on a white background is not good for accessibility. Let's consider making it darker.

This page is still debatable, as it needs to expose enough info, to not duplicate over the official Gridsome website.

A page dedicated just to Code Editors and the most popular plugins for them.

I'd like to state some issues here:

• I'm not too sure about the name since we aren't listing any article, in particular, might be worth it to just name it Blogs instead of what it is at the moment

• Some of the blogs are incomplete and needs attention

• In the section for the personal blog. I don't understand the format there. Markus Oberlehner is listed there as a level-1 heading and then others are listed inline Are the suppose to be listed inline or also have some text written too?

• I think it is important we don't populate the personal blog section with anybody that has only ever written one or two tutorials on Vue, I think it should only include people who have blogs dedicated to Vue and nothing else or at least write on Vue regularly and have articles > 5

The page is still in early development. Content needs a run down, sections are missing content completely.

What needs to be done

• PWA
• Vue-Nativescript
• Compared to others - for vue-nativescript
• Wees - refine it a bit
• Mobile UI Frameworks - sections are empty, but should give a rought starr

Page has only skeleton, needs to be added content.

vue-community.org

Most of the content is added, but needs to be curated.

Missing content

• GraphQL + Apollo
• Feathers
• Meteor
• SocketIO
• SSE
• MQTT

Hello Vue developers,

I belief the project Publii is worth mentioning in the list of Static Site Generators based on Vue.

The great thing about Publii is that, it not only is a Static Site Generator, it's also a full-fledged content management system (also based on Vue).

Project name: Publii
Official website: https://getpublii.com/
Description: Publii is a Static Site Generator and Content Management System. It's written using Vue, uses JSON-files for its configuration and uses Vue in combination with the template language Handlebars to generate the pages.

Perhaps this section could do with having @nuxt/press added?

It's very new - I don't think most people know it exists yet. But I'm sure it will with time become popular along with Gridsome and VuePress etc.

https://github.com/nuxt/press
https://nuxt.press/

Hi,

I have created local store and registered in my component and it it working fine.

but the problem is when i reload my app and navigate to that component where i register and using local store mutation gets called once. when i navigate back to home page and again navigation to that component mutation executing 4 times.
All the times mutation execution getting increases in format(1x1, 2x2, 3x3, 4x4......)

I am really not sure about the purpose of this page. Needs to be discussed.

Go through all books and note the quotes from their websites.

Lets gather some of the most popular projects, that just dont fit other categories, like Vue-Storefront for example.

Format:

## Project Name
Description that is around 250 characters or less, roughly 2-3 sentences. 

### Useful links 
docs, tutorials, etc.

A list of community leaders, library authors, and their role in the Vue community.

Please consider adding a review of PrimeVue to your comparison list

https://vue-community.org/guide/ecosystem/ui-libraries.html#summary-tldr

Seems like it should merit some consideration.

cheers

The tutorial link for Building a Desktop App with Vue: Electron in docs/guide/ecosystem/desktopapps.md is broken.
It gives a 404 error after redirection.

We could use more direct quotes, instead of trying to rephrase what they have written. This saves both time and the possibility to sound the same as the original source.

Nativescript-vue link should be this
Vue Native has been deprecated and is no longer maintained (see comment on website)

I've been looking through numerous issues and would like to contribute but I don't know how.

P.S: I'm not an expert in Vue, almost a year experience, hope it's enough!

Page in question found HERE

The second link (https://dev.to/vuevixens/building-a-desktop-app-with-vue-electron-3pl) is broken and goes to a 404 page.

Hi! First of all, thank you for your hard work!

After reading the guide, I noticed that no non-English content is available. I believe there's a lot of great content out there written in other languages, too, and it might be great to link it from the guide.

For instance, this introduction to Vue book written in Spanish is well-written and informative.

Should there be a place for such kind of content? Should it be collocated with other similar content? Or it'd be better to create a "Multilingual" root menu element, and gather all content there?

The guide looks great and I feel it adds a ton of value to both newcomers and well established people. Keep up the good work! 🙌

This page needs some content, that does not overlap with events.vuejs. It should follow a path, similar to Meetups and link to the above mentioned website.

This page should have more tips from mentors. Even if they overlap, users can find the people they look up to and see what they give as an advice on how they approach learning.

This page will be ever expanding, but we can close the issue, once we have around 10 testimonials.

FAQ page will always have room for improvement, but for now we need to have the questions already there answered.

This page will contain a list of legacy Vue packages that should probably not be used any more.

• Vuex ORM
• vuex-persistedstate
• vuex-pathify
• vuex-persist
• vuex-i18n
• vuex-cache

• Some pages (e.g. Nuxt) comprise of only bullet points
• Others are empty or have empty sections (e.g. Legacy; Hosting - Digital Ocean)

Inspired by Wikipedia, I propose a very simple component that shows a little notice stating that:

• the page needs to be worked on
• any help is appreciated
• simply links to the repository (perhaps also the Discord channel?)

Additionally, the same component (presumably with a different icon/colour, for purposes of differentiation) could be used for sections which merely require some expansion or development.

Would this be an acceptable PR to undertake?

Hello.

I don't want to tread on anyone's toes, but I'd like to make some small tweaks to the styles to make it easier to scan and read information.

I did these just mucking about in DevTools but happy to clone the repo and submit a PR:

• Lato font throughout
• tighter body line-spacing
• outdented headings, slightly darker
• simplified "Useful links" sections

There are probably other bits which could be improved.

I've screen-shotted some examples below, but happy to give it all a bit of a once over.

Outdented headings, makes it easier to scan pages:

Original:

Proposed:

Useful links, currently a bit heavy:

Original:

Proposed:

It may be a good idea to note which is the more popular solution when a list of resources is given. For example vue-i18n is quite more popular than vuex-i18n.

We should also add a TLDR at the beginning, as most people just want to see whats most popular and wont bother reading long descriptions.

Suggestion

This is a suggestion of a similar TLDR, from Cristi

Forms

• Best for simple, less boilerplate validation - vee-validate
• Best for customizable validations: - vuelidate
• Best for generated forms (e.g generated based on json) - vue-form-generator

Boilerplates:

• Desktop apps: electron-vue
• Laravel: ....
• Large teams: Vue enterprise boilerplate

Regarding https://vue-community.org/guide/community/vue-3.html

What's the optimal place to put:
https://v3.vuejs.org - it's official but not a repository. Perhaps we could rename official repositories to official resources?
https://github.com/blacksonic/awesome-vue-3 - that's an extensive list of resources that would be good to link and recommend for those looking for more materials.

It would be awesome if we have a section with Vue 3 related topics and articles.
More and more people are interested in the differences and upgrades it will bring. I think it would be awesome if we could aggregate all the nice articles into one place.

Format I imagine:

1. A few short sentences on what Vue 3 brings most to the table
2. Then we start with top features:
   1. Links to articles,
   2. RFC-s (explain briefly what these are) and so on.

Lots have been written on the topic, so we can collect lots of good info.

Hello, I'm one of the core maintainers of Vue Formulate and I'd love to have it represented on the page about Handling Forms. We released our 2.0 rewrite 2 months ago along with thorough developer documentation. We're on the cusp of releasing 2.3 which will be our largest feature update to Vue Formulate since the 2.0 release.

What would the proper process be for consideration? Thank you!

Most of he page is written, we need to finish the auto-generators

• Auto Generators
  • Vue Styledguidist - assigned to author
  • Vuese
  • Vuedoc
  • JSDoc Vuejs
  • Vue Design System

One could also contribute to the other parts as well.

Page should explain how to use Vue with etc. Any extra tooling, that is outside of the common Vue workflow is welcome on the page.

• JSX
• Typescript
• RXjs
• Apollo GraphQL
• Codemods