Routing, layouts, and views
Overview
This project uses Vue Router, which we initialize in src/router/index.js
, with routes defined in src/router/routes.js
. Inside the src/router
folder, there are also two sub-folders, both containing route-specific components: layouts
and views
.
Layouts
Every view component must use a layout component as its base and register it as Layout
, as this convention helps us mock out layout components when testing views. Layouts usually aren't very complex, often containing only shared HTML like headers, footers, and navigation to surround the main content in the view.
To use Layout add name as additional option for your view component.
Here's an example:
export default {
layout: 'main',
...
}
Views
Each view component will be used by at least one route in src/router/routes/*.routes.js
, to provide a template for the page. They can technically include some additional properties from Vue Router to control navigation, for example to fetch data before creating the component, but I recommend adding these guards to src/router/index.js
instead, as that behavior typically has much more to do with the route (and will sometimes be shared between routes) than it does the view component.