<?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 Filippo Scelfo on Medium]]></title>
        <description><![CDATA[Stories by Filippo Scelfo on Medium]]></description>
        <link>https://medium.com/@filipposcelfo?source=rss-682ba16b44aa------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*6lW5WG-kGTWaeXbWYGG1Bg.jpeg</url>
            <title>Stories by Filippo Scelfo on Medium</title>
            <link>https://medium.com/@filipposcelfo?source=rss-682ba16b44aa------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 23:23:20 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@filipposcelfo/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[Hands-on CSS and design principles.]]></title>
            <link>https://medium.com/@filipposcelfo/how-to-get-started-with-css-12c9c14ab8c4?source=rss-682ba16b44aa------2</link>
            <guid isPermaLink="false">https://medium.com/p/12c9c14ab8c4</guid>
            <dc:creator><![CDATA[Filippo Scelfo]]></dc:creator>
            <pubDate>Wed, 23 Nov 2016 04:54:07 GMT</pubDate>
            <atom:updated>2016-11-28T06:00:23.060Z</atom:updated>
            <content:encoded><![CDATA[<h3>Part 1:</h3><h3>How to get started with CSS.</h3><p>The best way to get started with CSS is to actually play with it. The best way to start playing with it is using <strong>Chrome Developer Tools</strong>.</p><blockquote>The Chrome Developer Tools (DevTools for short), are a set of web authoring and debugging tools built into Google Chrome. The DevTools provide web developers deep access into the internals of the browser and their web application. Use the DevTools to efficiently track down layout issues, set JavaScript breakpoints, and get insights for code optimisation.</blockquote><h3>Ready. Set. Go</h3><h4>1. So lets start by visiting any web page using Google Chrome and type the secret keyboard shortcut to access Chrome Dev Tools:</h4><h4>command + shift + C</h4><p>(Or you can be boring and right click on the page and then select “Inspect”)</p><h4>2. On your right hand side you’ll see a panel with the styles tab selected. Here’s where the magic happens. Change any CSS styles in there.</h4><p>Voilá</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*X4J6nOSrDVSMxPSRKmARmA.gif" /></figure><p>Chrome Dev Tool is the best way to get started with writing and understanding CSS.However your changes will be gone as soon as you refresh the page. To fix that we can use another tool called <strong>Labcoat.</strong></p><h3>Part 2:</h3><h3>Prototyping in production with Labcoat</h3><p>Labcoat is a web editor and a chrome extension that lets you redesign any website using CSS/JS.</p><p>Simply choose your target site and write <em>just the changes</em> in the Web Editor. Modify colours and fonts, update text, insert or remove elements — anything you can do with CSS and JS.</p><p>Need jQuery? No problem, add any external library. Labcoat also supports Less, Sass, CoffeeScript, and Javascript ES6 (via Babel).</p><p><strong>Website:</strong> <a href="https://labcoat.io/">www.labcoat.io</a><br><strong>Chrome extension:</strong> <a href="https://chrome.google.com/webstore/detail/labcoat/hidalhjdenohbkmadhjpcldoaljkakhj">https://chrome.google.com/webstore/detail/labcoat/hidalhjdenohbkmadhjpcldoaljkakhj</a></p><h4>Have fun!</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Nsz0THJeItQIzCTmd4F7NA.gif" /></figure><h3>Part 3:</h3><h3>Hands-on design</h3><p>Hands-on design is all about understanding the basic principles for designing web or app interfaces.</p><p>If you ever tried to design interfaces for the web or apps before you probably asked yourself the same questions as all of us:</p><p>What <strong>colour</strong> do I pick?<br>What <strong>font size</strong> should I use for headings?<br>How much <strong>margins</strong> is too much…<br>Hang on do I use <strong>margins</strong> or <strong>paddings</strong>?</p><h4>So, yeh… Let’s get some sh*t done!</h4><h4>Let’s take the following ugly screen (empty html file) to the next level.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/417/1*c-4-05gwxvwxXbwYkdlKCA.png" /></figure><h3>Some context</h3><p>To be continued…</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=12c9c14ab8c4" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Prototype in Production.]]></title>
            <link>https://medium.com/@filipposcelfo/day-1-prototype-in-production-3c21d1a418aa?source=rss-682ba16b44aa------2</link>
            <guid isPermaLink="false">https://medium.com/p/3c21d1a418aa</guid>
            <category><![CDATA[chrome]]></category>
            <category><![CDATA[css]]></category>
            <category><![CDATA[prototype]]></category>
            <category><![CDATA[labcoat]]></category>
            <category><![CDATA[chrome-dev-tools]]></category>
            <dc:creator><![CDATA[Filippo Scelfo]]></dc:creator>
            <pubDate>Fri, 04 Nov 2016 00:58:42 GMT</pubDate>
            <atom:updated>2016-11-23T04:44:37.057Z</atom:updated>
            <content:encoded><![CDATA[<p>CSS &amp; Design Workshop at <em>Redbubble — Day 1</em></p><h3>How to get familiar with CSS</h3><p>In this session we’ll learn about tools that help us <strong>prototype in production</strong> so we can get started with <strong>CSS</strong> and get some sh*t done! 😎</p><p>We’ll also cover some design principles to guide you when thinking about typography, colours and spacing.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/320/1*fUJXcGYaisZu-jarTU9Z4A.gif" /></figure><h3>Ready. Set. Go!</h3><p>The first and quickest tool to get started with prototyping in production is <strong>Google Chrome Dev Tools</strong>.</p><h4>1. So lets start by visiting any web page and type <strong>the secret keyboard shortcut</strong>: command + shift + C</h4><h4>2. On your right hand side you’ll see a panel with the styles tab selected. Here’s where the magic happens. Change any CSS styles in there.</h4><p>Voilá</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*JWNpFKY0LLla6SZr4i3Iaw.gif" /></figure><blockquote>Google Chrome Dev Tools are probably the best way to start playing and learning CSS. It gives you suggestions and shows you what properties are available so you don’t have to know every single line of CSS . It’s the quickest way to get feedback if you’d like to try or learn something.</blockquote><h3>“Yeah yeh ok that’s cool, but when I refresh the page I loose my changes…”</h3><p>Well there is a tool for that. It’s called <strong>Labcoat</strong>.</p><h3>Lab what?</h3><p><strong>Labcoat</strong> lets you write your own CSS styles (and Javascript) and because it has extensions you add to your browser, Labcoat <strong>will keep whatever styles </strong>you add to the site<strong> even if you refresh </strong>the page, <strong>or restart</strong> your browser <strong>or</strong> you got so exited after using Labcoat you went full weird and <strong>decided to burn the all thing down</strong>. <em>Your changes will still be there.</em></p><p>Let’s get started with Labcoat.</p><h4>1. Go to <a href="https://labcoat.io/">https://labcoat.io</a></h4><h4>2. Login with your LastPass account. Use designers@redbubble.com</h4><h4>3. Click on “prototypes” and then “Create prototype”</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gCYSuYgg_mDVNb2FepKGyQ.png" /></figure><h4>4. Write whatever changes you wanna make</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*lNXDTavVSsZiGfXvjUgdrQ.png" /></figure><p>One last step…</p><h4>5. To view your changes you’ll need to add the extension for Google Chrome.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4Mvpg950yYNmcDxpCSMhbA.png" /></figure><h4>6. Go back to the site you want to style and enable Labcoat.</h4><p>Tadá…</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*cliJUqZyLRvbK8aoQZrmWw.gif" /></figure><h3>Just wow! Am I right?</h3><blockquote><strong>The only problem </strong>I have with Labcoat is that it is very <strong>hard to share</strong> your style changes <strong>with other people</strong>.</blockquote><h3>“Great… So now, how do I make it cool?”</h3><h3><strong>1. Colours</strong></h3><p><strong>Don’t reinvent the wheel</strong>. Google has done lots and lots of research around design. Visit <a href="https://material.google.com/style/color.html">https://material.google.com/style/color.html</a> to learn about colours. You can pretty much choose whatever colour you want from there and apply it to your designs. It’s a perfect starting point and easy to share.</p><h4><strong>Quick overview:</strong></h4><p>It’s best practice to choose 2 colours that work harmoniously with each other. The idea is to have a <strong>primary</strong> colour and an <strong>accent</strong> colour.</p><h4><strong>Primary color</strong></h4><p>When using a primary colour in your palette, this colour should be the most widely used across all screens and components.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/375/1*oHd7MkbGnGbbTZCyrSBcyQ.png" /><figcaption><em>Example of a primary colour palette with variations for when a darker or lighter version of the colour is needed.</em></figcaption></figure><h4>Accent color</h4><p>Palettes with a secondary colour may use this colour to indicate a related action or information. The secondary colour may be a darker or lighter variation of the primary colour.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/375/1*mNoYQ3f56cLKA010aM4eig.png" /><figcaption>Example of a secondary palette with variations for when a darker or lighter version of the colour is needed</figcaption></figure><h4>Some examples</h4><p>Limit your selection of colours to three hues from the primary palette and one accent colour from the secondary palette.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*d8vhQeX_A-wfi5R-Sh09dg.jpeg" /></figure><h3>2. Typography</h3><p>Once again. <strong>Don’t reinvent the wheel</strong>. Same thing here, just visit <a href="https://material.google.com/style/typography.html">https://material.google.com/style/typography.html</a> to learn more about typography and what font size to use and when.</p><h4>Quick overview:</h4><p><strong>Too many type sizes and styles at once can wreck any layout</strong>. A typographic scale has a limited set of type sizes that work well together along with the layout grid.</p><p>Best practice is to pick 2 font sizes for<strong> headings</strong>. 1 consistent font size for the <strong>body text</strong> and 1 font size for <strong>buttons or links</strong>. You wight need more but use this as a guide to start with and if you need more then make a case for it. Keep it simple is the goal!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ru5Uat00Gx9bW_HGl66kUw.png" /><figcaption>The basic set of styles are based on a typographic scale of 12, 14, 16, 20, and 34.</figcaption></figure><h3>3. Spacing</h3><p>Believe it or not spacing between elements is <strong>the most important</strong> thing for achieving great design. Good spacing around the content improves everything about it.</p><p>Think of spacing as a repeatable unit. You want everything to be proportional… Our brain freaking loves proportions!</p><h4>How to use units</h4><ol><li>Pick a unit.</li><li>Multiply or divide your unit to get whatever spacing you need.</li><li>Stick with it!</li></ol><blockquote><strong>Tips</strong>: The most common unit used for web is 16px.</blockquote><h4><strong>Let’s say you want some small spacing between elements:</strong></h4><p>You can just divide 16px by 2 to get 8px.<br>Boom!! 8px is your number.<br><strong>Not 9px, 10px or 11px. Freaking 8!<br></strong>So why 8px? unit(16px) / 2.</p><h4>What about edge cases?</h4><p>Use <strong>0.5</strong> to increment your unit by <strong>(1.5, 2.5, 3.5, etc…)</strong> as well as using round numbers <strong>(2, 3, 4, etc…).</strong></p><p><strong>For example:</strong></p><p>16px * 1.5 = 24px<br>16px * 2 = 32px<br>16px * 2.5 = 40px<br>16px * 3 = 48px</p><h4>Yes it’s that simple!</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/375/1*Y2z0TRwCiaxHeYEVHUeREg.png" /></figure><blockquote>Screen edge left and right margins: <strong>16px (Unit)</strong><br>Content left margin from screen edge: <strong>72px (Unit * 4.5)</strong></blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/375/1*SbJuiMqNZlcQ9qfZ49keow.png" /></figure><blockquote>1) Status bar: <strong>24px (Unit * 1.5)</strong><br>2) Toolbar: <strong>56px (Unit * 3.5)</strong><br>5) Space between content areas: <strong>8px (Unit / 2)</strong><br>3) List item: <strong>72px (Unit * 4.5)</strong></blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/375/1*T0TcPJSqtN5p8pjGRehGEQ.png" /></figure><blockquote>Avatar: <strong>40px (Unit * 2.5) </strong><br>Icon: <strong>24px (Unit * 1.5)</strong><br>Touch target on both: <strong>48px (Unit * 3)</strong></blockquote><h3>We’re done. Have fun! 🤘😎🤘</h3><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3c21d1a418aa" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>