Frontend for Base.

# install dependencies
npm install

# serve with hot reload at localhost:8080
npm run dev

# build for production with minification
npm run build

# build for production and view the bundle analyzer report
npm run build --report

This is the template index.html for our single page application (SPA). During development and builds, Webpack will generate assets, and the URLs for those generated assets will be automatically injected into this template to render the final HTML.

This folder contains all the configuration files. The important files in this are:

1. dev.env.js: This contains the development environment variables.
2. prod.env.js: This contains the production environment variables.

The /src directory is where all the source files are present. It further has sub-directories each with it's own purpose:

This is the app entry file. This is where our Vue application is instantiated. Any Vue plugins (router, vuex, etc) can be registered here.

The App.vue file is the main app component. All other pages will be rendered inside this.

This is where all the static assets, like images, are stored.

This is where the Vuex store and all the modules are kept. The following must should be followed:

• All the globally shared state must be declared inside the state.js file.
• All the global getters must be declared inside the getters.js file.
• All the global mutations must be declared inside the mutations.js file.
• All the global actions must be declared inside the actions.js file.
• All the modules will go inside the modules sub-directory. Modules must be exported through the index.js file inside the modules directory. Each module (sub-directory) should follow the following conventions:
  • The module state must be declared inside the state.js file. Example: /store/modules/user/state.js
  • The module getters must be declared inside the getters.js file. Example: /store/modules/user/getters.js
  • The module mutations must be declared inside the mutations.js file. Example: /store/modules/user/mutations.js
  • The module actions must be declared inside the actions.js file. Example: /store/modules/user/actions.js
  • All of the above files, must then be included and returned (export default) as an object from a index.js file. Example: /store/modules/user/index.js

Here's a sample directory structure for the /store directory

• /store
  • state.js
  • getters.js
  • actions.js
  • mutations.js
  • /modules
    • index.js (exports all the modules. eg: user)
    • /user
      • index.js (exports user module's state, getters, actions and mutations)
      • state.js
      • getters.js
      • actions.js
      • mutations.js

This directory contains all the components which act as pages or, to be specific, are used/rendered by the router. They can be further nested in sub-directories according to context.

This directory contains all the Components used throughout the application. They can be further nested in sub-directories according to context.

This directory contains a single file, index.js, for now. This file contains all the route <-> page mappings.

This directory contains all the style files, in SCSS format. All the sub-directories, inside this directory, must have files prefixed or starting with an _ (underscores). For example: /scss/variables/_colors.scss.

All the sub-directories should have an all.scss file, which combines (imports) all the other files (that start with an _ underscores). Further, this all.scss file should be imported inside the /scss/app.scss file.

Any file, that are to be imported directly outside of the '/scss' folder, must be kept in the root of the /scss folder. For example, the /scss/app.scss file imports the /scss/variables/all.scss and the /scss/app/all.scss files, and then it is imported directly in the /src/App.vue file. Thus, the /scss/app.scss file acts as single source of all the styling, from outside of the /scss folder.

This directory contains purely static assets, which are to be used directly. It acts as an escape hatch for static assets that you do not want to process with Webpack. They will be directly copied into the same directory where webpack-built assets are generated which, in this case, is the /dist directory.

This directory holds the actual configurations for both the development server and the production webpack build. Normally you don't need to touch these files unless you want to customize Webpack loaders, in which case you should probably look at build/webpack.base.conf.js.