Ian Oxley
8438cf0578
* Replace divs with semantic markup Replace `<div>` tags with `<nav>`, `<aside>`, and a list for the nav items. * Use grid layout Replace flexbox with CSS grid layout. The right-hand side item is now in its own grid cell, so the text wraps inside its cell at smaller screen widths. Undo `<nav>` tag. * Sort CSS Sort the remaining CSS property declarations. * Fix right alignment issue in Safari Remove `justify-self: end` to fix the right alignment issue in Safari. * Fix vertical alignment in Edge Add `align-self: center` but only for MS Edge. Also removed `position: relative` on the wrapper element for the tabs. As the help item isn't using absolute positioning anymore we don't need to set relative positioning on the parent element.
Running
For information about installing Habitica locally, see Setting up Habitica Locally and for information about running the local client, refer to the "Run Habitica" section in that page.
Preparation Reading
-
Vue 2 (https://vuejs.org)
-
Webpack (https://webpack.github.io/) is the build system and it includes plugins for code transformation, right now we have: BabelJS for ES6 transpilation, eslint for code style, less and postcss for css compilation. The code comes from https://github.com/vuejs-templates/webpack which is a Webpack template for Vue, with some small modifications to adapt it to our use case. Docs http://vuejs-templates.github.io/webpack/
-
We’re using
.vuefiles that make it possible to have HTML, JS and CSS for each component together in a single location. They’re implemented as a webpack plugin and the docs can be found here http://vue-loader.vuejs.org/en/ -
SemanticUI is the UI framework http://semantic-ui.com/. So far I’ve only used the CSS part, it also has JS plugins but I’ve yet to use them. It supports theming so if it’s not too difficult we’ll want to customize the base theme with our own styles instead of writing CSS rules to override the original styling.
The code is in /website/client. We’re using something very similar to Vuex (equivalent of React’s Redux) for state management http://vuex.vuejs.org/en/index.html
The API is almost the same except that we don’t use mutations but only actions because it would make it difficult to work with common code
The project is developed directly in the develop branch as long as we’ll be able to avoid splitting it into a different branch.
So far most of the work has been on the template, so there’s no complex logic to understand. The only thing I would suggest you to read about is Vuex for data management: it’s basically a Flux implementation: there’s a central store that hold the data for the entire app, and every change to the data must happen through an action, the data cannot be mutated directly.
For further resources, see Guidance for Blacksmiths, and in particular the "Website Technology Stack" section.