Week 44, 2016

08 November 2016

First thing first, I'm staring weekly posts about findings that are somehow related to work. This is a mature but not yet implemented idea. Although, a friend of mine Vladimir Starkov sometimes practises the same.

In this issue there are tips on organizing Google Calendar, nice project management addition for GitHub, Styleguide solutions for React projects and a couple of good reads.

Week numbers in Google calendar

In Finland, the week numbers are widely used. People easily make agreements on let's say "the beginning on week 45". For this purpose and also for the actual weekly reports, I have subscribed for a special Google calendar which provides a small week number at the top right corner or every monday.

CalendarWeekNumbers3

Here are the instructions: http://www.daimto.com/how-to-add-week-numbers-to-your-google-calendar/.

ZenHub — a GitHub issue tracker

ZenHub is an add-on, which makes different boards with columns on top of GitHub issues.

zenhub task board

It looks like a competitor of embedded GitHub Projects but with more features.

React Storybook and React Styleguidist

In the project I have started on Monday, we faced the need to document React components. There were two candidates among the tools to use — React Storybook and React Styleguidist. Both with their pros and cons.

By now, we ended up with Styleguidist. Anyway, this is not a mature solution, and we can probably think back.

The Storybook was super easy to install. However, it requires more typing for every story and does not read the props out of the documenting comments.

The Styleguidist was a tricky thing to run. Everything goes smoothly at simple projects but this was not our case. There were some difficulties with the pages wrapped into react-hot-loader container. I solved it by introducing proper file structure. We should have it anyway. Now, there is a dedicated folder for the components and we taught the Styleguidist to work with it.

As a piece of advice to friends, I can give the following: try to reuse your normal webpack config and not to write another one in the styleguide.config.js file. It will save you some time when changing the building process. This is our version:

const siteWebpack = require("./webpack.config.js");

module.exports = {
  title: 'My Great Style Guide',
  components: './src/components/**/*.jsx',
  updateWebpackConfig(webpackConfig) {
    siteWebpack.module.loaders.forEach(function(loader) {
      webpackConfig.module.loaders.push(loader);
    });
    webpackConfig.postcss = siteWebpack.postcss;

    return webpackConfig;
  },
};

How to Write a Git Commit Message

The article How to Write a Git Commit Message by Chris Beams has already turned 2 years but still actual. I have read it previously and try to follow. But I do not recollect me shring the link to it. So, here it is.

4 different kinds of React component style

Setting up a new project I have scanned a lot of recent articles about React. One of them is 4 different kinds of React component style. I had doubts if to put it in this blog post or not because it did not tell me much new. On the other hand, it's not a long read and finely summarizes different kinds of React components.

You can hire me and the whole Bridge-the-Gap team to set up, manage, develop, and champion your design system. I can align the design and development processes in your organisation for a larger business impact.

© Varya Stepanova 2024