<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Stanislav Gurin on Medium]]></title>
        <description><![CDATA[Stories by Stanislav Gurin on Medium]]></description>
        <link>https://medium.com/@stanislavgurin?source=rss-77c30067bec2------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/2*ert-YRI8KzC45ZFMGYI4ZQ.jpeg</url>
            <title>Stories by Stanislav Gurin on Medium</title>
            <link>https://medium.com/@stanislavgurin?source=rss-77c30067bec2------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 16:36:58 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@stanislavgurin/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[How to save you days of bug fixing with custom scroll CSS and JS]]></title>
            <link>https://medium.com/@stanislavgurin/how-to-save-you-days-of-bug-fixing-with-custom-scroll-css-and-js-b6e526aaac2?source=rss-77c30067bec2------2</link>
            <guid isPermaLink="false">https://medium.com/p/b6e526aaac2</guid>
            <category><![CDATA[custom-scrollbar]]></category>
            <category><![CDATA[css3]]></category>
            <category><![CDATA[js]]></category>
            <category><![CDATA[html5]]></category>
            <category><![CDATA[jquery]]></category>
            <dc:creator><![CDATA[Stanislav Gurin]]></dc:creator>
            <pubDate>Sat, 21 Nov 2020 13:02:39 GMT</pubDate>
            <atom:updated>2020-11-21T13:02:39.900Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*1-bAoHf637vRLCmi" /><figcaption><a href="https://ageorgiev.com/blog/how-to-create-a-custom-scrollbar-in-your-website/">https://ageorgiev.com/blog/how-to-create-a-custom-scrollbar-in-your-website/</a></figcaption></figure><p>Sooner or later all developers are faced with the need to customize scrolls. I hope this article will give you enough information to make the right decision and not waste <em>days </em>fixing bugs, as the author did :)</p><p>A brief history of styling scrollbars:</p><ol><li>It used to be a thing only Internet Explorer could do (ancient versions) with stuff like <strong>-ms-scrollbar-base-color.</strong> These do not exist anymore.</li><li>Then WebKit-based browser engines got on board with stuff like <strong>::-webkit-scrollbar.</strong> It works across the <strong>Chrome</strong>, <strong>Edge</strong>, <strong>Safari</strong> and <strong>Opera</strong> landscape today.</li></ol><p>Standards have finally been incorporated, and those styling options are covered by un-prefixed properties like<a href="https://css-tricks.com/almanac/properties/s/scrollbar-color/"> <strong>scrollbar-color</strong></a> and<a href="https://css-tricks.com/almanac/properties/s/scrollbar-color/"> <strong>scrollbar-width</strong></a>.</p><p>The -webkit-scrollbar family of properties consists of <em>seven</em> different pseudo-elements that, together, comprise a full scrollbar UI element:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/570/0*WYAEHs036CYs69n6" /></figure><ol><li><strong>::-webkit-scrollbar</strong> addresses the background of the bar itself. It is usually covered by the other elements</li><li><strong>::-webkit-scrollbar-button</strong> addresses the directional buttons on the scrollbar</li><li><strong>::-webkit-scrollbar-track</strong> addresses the empty space “below” the progress bar</li><li><strong>::-webkit-scrollbar-track-piece</strong> is the top-most layer of the the progress bar not covered by the draggable scrolling element (thumb)</li><li><strong>::-webkit-scrollbar-thumb</strong> addresses the draggable scrolling element that resizes depending on the size of the scrollable element</li><li><strong>::-webkit-scrollbar-corner</strong> addresses the (usually) bottom corner of the scrollable element, where two scrollbars might meet</li><li><strong>::-webkit-resizer</strong> addresses the draggable resizing handle that appears above the scrollbar-corner at the bottom corner of some elements</li></ol><p>In addition to these pseudo-elements, there are also <em>eleven</em> pseudo-selector classes that aren’t required but provide designers with the power to style various states and interactions of the scrollbar UI. A full breakdown of those pseudo-selectors, and a detailed example, can be found in <a href="https://css-tricks.com/custom-scrollbars-in-webkit/">this CSS-Tricks article</a>.</p><p>These are the pseudo-class selectors. They allow for more specific selection of the parts, like when the scrollbar is in different states.</p><p><strong>:horizontal</strong> – The horizontal pseudo-class applies to any scrollbar pieces that have a horizontal orientation.</p><p><strong>:vertical</strong> – The vertical pseudo-class applies to any scrollbar pieces that have a vertical orientation.</p><p><strong>:decrement</strong> – The decrement pseudo-class applies to buttons and track pieces. It indicates whether or not the button or track piece will decrement the view’s position when used (e.g., up on a vertical scrollbar, left on a horizontal scrollbar).</p><p><strong>:increment</strong> – The increment pseudo-class applies to buttons and track pieces. It indicates whether or not a button or track piece will increment the view’s position when used (e.g., down on a vertical scrollbar, right on a horizontal scrollbar).</p><p><strong>:start</strong> – The start pseudo-class applies to buttons and track pieces. It indicates whether the object is placed before the thumb.</p><p><strong>:end</strong> – The end pseudo-class applies to buttons and track pieces. It indicates whether the object is placed after the thumb.</p><p><strong>:double-button</strong> – The double-button pseudo-class applies to buttons and track pieces. It is used to detect whether a button is part of a pair of buttons that are together at the same end of a scrollbar. For track pieces it indicates whether the track piece abuts a pair of buttons.</p><p><strong>:single-button</strong> – The single-button pseudo-class applies to buttons and track pieces. It is used to detect whether a button is by itself at the end of a scrollbar. For track pieces it indicates whether the track piece abuts a singleton button.</p><p><strong>:no-button</strong> – Applies to track pieces and indicates whether or not the track piece runs to the edge of the scrollbar, i.e., there is no button at that end of the track.</p><p><strong>:corner-present</strong> – Applies to all scrollbar pieces and indicates whether or not a scrollbar corner is present.</p><p><strong>:window-inactive </strong>– Applies to all scrollbar pieces and indicates whether or not the window containing the scrollbar is currently active. (In recent nightlies, this pseudo-class now applies to ::selection as well. We plan to extend it to work with any content and to propose it as a new standard pseudo-class.)</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/2245fec9437997c52602eafcc9b51bb5/href">https://medium.com/media/2245fec9437997c52602eafcc9b51bb5/href</a></iframe><p><strong>Scrollbar initial sizes tested in each browser:</strong></p><ul><li>OSX (Chrome, Safari, Firefox) — <strong>15px</strong></li><li>Windows XP (IE7, Chrome, Firefox) — <strong>17px</strong></li><li>Windows 7 (IE10, IE11, Chrome, Firefox) — <strong>17px</strong></li><li>Windows 8.1 (IE11, Chrome, Firefox) — <strong>17px</strong></li><li>Windows 10 (IE11, Chrome, Firefox) — <strong>17px</strong></li><li>Windows 10 (Edge 12/13) — <strong>12px</strong></li></ul><p>The scrollbar-width property allows the author to set the maximum thickness of an element’s scrollbars when they are shown</p><p>/* Keyword values */</p><p>scrollbar-width: auto;</p><p>scrollbar-width: thin;</p><p>scrollbar-width: none;</p><p>/* Global values */</p><p>scrollbar-width: inherit;</p><p>scrollbar-width: initial;</p><p>scrollbar-width: unset;</p><h3>Accessibility concerns</h3><p>Use this property with caution — setting scrollbar-width to thin or none can make content hard or impossible to scroll if the author does not provide an alternative scrolling mechanism. While swiping gestures or mouse wheels can enable scrolling on such content, some devices have no scroll alternative.</p><p>WCAG criterion 2.1.1 (Keyboard) has been in place for a long time to advise on basic keyboard accessibility, and this should include scrolling of content areas. And introduced in WCAG 2.1, criterion 2.5.5 (Target Size) advises that touch targets should be at least 44px in width and height (although the problem is compounded on high-resolution screens; thorough testing is advised).</p><ul><li><a href="https://developer.mozilla.org/en-US/docs/Web/Accessibility/Understanding_WCAG/Operable#Guideline_2.1_%E2%80%94_Keyboard_Accessible_Make_all_functionality_available_from_a_keyboard">MDN Understanding WCAG, Guideline 2.1 explanations</a></li><li><a href="https://developer.mozilla.org/en-US/docs/Web/Accessibility/Understanding_WCAG/Operable#Guideline_2.5_Input_Modalities_Make_it_easier_for_users_to_operate_functionality_through_various_inputs_beyond_keyboard.s/">MDN Understanding WCAG, Guideline 2.5 explanations</a></li><li><a href="https://www.w3.org/WAI/WCAG21/Understanding/keyboard">Understanding Success Criterion 2.1.1 | W3C Understanding WCAG 2.1</a></li><li><a href="https://www.w3.org/WAI/WCAG21/Understanding/target-size.html">Understanding Success Criterion 2.5.5 | W3C Understanding WCAG 2.1</a></li></ul><p>Good post on “wether to use custom scroll” <a href="https://www.nngroup.com/articles/scrolling-and-scrollbars/">https://www.nngroup.com/articles/scrolling-and-scrollbars/</a></p><h3>Points of Interest</h3><ul><li>If there is no qualifying selector preceding the various pseudo-elements, the styles will apply to <em>any</em> scrollbar that may appear on the page.</li><li>Setting -webkit-scrollbar styles is a good way to force your webpage to show horizontal or vertical scrollbars on versions of Mac OS newer than Lion, on which scrollbars are usually hidden by default.</li><li>Since this property is behind a -webkit vendor prefix, several jQuery plugins have been written to “polyfill” or extend this functionality to other browsers. One such plugin is<a href="http://jscrollpane.kelvinluck.com/"> jScrollPane</a>.</li></ul><h3>Using Plugins</h3><p>There are a number of jQuery plugins to customize the scroll bar. We tested 3 of “top free” plugins for customising scroll bar:</p><p><a href="https://github.com/Grsmto/simplebar/tree/master/packages/simplebar"><strong>SimpleBar</strong></a> — lightweight and performant plugin that replaces the browser’s default scrollbar with a custom CSS-styled one without losing performances. It keeps the <strong>native</strong> “overflow: auto” scroll and <strong>only</strong> replaces the scrollbar visual appearance.Highly performant, as the script doesn’t overwrite and mimic browser scrolling, but simply overlays the native scrollbar with a custom one.</p><ul><li>Highly performant, as the script doesn’t overwrite and mimic browser scrolling, but simply overlays the native scrollbar with a custom one.</li><li>Disables itself on mobile and device with native “floating” scrollbars (macbook trackpad for example) where it’s not needed.</li><li>SimpleBar has been tested on the following browsers: Chrome, Firefox, Safari, Edge, IE11. IE10 can be supported with some minor tweaking.</li></ul><p><a href="https://github.com/mdbootstrap/perfect-scrollbar"><strong>PerfectScrollbar</strong></a>. This JavaScript lets you add a custom scrollbar to scrollable elements on the page (except the BODY element) when you hover over it. Designed to be as unobtrusive as possible, it doesn’t alter the target container’s original styles in any way, simply adding a custom scrollbar over it. Any changes to the container’s dimensions are automatically accounted for (great for responsive design).</p><ul><li>No change on design layout</li><li>No manipulation on DOM tree</li><li>Use plain scrollTop and scrollLeft</li><li>Scrollbar style is fully customizable</li><li>Efficient update on layout change</li></ul><p><a href="https://github.com/malihu/malihu-custom-scrollbar-plugin"><strong>Malihu</strong></a> supports vertical/horizontal scrollbars, scrolling momentum, plus mouse-wheel, keyboard and touch response. It comes with several themes to easily experiment with different looks. A browser pleaser, the plugin works across a wide array of browsers, including IE8. It does however, require jQuery to work.</p><ul><li>Requires jQuery 1.6 or higher</li><li>Vertical and/or horizontal scrollbar(s)</li><li>Adjustable scrolling momentum</li><li>Mouse-wheel, keyboard and touch support</li><li>Ready-to-use themes and customization via CSS</li><li>RTL direction support</li><li>Option parameters for full control of scrollbar functionality</li><li>Methods for triggering actions like scroll-to, update, destroy etc.</li><li>User-defined callbacks</li><li>Selectable/searchable content</li></ul><h3>Other Resources</h3><ul><li><a href="https://css-tricks.com/the-current-state-of-styling-scrollbars/">CSS-Tricks: The Current State of Styling Scrollbars</a></li><li><a href="https://css-tricks.com/custom-scrollbars-in-webkit/">CSS-Tricks: Custom Scrollbars in Webkit</a></li><li><a href="https://developer.mozilla.org/en-US/docs/Web/CSS/CSS_Scrollbars">MDN Docs</a></li><li><a href="https://www.webkit.org/blog/363/styling-scrollbars/">Surfin’ Safari: Styling Scrollbars</a></li><li><a href="http://jscrollpane.kelvinluck.com/">jScrollPane</a></li><li><a href="http://blog.0100.tv/2012/11/webkit-scrollbars-on-os-x/">-webkit-scrollbar on OSX</a></li></ul><p>Let us know is this was helpful and feel free to share your experience in the comments.</p><p>Vova, thanks a lot :)</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b6e526aaac2" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How To Check the Accessibility of Your Site for Social Networks]]></title>
            <link>https://medium.com/@stanislavgurin/how-to-check-the-accessibility-of-your-site-for-social-networks-ebef7df8fb31?source=rss-77c30067bec2------2</link>
            <guid isPermaLink="false">https://medium.com/p/ebef7df8fb31</guid>
            <category><![CDATA[sharing]]></category>
            <category><![CDATA[open-graph]]></category>
            <category><![CDATA[social-media]]></category>
            <category><![CDATA[linkedin]]></category>
            <category><![CDATA[facebook]]></category>
            <dc:creator><![CDATA[Stanislav Gurin]]></dc:creator>
            <pubDate>Thu, 02 Apr 2020 16:51:22 GMT</pubDate>
            <atom:updated>2020-04-02T16:51:22.847Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*m5Jmb-KNjAsC5S6-" /></figure><p>I’m a Front-end Lead at <a href="http://justcoded.com/">JustCoded</a> with 10+ experience in front-end development. Social networks are developing rapidly and capturing more and more audiences. According to <a href="https://www.statista.com/topics/1164/social-networks/">Statista</a>, every third person on earth is registered in at least one of the social networks. The three most popular social networks are Facebook, Youtube, WhatsApp. This is a huge number of people who want to access content on your site and have the opportunity to share it. So, we have dozens of social networks and billions of websites. How do we deal with them?</p><h3>The Open Graph protocol</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/361/0*kqwdG1gfMYkQU1FD" /></figure><p><a href="https://ogp.me/">The Open Graph protocol</a> is a set of meta tags that help the social media engine get correct information about the resource. It was created by Facebook :) In my opinion, all websites that want to be accessible to users on social networks should follow this standard. There is an easy guide that you can find on <a href="https://developers.facebook.com/docs/sharing/webmasters">Facebook</a>.</p><p>There are a few cons:</p><ul><li><strong>Twitter</strong> uses its meta names that you can find on <a href="https://developer.twitter.com/en/docs/tweets/optimize-with-cards/overview/summary-card-with-large-image">Twitter Developers</a> Do not worry if you did not provide data for Twitter because it supports Open Graph protocol and will parse the data from og meta tags.</li><li>There are a lot of requirements for each of the social networks. For example, <strong>FB</strong> <a href="https://developers.facebook.com/docs/sharing/best-practices/">recommends</a> using images for preview only with 1:1 ratio. At the same time, the <a href="https://www.linkedin.com/help/linkedin/answer/46687/making-your-website-shareable-on-linkedin?lang=en">Linkedin recommendation</a> is a 1.91:1 ratio for images. If you put an image with another ratio it would be cropped. So, I would recommend not putting the important content of your preview image too close to the borders.</li><li><strong>Cache</strong>. Users post millions of pages every minute and that is why most social media networks cache data from websites. There are several options to clear cache and we will review them in detail in a few minutes.</li></ul><h3>Check it out</h3><p>So, after you have added the necessary tags for social networks you need to check your work. Almost all social networks have tools to do this.</p><h4>Facebook</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*f0IxA_BPvouzDbMJ" /><figcaption><a href="https://developers.facebook.com/tools/debug/?q=https%3A%2F%2Fjustcoded.com%2F">https://developers.facebook.com/tools/debug/?q=https%3A%2F%2Fjustcoded.com%2F</a></figcaption></figure><p><strong>Facebook</strong> has a <a href="https://developers.facebook.com/tools/debug/">Sharing Debugging Tool</a>, the most functional debugger at the moment. Insert your website <strong>URL</strong> and you will see what Facebook will retrieve for publishing. Note that if your website doesn’t have tags for social networks, then Facebook will use the first available image for og:image and the description text for og: description. It is not a bad variant, is it?</p><p>Make sure to check the meta tags of your post and pages before they hit Google and people start sharing them on social networks.</p><h4>Linkedin</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*hJe3WYHGNMpj73Cl" /><figcaption><a href="https://www.linkedin.com/post-inspector/inspect/justcoded.com">https://www.linkedin.com/post-inspector/inspect/justcoded.com</a></figcaption></figure><p><strong>Linkedin</strong> has a simple <a href="https://www.linkedin.com/post-inspector/">Post Inspector</a> that provides you almost the same data as FB checker. Note that it uses heavy cashing, so expect to see the changes in a day or so. You can ?latest to the <strong>URL</strong> it should look like <a href="https://justcoded.com/?latest">https://justcoded.com/?latest</a> Sometimes it works :)</p><h4>Twitter</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*LWJSuGEKiEVw7Cm_" /><figcaption><a href="https://cards-dev.twitter.com/validator">https://cards-dev.twitter.com/validator</a></figcaption></figure><p><strong>Twitter</strong> provides a <a href="https://cards-dev.twitter.com/validator">Card Validation Tool</a>. You need registered to use it. Remember that Twitter has <a href="https://developer.twitter.com/en/docs/tweets/optimize-with-cards/guides/getting-started">unique meta tags</a> that are not used by any other social media.</p><h4>OpenGraph Checker</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*nxR9t412N7OlQOEb" /><figcaption><a href="https://opengraphcheck.com/result.php?url=https%3A%2F%2Fjustcoded.com%2F#.XoNLCtMzZTY">https://opengraphcheck.com/result.php?url=https%3A%2F%2Fjustcoded.com%2F#.XoNLCtMzZTY</a></figcaption></figure><p>Despite its simple designs <a href="https://opengraphcheck.com/">Open Graph Checker </a>works without any registration and is quick.</p><h4>Simple code check</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/890/0*LNbJmmazUm6j0wmN" /></figure><p>If you are familiar with HTML then you can just open your page source code by right-clicking on any area and choose View Page Source. In Chrome option + command + U key for Mac users. After that try to find one of the og tags. For example, look for og:image. If you did not find it, then there is a 90% chance that your site does not use tags for social networks.</p><p>This is the easiest and most reliable way to check for og tags without any registration or cached versions :) Alternatively, just go to the social network of choice, add a link to the page inside the post window and see what info it will fetch. You don’t need to publish anything.</p><h3>Other uses of Open Graph</h3><p>This protocol is not limited only to social networks. Almost all popular messengers support <a href="https://ogp.me/">Open Graph Protocol</a> and show you extra information together with a link.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/478/0*Px1e8xZewlcxn4KH" /></figure><p>For example, Google uses data from meta tags in <strong>Google Docs/Sheets</strong> and links display extra details like text description and images giving you an idea of the page content without visiting it. You can check it by simply inserting any link into your Google Document and clicking it.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/366/0*rUnpqU9wzP0SRZYc" /></figure><h3>Bad example</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*UslT1x0Ll4PicoLq" /></figure><p>I love flying! Despite the chaos we are going through, I hope that very soon we will be able to travel and see the world again. I flew on Airbus planes to the majority of my travel destinations in the past, but I actually love Boeing :) However, if I decide to share my passion with Facebook users or anywhere else in the social networks, I will fail miserably. Why? Just insert the link of the official Boeing Company website into FB Checker. Let’s take a look why? Take the link to the <a href="https://www.boeing.com/">Boeing: The Boeing Company</a> and put into <a href="https://developers.facebook.com/tools/debug/?q=https%3A%2F%2Fwww.boeing.com%2F">FB Checker</a> As we can see there is an error with the SSL certificate. Okay, let’s get rid of it and use an HTTP link instead. Here’s what we see:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*cAm-40-GYIgq0kBB" /></figure><p>FB took the first image from the page then cropped it. Looks lousy, right? Linkedin <a href="https://www.linkedin.com/post-inspector/inspect/http:%2F%2Fboeing.com%2F">shows no information</a> at all. Why? There is no og:image meta tags :( Here is <a href="https://opengraphcheck.com/result.php?url=https%3A%2F%2Fwww.boeing.com%2F#.XoH0fdMzZTY">the report</a>. As you can see there is meta tags only for Twitter. Who knows maybe Boeing shares their content only through Twitter :)</p><h3>Conclusion</h3><p>We cannot ignore social <strong>networks/messengers/services </strong>and their importance will only grow. So, before you go live, make optimizations and check your site against the most popular social networks. Here’s a list of the main services to check your og tags:</p><ul><li><a href="https://developers.facebook.com/tools/debug/">Facebook Debug Tool</a></li><li><a href="https://www.linkedin.com/post-inspector/">LinkedIn Post Inspector</a></li><li><a href="https://opengraphcheck.com/">OpenGraphCheck.com — Check Open Graph Tags on Websites</a></li><li><a href="https://cards-dev.twitter.com/validator">Twitter Card Validator</a></li></ul><p>In my next article, I’ll explain the importance of <strong>Schema.org</strong> for <strong>Google</strong> and show how to implement it for different use cases.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ebef7df8fb31" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How Your Front-end Code Impacts Google Ranking: Top 5 Risky Areas]]></title>
            <link>https://medium.com/@stanislavgurin/how-your-front-end-code-impacts-google-ranking-top-5-risky-areas-8123513fd6ba?source=rss-77c30067bec2------2</link>
            <guid isPermaLink="false">https://medium.com/p/8123513fd6ba</guid>
            <category><![CDATA[google]]></category>
            <category><![CDATA[frontend]]></category>
            <category><![CDATA[seo]]></category>
            <category><![CDATA[optimization]]></category>
            <category><![CDATA[javascript]]></category>
            <dc:creator><![CDATA[Stanislav Gurin]]></dc:creator>
            <pubDate>Tue, 31 Mar 2020 07:35:03 GMT</pubDate>
            <atom:updated>2020-04-01T10:37:50.680Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*K6hDYpz3XSAUnXY6qG_-tw.png" /></figure><p>I’m a Front-end Lead at <a href="http://justcoded.com/">JustCoded</a> with 10+ experience in front-end development. The things I explain in this article may sound controversial to some of the developers and <strong>SEO</strong> specialists. I based most of these conclusions on <strong>Google</strong> articles and videos from official channels. However, none of the sources guarantees that the implementation of the recommendations will improve your ranking in search results.</p><h3>Meta tags</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/673/1*LYxoWNSzbO49IWkQya8wyg.png" /></figure><p>There are dozens of articles that advise on using these tags correctly and all of them agree that <strong>‘Title’</strong> is the most important meta tag for every web site. I won’t describe the general suggestions in much detail — check the official <a href="https://support.google.com/webmasters/answer/79812?hl=en">Google page</a> for more information.</p><p>Instead, I’d like to highlight a few points below:</p><ul><li>Always implement <a href="https://support.google.com/webmasters/answer/79812?hl=en"><strong>meta tags</strong></a>. <strong>Title</strong> and <strong>description</strong> are crucial for <strong>Google</strong> and other search engines.</li><li>Leave the <strong>keyword</strong> meta tag in the past as it’s been 10 years since it’s <a href="https://datadrivenlabs.io/blog/meta-keyword-tag-google-2018/">deprecated for Google</a>. Consider keeping it only if you want to promote your site for other search engines. In my opinion, even if the engine supports the <strong>keyword</strong> tag, it’s useless to stuff it with all your keywords. Remember — content is <strong>king</strong>.</li><li>Provide a unique <strong>title</strong> and <strong>description</strong> for every page even if your site is an <strong>SPA</strong>. The meta title displays as a name in your browser tab and serves as a navigation element for users in some way.</li><li>Close your site to <strong>Google</strong> until you are ready to make it live. I saw it many times when websites were visible in Google although they were still under construction. It’s really hard to make <strong>Google</strong> forget the test information on your pages, so if you are working on a server that’s visible to Google, use <a href="https://support.google.com/webmasters/answer/93710?hl=en">meta robots</a> to hide it from <strong>Google Bot</strong>.</li><li>If your site is in several languages, use <a href="https://support.google.com/webmasters/answer/189077?hl=en">rel=”alternate</a>. Also, I’d recommend always using the lang attribute &lt;html <strong>lang</strong>=”en-US”&gt;.</li><li>Favicon is important. In 2019, <strong>Google</strong> has <a href="https://www.blog.google/products/search/new-design-google-search/">announced</a> a new look for Google Search Console, therefore, make sure <a href="https://realfavicongenerator.net/favicon_checker">to check your site</a> for favicon.</li></ul><p>There are a lot of other meta tags. For example, <a href="https://ogp.me/">Open Graph</a> for social networks or <a href="https://www.dublincore.org/specifications/dublin-core/dces/">Dublin Core</a>, however, I would recommend using only base meta tags: “<strong>title</strong>”, “<strong>description</strong>” + <strong>Open Graph</strong>.</p><h3>Headings</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1021/1*lyptn0RBnZVPvmSN_5XV7w.png" /></figure><p>From my point of view, it is the holiest war topic of all time. There have always been two camps since <a href="https://developer.mozilla.org/en-US/docs/Web/Guide/HTML/HTML5">HTML5</a> was introduced. People from the first camp believe that you can use as many <strong>&lt;h1&gt;</strong> tags as the layout requires; those in the second camp believe that there should be strictly one <strong>&lt;h1&gt;</strong> per page.</p><p>Let’s take a look at what we have.</p><p>For example, here’s the official answer from <a href="https://twitter.com/JohnMu?s=20">John Muller</a>, a Webmaster Trends Analyst at Google:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1021/1*y3pJE6HGZL4c3Zdc-1tWLw.png" /></figure><p>Also, you can take a look at the video from <a href="https://www.youtube.com/watch?v=GIn5qJKU8VM">Web Masters channel</a> or <a href="https://www.youtube.com/watch?v=oe334miJxqg">Google Russia</a>.</p><p>Many websites use multiple <strong>&lt;h1&gt;</strong> in their <strong>HTML</strong>. For example, every slide on <a href="https://www.mercedes-benz.com/en/">Mercedes</a> has a unique <strong>&lt;h1&gt;</strong> tag.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*qu-kG60n8bFsB0os" /></figure><p>Still, a lot of people still believe that Google cares about the number of <strong>&lt;h1&gt;</strong> you use. Come on :)</p><p>From my experience, you can use <strong>&lt;h1&gt;</strong> as many times as your semantic layout requires. According to the <a href="https://dev.w3.org/html5/html-author/">HTML5 Doctype</a>, the article tag could contain many h1 tags as you can see in these <a href="https://www.w3.org/TR/2011/WD-html5-author-20110809/the-article-element.html">examples</a>.</p><p>So, it’s better to decide on the number of &lt;h1&gt; based on your design.</p><p><strong>Exception:</strong> if your website supports assistive technologies, I would recommend developing a heading hierarchy from the beginning of a page start and use only one <strong>&lt;h1&gt;</strong>. It’s safer because some old screen readers do not understand a multiple <strong>&lt;h1&gt;</strong> hierarchy on the page and may interpolate the results in the wrong way.</p><h3>HTML5 Tags</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1020/1*wnnogK_MHj-KypWGuUVXgQ.png" /></figure><p>Don’t be afraid of using <a href="https://www.w3schools.com/tags/tag_header.asp"><strong>&lt;header&gt;</strong></a>, <a href="https://www.w3schools.com/tags/tag_footer.asp"><strong>&lt;footer&gt;</strong></a>, <a href="https://www.w3schools.com/tags/tag_section.asp"><strong>&lt;section&gt;</strong></a>, <a href="https://www.w3schools.com/tags/tag_article.asp"><strong>&lt;article&gt;</strong></a> tags on your page because they help users and improve your rank in Google search results. Here’s a pre-launch checklist that you can use before going live.</p><ol><li><strong>Validate all pages</strong>. Of course, there could be some errors with an iframe or third-party plugins, but unclosed tags and hidden characters are more important. Don’t trust any plugins, always validate your pages on the official <a href="https://validator.w3.org/">Markup Validation Service</a>. Plugins could use the old base of rules and not correctly see HTML of the page.</li><li><strong>Check the structure</strong>. Use <a href="https://gsnedders.html5.org/outliner/">HTML5 Outliner</a> to check how the headings are connected with HTML5 tags like section, articles.</li><li><strong>Ensure web accessibility</strong>. Check your site with a <a href="https://wave.webaim.org/">Web Accessibility Evaluation Tool</a> for issues with web accessibility and headings on your site.</li><li><strong>Improve page loading time</strong>. Check your page with <a href="https://developers.google.com/speed/pagespeed/insights/">PageSpeed Insights</a>. We’ll take a closer look at it in the next chapter.</li></ol><p>An interesting point about &lt;<strong>b&gt;</strong>, &lt;<strong>strong&gt;</strong>, &lt;<strong>i&gt;</strong> and <strong>&lt;em&gt; </strong>tags.</p><p>“Whenever we checked, “<strong>strong</strong>” and “<strong>b</strong>” were the exact same in terms of ranking and scoring and how they’re indexed and all that sort of stuff. And you could use either one, and it wouldn’t make a difference in terms of Google ranking.” <a href="https://www.youtube.com/watch?v=awto_wCeOJ4">link to video</a></p><p>But let me say it one more time, the content is king.</p><h3>Page Speed</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1020/1*8cEaTypkcPmM_Riy3Gxc-A.png" /></figure><p>First of all, the page speed is important for users as <strong>47%</strong> of people expect a web page to load in two seconds or less.</p><p>Check your site with <a href="https://developers.google.com/speed/pagespeed/insights">Page Speed Insights</a>, and you will see a long list of issues that you have. Also, keep in mind that Google started indexing websites by their mobile version <a href="https://webmasters.googleblog.com/2020/03/announcing-mobile-first-indexing-for.html">this year</a> so make sure the mobile version of your website works well.</p><p>Here are some <strong>tips</strong> <strong>for your website optimization</strong>:</p><ul><li><strong>Optimize graphics</strong>. Images may take 90% of the whole weight of the page so it’s really important to use correct formats and <a href="https://2frontend.info/how-to-optimize-images-on-your-site-for-different-screens-and-devices/">responsive image approach</a>.</li><li><strong>JavaScript</strong> <strong>costs</strong>. Addy Osmani <a href="https://medium.com/@addyosmani/the-cost-of-javascript-in-2018-7d8950fbb5d4">wrote an article</a> and elaborated why JavaScript is so expensive. I would recommend reducing the usage of JavaScript to a minimum.</li><li><strong>Do not use HTML5 videos at all</strong>. Really. Instead, use services like YouTube or Vimeo for video — they will do all the optimization work for you.</li><li><strong>Use asynchronous download</strong> for most of the resources and third-party components on your page. <a href="https://github.com/verlok/lazyload">Lazy load</a> helps you to reduce the number of images on the first load of the page and increase the page speed.</li><li><strong>Think twice before using third parties on your website</strong>. It’s mostly chats that reduce your page speed. Some of them could upload the whole libraries and font packs as dependencies. If you really need that chat, load it asynchronously on some action: scroll down 10px, or button click.</li></ul><p>If you work with a design team, discuss page speed optimization at the initial stage of design work and before the development. Otherwise, you will spend dozens of hours fixing and rebuilding your structure.</p><h3>JS + SEO</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1020/1*0ifJ0FIu-phAq9z4_h4OKg.png" /></figure><p>Unfortunately, websites are increasingly getting built as <strong>SPA</strong>s without any optimization for <strong>SEO</strong>.</p><p>It is too hard to fix an already built <strong>Web APP</strong> that <strong>Google</strong> has already indexed or not indexed. So if you are going to use JS frameworks, investigate tools for pre-rendering content. There are a lot of videos on <a href="https://www.youtube.com/playlist?list=PLKoqnv2vTMUPOalM1zuWDP9OQl851WMM9">Google Webmaster</a> channel where <strong>Google</strong> specialists communicate their vision.</p><p>Here are the most important things regarding <strong>JS</strong> + <strong>SEO</strong>:</p><ul><li>If your website uses <strong>JS</strong> for content loading or written in <strong>Angular</strong>, <strong>Vue</strong>.js, <strong>React</strong> (or any other framework), make sure that all of your pages could be rendered by Google bot. An easy way to do this right now is to paste your website URL in <a href="https://search.google.com/test/mobile-friendly">Mobile Friendly Test</a> tool and get the results. If you will see the page upon finishing, then Google can render your website. Anyway, I would recommend using <a href="https://medium.com/@baphemot/whats-server-side-rendering-and-do-i-need-it-cb42dc059b38">SSR</a> if you want to be 99% sure that your content will be indexed by Google.</li><li><strong>Try not to overload your site with JS</strong>. Remember, <a href="https://v8.dev/blog/cost-of-javascript-2019">JS costs</a>. A lot of animations and interactions can be done with CSS or even dropped.</li><li><strong>Use services to track issues</strong>. Your users will leave the site if they see an error page loading and you would have never guessed why statistics are going down. So, use trackers for your website. For example, <a href="https://sentry.io/welcome/">Sentry.io</a> provides you a good set of tracking tools.</li></ul><p>A lot of information on this topic is available on <a href="https://webmasters.googleblog.com/search/label/javascript">Official Google Blog</a> and <a href="https://www.youtube.com/playlist?list=PLKoqnv2vTMUPOalM1zuWDP9OQl851WMM9">YouTube channel</a></p><h3>Bottom line</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Cy6nKOK5vmohbUxp63EJ2g.jpeg" /></figure><p>So you can see that frontend affects how Google will rank your site. At the same time, even if you have implemented all recommendations from <a href="https://developers.google.com/search/docs/guides/get-started">Google</a>, you may not achieve the desired results.</p><p>Here’s a <a href="https://docs.google.com/spreadsheets/d/1tTfU0TOaF-BeuQU5iziNUTGmnE56WwHPFIKQzh4dykw/edit?usp=sharing">checklist</a> that you can share and use with your team to make sure nothing was missed. Also counts abstract scores for your website :)</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8123513fd6ba" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Web Starter Kit in help]]></title>
            <link>https://medium.com/@stanislavgurin/web-starter-kit-in-help-6afe99d33859?source=rss-77c30067bec2------2</link>
            <guid isPermaLink="false">https://medium.com/p/6afe99d33859</guid>
            <category><![CDATA[gulp]]></category>
            <category><![CDATA[optimization]]></category>
            <category><![CDATA[github]]></category>
            <category><![CDATA[npm]]></category>
            <category><![CDATA[javascript]]></category>
            <dc:creator><![CDATA[Stanislav Gurin]]></dc:creator>
            <pubDate>Fri, 16 Aug 2019 15:10:03 GMT</pubDate>
            <atom:updated>2019-08-16T15:10:03.166Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*4MS78iy_jxTFwEz8" /><figcaption><a href="https://github.com/justcoded/web-starter-kit">https://github.com/justcoded/web-starter-kit</a></figcaption></figure><p>Hi, there.</p><p>In the next pages, I am going to share our experience with the custom Gulp Build <a href="https://github.com/justcoded/web-starter-kit">https://github.com/justcoded/web-starter-kit</a>. We have been using and supporting for the last 4 years on <strong>FrontEnd</strong> projects that ranged anywhere from 1 to 40 pages, <strong>70%</strong> <strong>Markup</strong> and <strong>30%</strong> <strong>JS</strong>. It is a story of fails and successes that I believe will help you find a happy medium when it comes to deciding on when to use or not to use <strong>Gulp/Grunt/WebPack</strong> in your project.</p><p>Four years ago we faced issues of huge projects, tons of code, libraries that are needed to be automated. At the same time we decided to use <strong>SCSS</strong> as the main preprocessor, <strong>ES6</strong> for <strong>JS</strong>, and use the component approach in the development for all of our projects. What we needed to <strong>automate</strong>:</p><ul><li>First of all, we use <strong>SCSS</strong> in all of our projects by default. Because of <strong>SCSS,</strong> we need to compile it into pure <strong>CSS</strong> that the browser can understand.</li><li>Second, we need to add vendor <a href="https://developer.mozilla.org/en-US/docs/Glossary/Vendor_Prefix">prefixes</a> to the styles that the browser does not support. Thank God only a few browsers require these dozens of repeatable lines of code.</li><li>Third, we want to use modern JS standards but with browser support for outdated browsers. So, we needed the module to transpile <strong>JS</strong> into <strong>ES5</strong> that supports most of the browsers that we are supporting.</li><li>Also, we needed to compress <strong>JPG/PNG/SVG</strong> and linting for JS/HTML.</li></ul><p>At that time I had a negative experience with Grunt and do not want to use it.</p><p>As one of the famous physics sad:</p><blockquote>Make everything as simple as possible, but not simpler</blockquote><blockquote>- Albert Einstein</blockquote><p><a href="https://webpack.js.org/"><strong>WebPack</strong></a> was raw and unstable. So, there was only one candidate — <a href="https://gulpjs.com/"><strong>Gulp</strong></a>. Four years later and I still don’t regret ever deciding that projects without <strong>JS</strong> <strong>frameworks</strong> is good.</p><p>So, after the choice has been made, we start developing our Web Starter Kit (<strong>WSK</strong>). We decided to choose GitHub as the main version system.</p><p>Here are the top 5 challenges that we faced while developing:</p><h3>1. Standards</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/953/0*U64PlBQrPOot1QmC" /></figure><p>If you want to keep your code clean and supported by other developers you need to follow standards/guidelines.</p><ul><li>Because of <strong>SCSS,</strong> we follow <a href="https://sass-guidelin.es/">https://sass-guidelin.es/</a> by <a href="http://hugogiraudel.com/">Hugo Giraudel</a>. From my point of view, they’re the best guidelines for <strong>SCSS</strong> at the moment. Simple, easy to read and the main thing is that it works on small projects and 40+ pages.</li><li>For <strong>JS</strong> we fall in love with <a href="https://github.com/airbnb/javascript">https://github.com/airbnb/javascript</a>. Right after we added <a href="https://www.npmjs.com/package/gulp-eslint">ES lint</a> with <a href="https://www.google.com/search?client=firefox-b-d&amp;q=eslint-config-airbnb-base">es-lint-config-airbnb-base</a> into our build.</li><li>For <strong>HTML</strong> we used <a href="https://www.npmjs.com/package/gulp-file-include">gulp-file-include</a> and always separate <strong>HTML</strong> for small reusable components.</li></ul><p><strong>CSS </strong>after a long time discussing it with the team we decided to use mixed methodology- like <strong>BEM + CSS</strong> reset and small cascade styles that should be separated into components. With CSS reset and using cascade we are more flexible that with strict <strong>BEM</strong> which denies using any global styles.</p><h3>2. File Structure</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/957/0*CaDFzh62WTZQbGwn" /></figure><p>The First version of WSK had spaghetti code :(. It means that all tasks were in one file and we did not separate them into files. After a couple of months of using it, we realized that it was our fail and put them into task folder. As for our source code, we put all of them into src/ folder. As you can see now it has a simple intuitive folder structure <a href="https://github.com/justcoded/web-starter-kit/tree/master/src">https://github.com/justcoded/web-starter-kit/tree/master/src</a>. The main rule was that we could not put sources with build files. No sooner had you started the build, it compiled all of the sources into assets/ folder on the root level of our structure.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/878/0*EJOSTB2qxWehzvy4" /><figcaption>The structure of the root directory</figcaption></figure><h3>3. Vendors</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/762/0*CJuEFgbYAR3Oubx4" /></figure><p>There are tons of plugins in projects that we are developing and we do not want to put our vendors files with our source code files. From the very beginning, we decided to use <a href="https://bower.io/"><strong>Bower</strong></a> for frontend plugins but lately, we replaced it with <a href="https://docs.npmjs.com/misc/registry"><strong>NPM</strong></a>. So, the first part of the job has already been done :) The next step was to separate vendors steam with sources. We created a folder, <a href="https://github.com/justcoded/web-starter-kit/tree/master/src/vendor_entries">vendor_entrites</a>, where the developer can paste links to plugin files and it would be compiled into a separate file called <a href="https://github.com/justcoded/web-starter-kit/blob/master/index.html">vendors</a> vendor.min.js or vendor.min.css Another important thing is that we do not use <a href="https://www.npmjs.com/package/uglify-js">Uglify</a> or <a href="https://www.npmjs.com/package/gulp-babel">Babel</a> for vendors. If you are going to use some compressors for plugins then make sure that it is not already minified.</p><h3>4. Documentation</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/832/0*iePRtt1EzVMd0LcY" /></figure><p>If you want people to use your build than write simple documentation. Otherwise, you will never remember what each feature was for or how to change routes in your build. In the beginning, we did not have time for documentation because we needed to quickly start our projects that would be based on it. With time we started to write the documentation and believe me I had no idea how to write it because for me, it was obvious how everything was supposed to work :) So, to be frank I found Google WSK <a href="https://github.com/google/web-starter-kit">https://github.com/google/web-starter-kit</a> and copy-paste documentation and re-wrote it.</p><p>When I found <a href="https://github.com/google/web-starter-kit">Google WSK</a> it was similar to what we had been developing. At that time my hands dropped. Why do I need to develop a WSK if it has already been done? We wanted to support our build by ourselves, and make it faster than Google’s. After 2-month Google <a href="https://developers.google.com/web/tools/starter-kit/">had stopped supporting</a> the build and we were happy to support our WSK :)</p><p>Let’s get back to the documentation. We did the same as Google did, divided everything and described each part in detail. Also, we described all of our releases and used tags for releases.</p><h3>5. Images vs Prefixes</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*eQqT2CyLGuHf8Sa6" /></figure><p>The specifics of our projects which we always have to deal with including a huge amount of images and the support of outdated browsers. With the support of outdated browsers, we integrate <a href="https://www.npmjs.com/package/gulp-autoprefixer"><strong>Gulp Autoprefixer</strong></a> and always update our browser list file according to our current support. It is a really important thing because vendor prefixes could take half of your code. Next year we are going to get rid of it because only a small part of the browsers are still using prefixes.</p><p>As for the images, it was a year-long nightmare. First of all, the image compression task requires a lot of performance to do it. Also, we had the next issues:</p><ul><li>In some project where there were 50+ images, we had to wait up to 30 minutes until the compressor finished the task.</li><li>SVG images did not compress correctly. For SVG images we used <a href="https://www.npmjs.com/package/gulp-svgmin">gulp-svg-min</a> and in some cases, it had magically broken the images.</li><li>Module sometimes does not compress the images. Magic :)</li><li>Algorithms that plugin is used are not working as we expected. For example, <a href="https://www.jpegmini.com/">https://www.jpegmini.com/</a> shows good results with lossless mode</li></ul><p>After a couple months of fighting, we decided to remove <strong>SVG</strong> compression and set the compression level to almost zero. So, now the <strong>WSK</strong> just copies the images from the src/ folder into assets. From my point of view, images should be optimized on the server-side or third parties with the effective private algorithm of compression.</p><p>What about numbers? We have spent around 3 weeks for the first build and on day a month for maintenance. At the same time, we develop NPM packages called<a href="https://www.npmjs.com/package/jcn"> jcn</a> where users can choose what type of <strong>WSK</strong> they want. Now we support only simple starters and a WordPress starter that is different only due to the tasks because for we do not need to optimize our assets for WP. Optimizing assets is a <strong>WP</strong> part of the job :)</p><p>What do we have in total? We have spent around a couple of hundred hours for <strong>WSK</strong> and finally got a flexible build that helps us to use modern features with easy on start.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6afe99d33859" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Design and Development How To Make Them Friends]]></title>
            <link>https://medium.com/@stanislavgurin/design-and-development-how-to-make-them-friends-6cbe0a2aec0e?source=rss-77c30067bec2------2</link>
            <guid isPermaLink="false">https://medium.com/p/6cbe0a2aec0e</guid>
            <category><![CDATA[sketch]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[assets]]></category>
            <category><![CDATA[development]]></category>
            <dc:creator><![CDATA[Stanislav Gurin]]></dc:creator>
            <pubDate>Fri, 09 Aug 2019 15:55:53 GMT</pubDate>
            <atom:updated>2019-08-09T15:55:53.314Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/848/1*lVTtZBEaRCdf0kwJQR26ww.png" /><figcaption>Image Credit: <a href="https://blog.proto.io/">proto.io</a></figcaption></figure><p>In order to achieve optimal performance and keep the customer happy it is advised to follow these guidelines. Before deploying, check if you have added these functionalities, and add them if you didn’t. Follow these guidelines to achieve the optimal performance and to keep your client happy. Before you deploy anything, make sure to implement everything described below. These are the things that our clients do not usually ask for, however, they add quality to our work and add value.</p><h3>1. The Design</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*pgXPktDD9mLSuzlzTJifYw.png" /></figure><p>A lot of time has passed since the developers worked in the same editors as the designers. Now we have powerful instruments such as <strong>Sketch, AdobeXD</strong>, old school <strong>Photoshop</strong> for the designers and much simpler tools such as <strong>Zeplin</strong>, <strong>Avocode</strong>, and <strong>Invision</strong> for the developers. Also, I cannot ignore Figma as it’s becoming more and more popular, it is an all-in-one platform with a lot of benefits for developers and designers.</p><p><strong>Zeplin</strong>, <strong>Avocode</strong>, <strong>Invision</strong> do not have superfluous stuff for the developers, just export, take sizes, margins etc. Everything you need in one place and you do not have to know how to turn off layers or save masks with multiply effect on it 🙂 So, the sources for the design is not necessary for developers now, just export to one of the most popular space and provide the link to it.</p><h3>2. The Assets</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*aMIaduIQFKQHHlaC.png" /></figure><p>Developers spent a lot of time getting icons, images and other assets from the design. Usually that time does not include getting into the total project estimate time because we assume that all assets will be provided from the client’s side. In case with Photoshop the developer does not have another choice except manually transform layers into images with appropriate formats. That is why <strong>Photoshop</strong> is old school in nowadays and this part of work is already done in modern design editors.</p><p><strong>Zeplin</strong> provides more powerful interfaces to for? the developers but in Sketch file all images and icons should be exportable, and the designer or developer should click on every layer “Make Exportable” only after that the will become accessible in <strong>Zeplin</strong>. My worst nightmare was when I received a huge Sketch file and spent almost a day clicking on images, icons and masks to make them exportable. So, do not forget to provide all the assets with the design or make them exportable in the source design.</p><h3>3. Vector Images</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*YV47LrrAxAwbOrJv.png" /></figure><p>We are living in the century of devices that have 2x and more device pixel ratio. It means that we should use <strong>SVG</strong> format for icons, masks, logos wherever we can. There are a lot of icon packs that are already ready for integration into the site. Developers becoming angry when they see icons in raster format, because it will be blurred on devices. For all small graphic like icons, logos it is better to use <strong>SVG</strong> or some of icon fonts pack.</p><h3>4. Effects</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*PVevg441tcS1OMLJ.png" /></figure><p>Another problem with the designs that are coming from the Photoshop layers using effects on layers. For example you have images and masks with the multiply effect . So, you are trying to slice or at least get settings and you cannot because multiply is connected with the layer under it. Not all browsers support effects on layers, so it is better to not use them separately.</p><h3>5. Fonts</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/709/0*5ou863g8baqneQRb.png" /></figure><p>The fonts should be provided with the design. Without original fonts developers cannot export the original <strong>Sketch</strong> file into <strong>Zeplin</strong>, <strong>Avocode</strong>, <strong>Invision</strong> etc., with original view of the text view. So, if you will provide source of the design than always provide fonts that have been used.</p><h3>6. Style Guide</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*WqkkshqPAlkmwlX9.png" /></figure><p><strong>Style Guide</strong> is the key to success! When the development team has all views of the main components from the design it is really easy to develop every page like a constructor.<br> Also, should it is better to have mobile and tablet styles guides separately from the desktop.</p><h3>7. Hidden Layers</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*0qjy96BaZWDWYZ6y.png" /></figure><p>Hidden layers always confuse. That is why always should be screens of all states, pop ups, tooltips in the project. From my point of view it’s better not to use hidden layers at all. Use separate <strong>artboard</strong> or layer groups but do not hide them.</p><h3>8. Text</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1016/0*NbCoJGVPUoukcz7p.png" /></figure><p><strong>Lorem ipsum</strong>, in graphical and textual context, refers to filler text that is placed in a document or visual presentation. Without context it is hard to find out the semantic value of the block.</p><p>For example, there is a form:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/507/0*rScunRsfTA5nJl7O.png" /></figure><p>Can you imagine lorem ipsum fields in this form? In that case you will never guess what type of fields these would be or what the purpose of this form is. That is why original text is important in the design. Also, semantic text helps to understand where the links are and what the buttons do. Keep in mind the text is important.</p><h3>9. Responsive</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/766/0*AjFFyNB_6-SLRhW6.png" /></figure><p>It is probably the hardest topic of the whole article. We have collected all the main issues with what our team faced last time.</p><ul><li>There are the following dimensions in px for Mobile <strong>320/375/414</strong>, Tablet 768/1024, Desktop 1280/1440/1920 so every dimension means breakpoint where the site should be rebuild.</li><li>Do not hide the blocks on mobile/desktop view. On the mobile view should be the same content as on the desktop. You can transform list of post into gallery if they are not important but never just remove them.</li><li>Do not move sections from one block to another. Webpage already has the grid and it is hard to move block form on row to another. For example, if you have desktop view with the image on the left side (1) and heading (3) with some paragraph (4)(5). On mobile view it transform into 1 column and image appears between heading (3) and paragraph (4) inside the container (2).</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*o_Lh9raxKPn4U5qm.png" /></figure><ul><li>All the texts should be the same across all responsive views of the design. Responsive could be develop in desktop or mobile first. It means that the developer starts from desktop or mobile view and it is really confusing when there is different text between two resolutions in the same block.</li><li>Use the same factor for all sizes.</li></ul><h3>10. Specification</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/965/0*Tu8kEO7hN8wfm-VV.png" /></figure><p>Any specification would help. In our fasting growing word we cannot image a website without animations. In order to be on the same page with the design we have to have animation specification with examples or animation wireframes that show us how it should work. That is why it is so important to have a document with detailed description of the animation effects, rollovers, form steps, etc.</p><h3>Results:</h3><p>So, let’s summarize what could increase development process:</p><ol><li>All views in <strong>Zeplin/Avocode/InVision</strong> with already exportable assets</li><li>Fonts should be provided including all font styles (italic, bold, medium etc.)</li><li>Icons should be separately in <strong>SVG</strong></li><li><strong>Animation</strong> references must be. Help your team to understand how it should be.</li><li><strong>Style Guide</strong> could be really helpful</li><li>UX Text is everywhere. No more “<strong>Lorem Text</strong>”.</li><li>Information is never useless (<strong>Maps theme name, Highlight Code theme</strong> name if one of these were used)</li></ol><p>Make sure to share down in the comments design mistakes that we do on a daily basis so others can learn from them too.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6cbe0a2aec0e" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How To Estimate Your Task]]></title>
            <link>https://medium.com/@stanislavgurin/how-to-estimate-your-task-e35ff1741e27?source=rss-77c30067bec2------2</link>
            <guid isPermaLink="false">https://medium.com/p/e35ff1741e27</guid>
            <category><![CDATA[project-management]]></category>
            <category><![CDATA[estimations]]></category>
            <category><![CDATA[agile]]></category>
            <dc:creator><![CDATA[Stanislav Gurin]]></dc:creator>
            <pubDate>Fri, 09 Aug 2019 15:55:15 GMT</pubDate>
            <atom:updated>2019-08-09T15:55:15.215Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*Yj2RvGvk0XqSbj6q" /></figure><p>Clients, managers, and maybe even you want to know when the task will be ready. The first step is the most crucial of any development process. Without a timeline, you can’t start any part of the work. It can be measured in any number of units, such as <strong>hours, days, weeks, point, elephants</strong>.</p><p>In the next <strong>10 minutes</strong>, I am going to share one of the approaches for estimating any part of the work on your project.</p><p>First of all, we need to write down our results somewhere. Don’t judge me, but I am a big fan of<strong> Google Sheets</strong>. With the help of <strong>Google Sheet</strong>, you can do everything from small to big :)</p><p>If you do not have your estimate table you can use this one <a href="https://docs.google.com/spreadsheets/d/1d3FKbr6zeHlz6BxxIgjYBFz-K55wrXp5LFF3RFseUok/edit#gid=342802380">https://docs.google.com/spreadsheets/d/1d3FKbr6zeHlz6BxxIgjYBFz-K55wrXp5LFF3RFseUok/edit#gid=342802380</a>. I would recommend using the example or use the same types of columns and rows in yours.</p><p>As you can see there are two main columns <strong>Realistic</strong> and <strong>Pessimistic. What they are for?</strong></p><p>In the <strong>Realistic</strong> column, you should calculate the time that you need for the development component with small risks.</p><p>The <strong>Realistic</strong> column of the estimated time should include:</p><ul><li><strong>Time</strong> for development current feature</li><li><strong>TIme</strong> for upload/merge/fix conflict (if you do not have <strong>CI/CD</strong> on the project hehe:)</li><li><strong>Time</strong> for fixes after <strong>QA</strong> checks</li><li><strong>Time</strong> for Tests (if this applies to your project)</li><li><strong>Time</strong> for the <strong>Reports/Documentation</strong>. Depends on your working flow model.</li><li><strong>Time</strong> for communication with the client (calls, e-mails, etc.)</li><li><strong>Scrum activities</strong> (daily stand-up with the team, retro, demo, etc.)</li></ul><p>That list doesn’t include everything that should be taken into account for estimated time as it certainly depends on your workflow. In some companies, there are no scrum activities and it might be okay. I would recommend adding at least 20% of the time to all of the lists without the development. Keep in mind that for some components/pages/modules you may need more time to read documentation or figure out how the components work.</p><p>In the <strong>Pessimistic </strong>column, you should write the same as on <strong>Realistic</strong> but with the risks. For example, you will have to develop 3D Gallery and you have never developed it. Of course, you will need time to find the right plugin or modify an exciting one. It that case the risks would be higher than the standard <strong>20%. In other cases, usually, I</strong> add around 10–20%. If the component is really easy to develop I put the same time as in the realistic column.</p><p>What should be in the <strong>Pessimistic </strong>column<strong>:</strong></p><ul><li>Any part of the other component. If you estimate the header, the estimate should include the development of the header not for modals, popups, animations, etc. I would recommend writing down modals/popup separately on the next line of the table.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/696/0*dMMCizjiK8SS18al" /></figure><ul><li>Do not add in all risks. If your risks are more than 100% of the Realistic, it is a red flag to put them into a separate table or review it with the client to find the missing parts of the puzzle.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/705/0*GQ0xEO9mzmR7UEc_" /></figure><p>Generally speaking, this approach can be used for any phase of the project. You can use Google Sheet, Excel or just a piece of paper.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*UpqjPsn1PeCuSbdE" /></figure><p>Lastly, here are my <strong>recommendations</strong>:</p><ul><li>Try to <strong>decompose</strong> your tasks. If it’s a page that separates into small components, such as sections, pop-ups, modules, animations and if the estimate of the one row is more than <strong>24–32h,</strong> I separate it into small parts. Any of the project requirements like old school browser support or print version could be estimated at the end of the components list.</li><li>Do not forget that some of the estimates can be separated from the component in the estimate but not in the development. For example, you cannot leave IE11 browser support as a task that needs to be done at the end of the sprint because it’s something that needs to be taken into account while developing the component.</li><li><strong>Round the numbers</strong>. 0.2, 0.3, 0.4. It’s hell when you have 7.99 hours of 1/35 of the day. Round all number into 0.5 or 1h.</li><li>If you cannot estimate a functionality or component but the estimate is necessary, you can provide an estimate based on your experience or estimates some of the examples. Do not forget to make a note about it and notify your manager. I use a note or comment on a row or just type comments into the next column</li><li>If you are not more than <strong>60%</strong> sure that the component or the page would be than write a question to the <strong>manager</strong>/<strong>client.</strong> Do not pile everything into the risks.</li><li>The name of the rows should be semantic. For pages, you can use the name of the page or section names. <strong>Section</strong>, <strong>Block</strong>, <strong>Form</strong> are common names and it’ll be tough to figure out what you’re referring to. Just write down prefixes. <strong>Contact Block</strong>, <strong>Team Section</strong>, <strong>Team Gallery</strong> are more semantic names that help you to identify what has been estimated.</li><li>Do not write<strong> Backend Estimate</strong> into a separate document. It sounds strange I know. All of the estimates should be done within one document otherwise you will not see what component you will have to work with the BE developer or where the bottleneck is.</li><li>You <strong>should</strong> always have a range of numbers. The world is not a dreams castle and unicorns do not fly the streets. There are always risks even if you’ve done it before and have scripts there are a lot of circumstances that simply do not depend on you.</li><li>Before estimating, carefully read all of the project requirements. Small text at the end of the document could be the hardest feature that you have ever done</li></ul><p>These <strong>rules</strong> and <strong>examples</strong> will help you quick start your project estimate, without the headache.</p><p>If you have any questions or want to share your experience, please feel free to contact me.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e35ff1741e27" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Top 5 Tips on How To Optimize Your Images for Web]]></title>
            <link>https://medium.com/@stanislavgurin/top-5-tips-on-how-to-optimize-your-images-for-web-15e4f9b20c32?source=rss-77c30067bec2------2</link>
            <guid isPermaLink="false">https://medium.com/p/15e4f9b20c32</guid>
            <category><![CDATA[responsive]]></category>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[optimization]]></category>
            <category><![CDATA[image]]></category>
            <category><![CDATA[google]]></category>
            <dc:creator><![CDATA[Stanislav Gurin]]></dc:creator>
            <pubDate>Fri, 02 Aug 2019 15:49:03 GMT</pubDate>
            <atom:updated>2019-08-02T15:49:03.702Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*A5eNUVdA_7269GjERvlYow.png" /></figure><p>The topic “<strong>How to optimize your site for better load speed</strong>” is a hot one in all chats and forums. <strong>Google</strong> has announced that page speed is now the main factor for <strong>Google Search</strong> and <strong>Google Ads</strong>. Here is the link for proof: <a href="https://developers.google.com/web/updates/2018/07/search-ads-speed">https://developers.google.com/web/updates/2018/07/search-ads-speed</a> Also, almost 50% of users will not wait more than <strong>3 sec</strong> for a page to load <a href="https://www.marketingdive.com/news/google-53-of-mobile-users-abandon-sites-that-take-over-3-seconds-to-load/426070/">https://www.marketingdive.com/news/google-53-of-mobile-users-abandon-sites-that-take-over-3-seconds-to-load/426070/</a></p><p>In the next <strong>15 minutes</strong>, we will figure out how to increase your page speed by <strong>optimizing images</strong>.</p><p>First of all why are images important? Because the images could take up to 90% of the whole site. You can check it by using one of the hundreds of resources to check. For example, here is what Microsoft’s offering <a href="https://tools.pingdom.com/#5b135290a1000000">https://tools.pingdom.com/#5b135290a1000000</a></p><p>What is the effect of <strong>not</strong> optimizing your graphics:</p><ul><li><strong>Page loads slow.</strong> The user will not wait until the page loads and closes the window.</li><li>A lot of <strong>lags</strong> in the browser. The browser will spend more resources rendering the images..</li><li><strong>Google rank </strong>will go down because of speed. If the page doesn’t load in <strong>2–4 seconds</strong>, then it won’t matter how much money you spend on advertisement</li></ul><p>Now, keeping the above in mind, what can we do?</p><h3>1. Use Asynchronous Load For Graphics</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/871/0*YwX5JAsEYVIJ3pzh" /></figure><p>The <strong>images</strong> will load only when it shows in the browser’s viewport. No need to load all images on the first load if there is a risk that the user will not scroll to them. <br>It is almost native and you can use this without <strong>plugins</strong> <a href="https://addyosmani.com/blog/lazy-loading/">https://addyosmani.com/blog/lazy-loading/</a>, if you want support for other browsers you can use <strong>plugins</strong>. I would recommend <a href="https://github.com/verlok/lazyload">https://github.com/verlok/lazyload</a> It supports different types of images with media queries.</p><h3>2. Use the different format of Images</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/766/0*RHvsEvVRurrnyEDi" /></figure><p>Not only <strong>JPG</strong>, <strong>PNG</strong>, <strong>SVGs</strong> are used on the web:</p><ul><li><strong>WebP</strong> <a href="https://developers.google.com/speed/webp/">https://developers.google.com/speed/webp/</a>. It is a really powerful format that maintains a decent amount of quality after compression. Unfortunately, the Safari browser does not support it <a href="https://caniuse.com/#feat=webp">https://caniuse.com/#feat=webp</a> but you can use other formats as a fallback.</li><li><strong>JPEG2000</strong> <a href="https://caniuse.com/#search=jpeg2000">https://caniuse.com/#search=jpeg2000</a>. This format could be used as the fallback for Safari instead of <strong>WebP.</strong></li><li><strong>JPEG XR</strong> <a href="https://caniuse.com/#search=jpg%20XR">https://caniuse.com/#search=jpg%20XR</a>. It’s the same as <strong>JPEG200</strong> but for IE/EDGE browsers.</li></ul><p>By the way, it is one of the most important tests that Google Page Speed checks <a href="https://prnt.sc/on0zhj">https://prnt.sc/on0zhj</a>.</p><h3>3. Use compression</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*vqnoztRy8Oav8Dun" /></figure><p>Use <strong>compression</strong>. For example, let’s take a look at <a href="https://www.apple.com/">https://www.apple.com/</a> and download that image</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*ztTbtmHytYzvbXlU" /></figure><p>And upload it to the <a href="https://tinypng.com/">https://tinypng.com/</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*3c5_FJgnDHuhl-ZL" /></figure><p>We have saved <strong>39%</strong> and the difference between them is subtle</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*3beS2984irWVmjQT" /></figure><h3>4. Responsive Images</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*btOtqbcY67OOwKa8" /></figure><p>Six years ago not all sites were responsive and there weren’t a lot of mobile versions of the site where you could choose what size of images would be uploaded. Now almost <strong>100% </strong>of websites are responsive and there exists a conversion from mobile to desktop. That is why we have to take into account different screen resolutions.</p><p>For example, you have a <strong>100%</strong> width block with a background image on it. If you upload 1920 x 1080 image for the desktop mobile user will not be happy because they would have 1920 image on their <a href="https://www.paintcodeapp.com/news/ultimate-guide-to-iphone-resolutions">https://www.paintcodeapp.com/news/ultimate-guide-to-iphone-resolutions</a> 375px or 414px screens and that is more than <strong>3x </strong>bigger than the display could show. That is why we need to use different screen resolutions for different types of devices. Here is an article from our blog with a code example that you can take a look at. <a href="https://2frontend.info/how-to-optimize-images-on-your-site-for-different-screens-and-devices/">https://2frontend.info/how-to-optimize-images-on-your-site-for-different-screens-and-devices/</a></p><p>From my point of view, responsive images are the main issues of a lot of sites. Of course, it takes time but you have to care about your users and provide them the content as fast as you can.</p><h3>5. Image hosting</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/791/0*w3xnk37lR2XCPQJw" /></figure><p><strong>A content delivery network</strong> (<strong>CDN</strong>) could be a good way to deliver static content to your users. There are a lot of companies that offer <strong>CDN</strong>. If your site does not have dozens of images it could be useless and expensive for your product because of the price.</p><p>So what is the most important way to optimize your images? All of them!! Use all of the progressive approaches to deliver content to your users. Raise the bar!!</p><p>P.S <strong>Please visit</strong> our blog <a href="https://2frontend.info/tags/">https://2frontend.info/tags/</a>, where you can find unique articles with examples made by ourselves in <strong>VR, 3D, JS.</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=15e4f9b20c32" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[PWA, Push Notifications & The Dark Side]]></title>
            <link>https://medium.com/@stanislavgurin/pwa-push-notifications-the-dark-side-8ded10ea6751?source=rss-77c30067bec2------2</link>
            <guid isPermaLink="false">https://medium.com/p/8ded10ea6751</guid>
            <category><![CDATA[push-notification]]></category>
            <category><![CDATA[pwa]]></category>
            <category><![CDATA[mobile]]></category>
            <category><![CDATA[html5]]></category>
            <category><![CDATA[javascript]]></category>
            <dc:creator><![CDATA[Stanislav Gurin]]></dc:creator>
            <pubDate>Fri, 02 Aug 2019 15:46:56 GMT</pubDate>
            <atom:updated>2019-08-02T15:46:56.308Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*JmSJfzgXntpquNS076OnTQ.png" /></figure><p>A couple of months ago we received a request for the development of push notifications in a PWA (Progressive Web Application). The main idea was to increase the conversion of users by adding notifications about new products. The website was built on a CMS with a standard tech stack (HTML5/CSS3 + JS + jQuery).</p><p>I don’t want to go too deep into what push notifications are, however, you can find a lot of technical articles about it. For example <a href="https://medium.com/better-programming/everything-you-need-to-know-about-pwas-push-notifications-e870bb54e14f">https://medium.com/better-programming/everything-you-need-to-know-about-pwas-push-notifications-e870bb54e14f</a></p><p>My main focus is to share our experience with push notifications to help save you time.</p><p>So let’s get back to our story :) We had little experience with push notifications in PWAs at that time, so we decided to develop a small prototype to play around with and here is what we found out:</p><p>Naturally, we support <strong>iOS</strong> and <strong>Android</strong> <strong>OS</strong>, so let’s begin.</p><p><strong>Android</strong>, <strong>pros</strong>:</p><ul><li>Push notifications work</li><li>You can subscribe for push notifications in the browser or inside the PWA</li><li>The difference between the system and PWAs is subtle.</li></ul><p><strong>Cons:</strong></p><ul><li>Push notifications work only if the <strong>Web Application </strong>is opened. There is a high risk the if the user closes your application, they would be waiting for a notification that will never come.</li></ul><p>Because the <strong>PWA</strong> uses Chrome when you are removed or subscribe on any notifications it is also would have an effect on your PWA.</p><p><strong>iOS</strong>, pros</p><ul><li><strong>None</strong></li></ul><p><strong>Cons</strong>:</p><ul><li><strong>iOS</strong> does not support the push notification API <a href="https://caniuse.com/#feat=notifications">https://caniuse.com/#feat=notifications</a> so you will not be able to subscribe.</li></ul><p>Let’s recap what we’ve learned thus far- <strong>Push notifications</strong> will work on <strong>Android OS-</strong>based devices only if the <strong>PWA</strong> window isn’t closed by the user. Also, we will have to take into account that notifications will work on desktops but are users subscribe for them</p><p>I want to add a couple of lines about <strong>PWAs</strong>:</p><ul><li><strong>PWA</strong> is not a native Application. It does not have its own cache and uses <strong>Chrome</strong> (on Android) and <strong>Safari</strong> (on iOS) browsers.</li><li><strong>Apple</strong> always breaks the <strong>PWA</strong> support on iOS because of the App Store.</li><li><strong>PWA</strong> is not a magic tool that can be used instead of a Native App.</li></ul><p><strong>PWA</strong> is a <strong>Dream City</strong> where users can easily “install apps” without downloading through the store. Could it be realized in a couple of years? What is the benefit of the <strong>App Store </strong>and <strong>Google Play Market </strong>if users don’t install apps through their stores? There are many questions left unanswered, such as what will happen to <strong>PWAs</strong> in the future?</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8ded10ea6751" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Top 5 Common Mistakes On Your Frontend Career Start]]></title>
            <link>https://medium.com/@stanislavgurin/top-5-common-mistakes-on-your-frontend-career-start-9718549d1072?source=rss-77c30067bec2------2</link>
            <guid isPermaLink="false">https://medium.com/p/9718549d1072</guid>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[html]]></category>
            <category><![CDATA[front-end-development]]></category>
            <category><![CDATA[css]]></category>
            <dc:creator><![CDATA[Stanislav Gurin]]></dc:creator>
            <pubDate>Wed, 24 Jul 2019 17:00:57 GMT</pubDate>
            <atom:updated>2019-07-24T17:08:37.044Z</atom:updated>
            <content:encoded><![CDATA[<p>When I started my career as a markup developer 10 years ago there weren’t any courses, mentoring institutes, conferences or videos on YouTube. We had to deal with every bug by ourselves which included long nights of experimenting with the console to fix <strong>IE</strong>. There weren’t any debug tools and IE6 was the main browser. Can you imagine that? I remember when the firebug console appeared in the first <strong>Firefox</strong> version. We bought a bottle of wine and celebrated all night long. Nowadays people have all of the good stuff for a quick start in their career as a <strong>QA/FE/BE/PM</strong>. However, on the way to the dream city you’ll notice there are a lot of hidden treats under the hood.</p><p>Let’s find out what the most common cases look like that can knock you off the path to being a Frontend developer.</p><h3><strong>1. The Basics</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/760/0*63yEClVJ1GQVyUwT" /></figure><p>Based on my personal experience you will gain more profit if you invest your time into the basics. Everything is constantly changing, frameworks come out with new documentations every 2–3 years, leaving a lot of reading in between updates. Do browsers change quickly? Thank God — no. Issues, protocols, and architectures has been pretty much the same in the last 5 years.</p><p>Take a look at the <strong>Frontend</strong> roadmap <a href="https://github.com/kamranahmedse/developer-roadmap">https://github.com/kamranahmedse/developer-roadmap</a>, it’s perfect :)</p><p>Here is a shortlist that will help you get a good start in your career:</p><ul><li>If you write <strong>HTML</strong> then you must know tags. You can find a lot of articles on the internet about <strong>Doctype</strong> but I prefer the original <strong>source</strong> <a href="https://www.w3.org/TR/2014/REC-html5-20141028/">https://www.w3.org/TR/2014/REC-html5-20141028/</a></li><li>For every page, styles are necessary so <strong>CSS</strong> is truly important <a href="https://www.w3schools.com/css/">https://www.w3schools.com/css/</a></li><li>Also, you can find some basic about the web in general <a href="https://internetingishard.com/html-and-css/basic-web-pages/">https://internetingishard.com/html-and-css/basic-web-pages/</a></li><li>Not one project could be developed without a version of control. The most popular now is <a href="https://githowto.com/">https://githowto.com/</a></li><li>JavaScript <a href="https://javascript.info/">https://javascript.info/</a> I like that site, there are a lot of example with explanations</li><li>Of course <a href="https://stackoverflow.com/">https://stackoverflow.com/</a>, here you can find answers to any question but be careful, almost <strong>90%</strong> is not good if you’re looking for a quick “copy-paste” solution for your code.</li><li>Almost <strong>60–80%</strong> of webpages is images, so you have to deal with image optimization and formats. There is no perfect site that I can recommend as there are dozens of them, but you have to know web formats <strong>JPG</strong>, <strong>SVG</strong>, <strong>PNG</strong>, <strong>WebP</strong> as well as which cases you need to use one of them.</li><li>Nowadays everything needs to automatize, so there is a 99% risks that you will use gulp/webpack in your project. You can easily build your own build <a href="https://gulpjs.com/docs/en/getting-started/quick-start">https://gulpjs.com/docs/en/getting-started/quick-start</a> or use one of the most popular. For example, <a href="https://github.com/justcoded/web-starter-kit">https://github.com/justcoded/web-starter-kit</a></li><li><strong>CSS</strong> with superpowers hehe :) <a href="https://sass-lang.com/">https://sass-lang.com/</a> Just try it and you will never have to use <strong>CSS</strong> again. Guidelines from Hugo <a href="https://sass-lang.com/">https://sass-lang.com/</a> also helps you build a flexible architecture for projects.</li></ul><p>I can continue this list with hundreds of links, but it is not the main task for today. Just try to ask yourself how everything works under the hood and you will open the magic world of the <strong>WEB</strong> ;)</p><h3><strong>2.</strong> <strong>In a Nutshell</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/750/0*RLq63JV6P3cGYV2g" /></figure><p>Let’s take a look at simple contact form:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/708/0*t8J7aNamfSJXU0xM" /></figure><p>Which fonts are used in the design? What about indents? Where are the rollovers or focus states? These are the most common questions that we ask when we see forms similar to the one above. Lets dive deep into it and review a few uncommon questions:</p><ul><li>Where should the data should be stored?</li><li>Is the data sensitive?</li><li>What will the <strong>response</strong> be from the server? We have to keep in mind that validation on the frontend could be easily removed by turning off <strong>JavaScript</strong> on the page. So, validation should always be on the server too.</li><li>What should be shown after the form is submitted?</li></ul><p>As you can see there are a lot of questions that come to mind even for a simple contact form. Always be conscientious and better understand business needs.</p><h3><strong>3. Estimate Your Work</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/833/0*5r7iuicGpdFo5acD" /></figure><p>Always estimate your work. You can try a simple approach that always works for me. Before you start any of the tasks create a simple google sheet with at least two columns: <strong>Realistic</strong> and <strong>Pessimistic</strong>. You should separate each of the pages or modules into small components and estimate them <a href="http://prntscr.com/od6lsu">http://prntscr.com/od6lsu</a>. <strong>Realistic</strong> is the time that you’re expected to finish if all goes well, while the <strong>Pessimistic</strong> column estimates how long it would take to finish everything plus risks.</p><p>This simple pattern helps you to see your real velocity and deviation coefficient from your estimate. Also, it can show you the bottleneck of your development process.</p><h3><strong>4. The Project Starts Not From the Code</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/871/0*Moxrq-X8S7elO0FH" /></figure><p>It’s true. Based on my personal experience, you’re very lucky if at least 60% of the project time is spent on the development. Meetings, project setup, architecture are not just “PM words”. It is a nightmare for every PM and developer to find out that a component doesn’t work at the end of the project and you have to re-write all of your code. These small steps will help you not fuck it up:</p><ul><li><strong>Know your customer</strong>. What is the main purpose of the website/application/form etc. What is the customer’s business? Remember that all IT products solve business needs, and I’ve yet yo meet someone who wanted to develop something without a purpose.</li><li><strong>Questions are everything</strong>. Take a look at the design, read all the documents carefully and prepare questions.</li><li><strong>Develop a roadmap</strong> for your project. You have to have a project plan that describes what has to be done and how long it will take.</li></ul><p><strong>What is expected from the client</strong>? You should have a clear idea of their expectations. Acceptance criteria are really important. You do not have to write long scroll documents. Just a couple of lines would be enough.</p><p>Do not forget<strong> </strong>about the <strong>Pareto Principle!</strong> :)</p><h3><strong>5. Start Small</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/760/0*DCIowJxnWoLsoyrg" /></figure><p>People always want to try something new and much bigger than what they’ve got. <strong>Frameworks</strong> and <strong>libraries</strong> can give you this fake feeling that building an application is no big deal. All you need to do is copy the code and paste it into your editor, right? Wrong. In some cases, this is the last resort approach but on a daily basis, it doesn’t work that way and you will have tons of code that no one can support.</p><p>There are some easy tricks that help you build a space rocket:</p><ul><li>Always separate <strong>modules</strong> into small components. Each of the components should do some easy part of work. There are a lot of patterns even in <strong>CSS</strong>. For example, you can use <a href="https://en.bem.info/methodology/quick-start/">BEM methodology </a>or some <a href="https://addyosmani.com/resources/essentialjsdesignpatterns/book/">JS Patterns</a>.</li><li><strong>The Component</strong> should be finished. Don’t take it all in a row. Select components and finish it completely. For example, navigation. It could be a really big component with a lot of drop-downs or additional items. Anyway, try to finish it in one day with <strong>responsive</strong>, <strong>scripts</strong> and <strong>PX-Perfect</strong>.</li><li><strong>Test</strong> your code every day. Open your <strong>webpage</strong>, <strong>resize</strong>, check the console. There are dozens of checklists for every type of project. You can use your own. Even when using a modern framework a broken button can easily fail on your demo.</li><li><strong>Performance</strong>. People want to see results as quickly as possible. Google decreases page rank for slow pages. Your page should be loaded in 2–3 secs. You can use tons of approaches for page speed optimization (<a href="https://developers.google.com/web/fundamentals/performance/lazy-loading-guidance/images-and-video/">lazy loading</a>, <a href="https://2frontend.info/how-to-optimize-images-on-your-site-for-different-screens-and-devices/">responsive images approach</a>, etc.). Performance starts from the optimization of each of the components :)</li></ul><p>Make it simple. If <strong>jQuery</strong> is enough for your project then use it. Businesses don’t normally care what technology has been used in the solution, so if it works and it’s easy to support than use it.</p><p>Of course, there will be a lot of walls you’ll need to break on the way, however, what’s most important is that you like what you’re doing. You will be always surrounded by other people who can help you on your way.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9718549d1072" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>