The Nuxt Starter is frontend boilerplate for our Nuxt projects. It consists of a basic set of commonly used components, tools and libraries, as well a Webpack configuration. The goal is the have a starting point and a mandatory structure & conventions for every single Nuxt Project at Nueva, that can be easily customised and extended without having to write the same basic components over and over again. It provides a solid structure and a set of tools to improve code consistency and quality of the final project.

What belongs to the Nuxt Starter?

• Generalised functional low-level Vue-Components with basic styling, that are applicable to many projects
• Useful Vue filters, mixins and directives that improve the workflow or quality of every individual project
• Useful Sass Definitions (Vars, Mixins, Functions)
• Generally everything that we agree on that improves the developer experience and the quality of the projects and should speed-up development processes.

What does NOT belong to the Nuxt Starter?

• Project-specific components/libraries, etc.
• Is it something like swiper.js, flickity.js, vue.js? → Might be something for the Pattern Library (Manu & Janson agree)

What is the difference between the Pattern Library and the Nuxt Starter?

The Nuxt Starter contains all the important components for a very basic website and all the configuration to work with.

The Pattern Library contains useful script libraries that cover more complex functionality, that might not be applicable to most projects. (e.g. Datepicker, etc.)

An approach is to fill the library only with pure functional useful patterns that are often needed to avoid writing them over and over again. This approach should be verified by developing a medium complex live example component regarding to feasibility and time exposure.