Blog

Recently I attended Front Trends 2014 in Warsaw. This is an awesome conference which you should (no, definitely have to!) attend in 2015. Besides incredible main programm Front Trends provides a set of Lighting Talks. This year I was a part of it presenting Steroids, a framework and a toolkit for developing HTML5 mobile apps. If you did not have a chance to hear it, this offline text presentation is for you.

The bem-core library goes futher and there already is 2.0.0 version available. This blog was safely switched to the new major version with some diff to the code. Now so can do you. Careful examination of the version changelog will help you with it. Look how I did this.

Depending on a project people prefer different ways to adapt BEM. This results into a range of tools for our choice. Today, I am translating Maxim Shkalin's description of the BEML templating pre-processor. Willing to lighten the development with BEM I propose a tiny extension for the HTML syntax (yes, I used to writ all those long CSS classes manually). As the name BEMHTML is greedily taken by the Yandex guys, let us call it BEML.

Last week I met the need to develop a web site which static assets have to be hosted on a different server and respond by different URLs than its HTML. This is the requirement to all the static files: stylesheets and JavaScript linked to the page as well as imges and fonts mentioned in HTML, CSS and JavaScript code. However it is obvious that these resources should be local when developing. Thus, the challenge was to introduce a piece of magic which knows where we aim to host the statics and transforms all the relative paths into absolute ones according to it. The tools which helped me is…

The recently published step-by-step tutorial on i-bem.js mentioned YM modular system as a base for component JavaScript solution behind BEM. Why do we need another modular system? Let us see... The author of YM modules, Dmitry Filatov recently came up with an article about YM modules in Russian. And below you can find the translation. So, one more modular system? Besides CommonJS and AMD? Why should we care? I will not write why modules and modular systems are needed, there are plenty of articles about it. Let us rather proceed to the main question: why do we need another modular system? For…

We usually start developing a web site prototyping the interface and then implementing HTML/CSS and bacis JavaScript. In case of using the full BEM stack a tranformation from prototype to a functioning web site goes smoothly. You can clone the project from project-stub and create a static web page as it was described earlier. Thanks to templates, you do not need write all the HTML manually. Describing page sructure in rather than writing all the tags manually saves time. But sometimes this is still a lot of work to do, especially for large pages. Luckily BEMJSON can include JavaScript…