Conventional commits provide a consistent way to structure commit messages, which helps with automation, release notes generation, and understanding the history of a project. The format adheres to the following structure:
<type>(<scope>): <message>
| // to encode a font into Base64 use this tool https://www.npmjs.com/package/font-store | |
| (function (window, document) { | |
| 'use strict'; | |
| var isModernBrowser = ( | |
| 'querySelector' in document && | |
| 'localStorage' in window && | |
| 'addEventListener' in window | |
| ), | |
| key = 'font', |
I published this email exchange as a full post at csswizardry.com/…/can-css-be-too-modular.
| <script type="text/javascript"> | |
| (function () { | |
| "use strict"; | |
| // once cached, the css file is stored on the client forever unless | |
| // the URL below is changed. Any change will invalidate the cache | |
| var css_href = './index_files/web-fonts.css'; | |
| // a simple event handler wrapper | |
| function on(el, ev, callback) { | |
| if (el.addEventListener) { | |
| el.addEventListener(ev, callback, false); |