Zarema Khalilova

We have many #OpenSource libraries. Some of them need a demo besides documentation. We use GitHub Pages for a demo of libraries. We create a demo folder near with code of the library, add index.html with demo code and publish files only from demo folder to gh-pages. Fast and simple.

To avoid code formatting conflicts and keep a high quality of code we use linters. ESLint for #JavaScript, Stylelint for #CSS, remark-lint for #markdown. Good point that tools allow using shareable config, it useful cause we have many projects.

We in our #Frontend team prefer to use the modern and clean syntax of #CSS instead of Sass or Less. On bundle step, we use post-processing by PostCSS to add prefixes, minify code, uploading assets and more. PostCSS get CSS more powerful, it‘s a fantastic tool.

I am working on #OpenSource file uploader. The uploader is the widget that other developers embed in their apps. It should work well in different browsers and on different devices. BrowserStack and Sauce Labs help to achieve that. I can test the uploader in many varieties of browsers+OS only used my browser without virtual machines.

React Storybook is one of the most favorite tools in our #Frontend team. When we start a new frontend part, we install storybook at first and create visual React components based on our design with usage stories in Storybook. So, we get a live version of design quickly and can sync with designers before developing of whole app and configure Webpack.

Since 2011 our frontend was in Django monolith. However, in 2016 we decide to separate #Frontend from Django for independent development and created the custom isomorphic app based on Node.js and React. Now we realized that not need all abilities of the server, and it is sufficient to generate a static site. Gatsby is suitable for our purposes. We can generate HTML from markdown and React views very simply. So, we are updating our frontend to Gatsby now, and maybe we will use Netlify for deployment soon. This will speed up the delivery of new features to production.

#StaticSiteGenerators #StaticWebHosting

In Uploadcare we like to write internal documentation and instructions for all occasions. We used Confluence before, but strong and very slow UI fall us to frustration. We start to research alternative and met slite. The ability to quickly create notes and search, great onboarding, the familiar interface in Slack style, useful shortcuts, nice code snippets, support of Markdown. Now writing instructions and team notes have become much more pleasant.