anasameur / vuejsboilerplate Goto Github PK

I think you should better base your boilerplate on Nuxt instead of VueJs in order to get aligned with the VueJS/Nuxt community.

It seems that you are building your own Nuxt at this point, so why not use an accepted convention by the community?

Look at these ressources:
https://github.com/nuxt-community/awesome-nuxt
https://github.com/nuxt-community/modules
https://www.toptal.com/vue-js/server-side-rendered-vue-js-using-nuxt-js

I also found an example of a starter project that uses both Nuxt and Vuetify, maybe you can have at look at it: https://github.com/vuetifyjs/nuxt

• text interpolation using the “Mustache” syntax (double curly braces) are deleted

Sentry is awesome for handling the logs and i found a Nuxt module that makes the integration easier: https://github.com/nuxt-community/sentry-module

I think it would be better to use Puppeteer+Jest instead of Nightwatch+Selenium for End-to-end testing, as it's the latest headless browser on the market.
It's also made by Google and will be combined with the testing framework built by Facebook.

https://github.com/GoogleChrome/puppeteer
http://jestjs.io

I found a Nuxt module that can handle i18n for translations:
https://nuxt-community.github.io/nuxt-i18n/

• vue-i18n integration
• Automatic routes generation prefixed with locale code
• SEO
• Translations messages lazy-loading
• Redirection based on browser language
• Different domain names for each language
• Vuex store module with current locale & messages

Also, the languages are handled as separate JSON files, so it makes translation a lot easier.

More info here: https://fr.nuxtjs.org/examples/i18n/

I think OneSignal could be great for this usecase instead of Firebase

It seems there is a recommended way of handling notifications with it: https://pwa.nuxtjs.org/modules/onesignal.html