<?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[Fort Awesome Articles - Medium]]></title>
        <description><![CDATA[Thoughts &amp; tips on front end design and development. From the folks who bring you Font Awesome &amp; Fort Awesome. Find us at https://fontawesome.io and https://fortawesome.com. - Medium]]></description>
        <link>https://medium.com/fort-awesome?source=rss----e3c6b1226ade---4</link>
        <image>
            <url>https://cdn-images-1.medium.com/proxy/1*TGH72Nnw24QL3iV9IOm4VA.png</url>
            <title>Fort Awesome Articles - Medium</title>
            <link>https://medium.com/fort-awesome?source=rss----e3c6b1226ade---4</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 11:24:12 GMT</lastBuildDate>
        <atom:link href="https://medium.com/feed/fort-awesome" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Fort Awesome Acquires Symbolset!]]></title>
            <link>https://medium.com/fort-awesome/fort-awesome-acquires-symbolset-72229dab2c13?source=rss----e3c6b1226ade---4</link>
            <guid isPermaLink="false">https://medium.com/p/72229dab2c13</guid>
            <category><![CDATA[fort-awesome]]></category>
            <category><![CDATA[icons]]></category>
            <category><![CDATA[design]]></category>
            <dc:creator><![CDATA[Dave Gandy]]></dc:creator>
            <pubDate>Wed, 10 Aug 2016 19:30:11 GMT</pubDate>
            <atom:updated>2016-08-10T19:32:19.610Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*R4fKd6ecblOQvjIKPzThkA.png" /></figure><blockquote>I come from a planet of outlaws. Billie the Kid. Bonnie &amp; Clyde. John Stamos.</blockquote><p>We’ve kept this under wraps for a bit, but today we’re crazy-super-excited to announce that <strong>Fort Awesome has acquired the Symbolset marketplace!</strong></p><p>And we have lots of Awesome things planned.</p><h3>About Symbolset</h3><p>For those of you not familiar, Symbolset sells absolutely gorgeous icon sets with a hefty dose of ligatures magic. Whatever style of icons your site needs, Symbolset likely has. If you haven’t already, you really gotta <a href="https://symbolset.com/">see it in action</a>. And while you’re there, make sure to check out the <a href="https://symbolset.com/icons">icon sets</a>.</p><p>What first drew us to Symbolset (aside from the impeccable, meticulously-crafted, intuitive-to-use icons) is the original purpose:</p><ol><li><em>Make great icon design available to the world.</em></li><li><em>Make icons semantic, meaningful, and accessible to humans and machines alike.</em></li><li><em>Make icons easy to implement and technology-agnostic.</em></li><li><em>Make icon design a viable profession for talented icon designers.</em></li></ol><p>It’s amazing how well this matches our philosophy when we’re designing Font Awesome. <strong>And we’re ecstatic to remain loyal to Symbolset’s original purpose.</strong></p><h3>What This Means</h3><p>We’re committed to making Symbolset the de-facto place to buy the world’s best icon sets. So we’re investing heavily in the platform.</p><p>We’ve started by adding Black Tie (our commercial multi-weight icon set in <a href="https://symbolset.com/icons/black-tie-solid">Solid</a>, <a href="https://symbolset.com/icons/black-tie-bold">Bold</a>, <a href="https://symbolset.com/icons/black-tie-regular">Regular</a>, and <a href="https://symbolset.com/icons/black-tie-light">Light</a>), complete with shiny-new, magical ligatures support. And we’ll be adding more sets just as fast as we can.</p><p>For existing users, not much will change right away. You’ll still have access to all of your purchased icon sets. You’ll start seeing more sets come online soon, and any technology improvements will be backported to existing sets.</p><p><strong>A huge thanks to the absolutely talented, spectacular, amazing designers on Symbolset. You really need to check out their work:</strong></p><ul><li><a href="https://symbolset.com/icons/standard">Standard</a> by Mike Fortress</li><li><a href="https://symbolset.com/icons/symbolicons-line">Symbolicons Line</a>, <a href="https://symbolset.com/icons/symbolicons-block">Symbolicons Block</a>, <a href="https://symbolset.com/icons/forecast">Forecast</a>, <a href="https://symbolset.com/icons/junior">Junior</a>, <a href="https://symbolset.com/icons/air">Air</a>, and <a href="https://symbolset.com/icons/elements">Elements</a> by Jory Raphael</li><li><a href="https://symbolset.com/icons/pika">Pika</a> and <a href="https://symbolset.com/icons/gizmo">Gizmo</a> by Dutch Icon</li><li><a href="https://symbolset.com/icons/steedicons">Steedicons</a> by Kyle Steed</li><li><a href="https://symbolset.com/icons/geomicons-squared">Geomicons Squared</a> by Brent Jackson</li><li><a href="https://symbolset.com/icons/glyphish">Glyphish</a> by Glyphish</li><li><a href="https://symbolset.com/icons/community">Community</a> by Wen Ping Huang</li></ul><p>We’ve got a lot more in the works for Symbolset. So stay tuned.</p><p><em>For all the latest news, follow us at </em><a href="https://twitter.com/getfortawesome"><em>@getFortAwesome</em></a><em> and </em><a href="https://twitter.com/symbolset"><em>@Symbolset</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=72229dab2c13" width="1" height="1" alt=""><hr><p><a href="https://medium.com/fort-awesome/fort-awesome-acquires-symbolset-72229dab2c13">Fort Awesome Acquires Symbolset!</a> was originally published in <a href="https://medium.com/fort-awesome">Fort Awesome Articles</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Custom icons — now with less frustration]]></title>
            <link>https://medium.com/fort-awesome/custom-icons-now-with-less-frustration-31313c39fef3?source=rss----e3c6b1226ade---4</link>
            <guid isPermaLink="false">https://medium.com/p/31313c39fef3</guid>
            <category><![CDATA[svg]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[fort-awesome]]></category>
            <dc:creator><![CDATA[Rob Madole]]></dc:creator>
            <pubDate>Fri, 05 Aug 2016 16:43:45 GMT</pubDate>
            <atom:updated>2016-08-09T14:39:42.415Z</atom:updated>
            <content:encoded><![CDATA[<p>Recently we had one of our customers contact us through support to tell us that a tall custom icon he was uploading using Fort Awesome’s copy-n-paste feature was landing in the EM box on the left and stubbornly refusing to center and trim itself.</p><p>This is what we wanted:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*TVzfpScwM4Yd4uir85kj1g.png" /><figcaption>Centered with no padding on either side of the icon</figcaption></figure><p><strong>tldr;</strong> We have deployed some fixes to our custom icon engine that makes this <em>just work</em>. The rest of this article unpacks some common use cases our customers have.</p><p>This is what we got:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*S8j1WXxF3lqz8lTRz5S7kQ.png" /><figcaption>See all that spacing on the right? Not what we want.</figcaption></figure><p>This was happening because we were not respecting the viewBox of the SVG file or scaling the vector icon correctly. <strong>We think we’ve fixed all of this.</strong></p><h4>What’s a viewBox?</h4><p>Imagine a nice landscape. This happens to be Estes Park, Colorado.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*svrDeidY-7OJxH8Uf2mvZg.jpeg" /><figcaption>Credit Peter Roome <a href="https://www.flickr.com/photos/roome">https://www.flickr.com/photos/roome</a></figcaption></figure><p>The viewbox for an SVG file works like a window. It designates what part of the underlying image (or icon in our case) that we care about.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*e0BiRxYvC4CBG6QAyqXH5w.png" /></figure><p>It’s on the <em>root element</em> of the SVG.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*elMLISzCnGcloHLtMVyb0g.png" /><figcaption>viewBox=”0 0 201.87 1008&quot;</figcaption></figure><p>Our lightsaber viewBox starts in the upper-left corner <strong>(0, 0)</strong> and draws a rectangle to <strong>201.87, 1008</strong>. Our width is 201.87 units and the height is 1008 units.</p><p>In Illustrator we see the viewBox represented by the artboard.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*phUhDjq1T4kxRl0Of42cGA.png" /><figcaption>The artboard matches our SVG’s viewBox: <strong>0 0 201.87 1008</strong></figcaption></figure><h3>I want to…</h3><p>With that introduction out of the way let’s talk about how we can accomplish some of the common use cases that our customers have.</p><ol><li>Fill the available space</li><li>Control the whitespace</li><li>Make a wide icon</li><li>Exceed the boundaries</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hkQ41NF2-JwuUmtjs9CpwA.png" /><figcaption>Four use cases and their examples</figcaption></figure><p>These examples and the source files can be found here:</p><ul><li><a href="http://codepen.io/robmadole/pen/PzyRdw">See them being used on codepen.io</a></li><li><a href="https://gist.github.com/robmadole/8b570489ba87f27a7a06c777cdf700b8">Get the source files from gist.github.com</a></li></ul><h4>Fill the available space</h4><p>This is the most common usage that we see in Fort Awesome. Just fill the icon’s area with my artwork and don’t include any whitespace.</p><p>To accomplish you can 1.) copy from Illustrator or Sketch and 2.) paste it into the custom icon inside of Fort Awesome.</p><h4>Control the whitespace</h4><p>There are times when you don’t want the icon to fill the entire width and height available.</p><p>To accomplish this you should use the artboard of your editor (Illustrator or Sketch) and adjust it to visually match your desired result. Then export or “Save as” the icon to an SVG file. <strong>This is an important step as the exporting of the file creates the correct viewBox for your artwork</strong>.</p><h4>Make a wide icon</h4><p>This comes up pretty often for customers who have text-based logos that are much wider than they are tall.</p><p>Treat this use case the same way you would control whitespace. Make the artboard exactly the size you want and export to an SVG file.</p><h4>Exceed the boundaries</h4><p>While less common than our other use cases it’s useful to occasionally put stuff outside the EM box.</p><p>To accomplish this simply size your artboard and then let your artwork fall outside of it. Export to an SVG file and then create your custom icon in Fort Awesome. We’ll make the icon match what you see in your editor.</p><p>We have deployed these updates to our system that should have your custom icons behaving more predictably. Try it out and <a href="/service/mailto:support@fortawesome.com">let us know</a> if you have any unexpected problems or it just doesn’t work like you think it should.</p><p>Not a Fort Awesome customer? If you want to try this out <a href="https://fortawesome.com/start">sign up for a 14-day trial</a>. Plans start at $49 per year which will let you upload 20 custom icons.</p><p>Lightsaber by Uri Kelman and C-3PO by James Fenton from the Noun Project.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=31313c39fef3" width="1" height="1" alt=""><hr><p><a href="https://medium.com/fort-awesome/custom-icons-now-with-less-frustration-31313c39fef3">Custom icons — now with less frustration</a> was originally published in <a href="https://medium.com/fort-awesome">Fort Awesome Articles</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[No More Doc-Blocking: Shareable Doc & More in Fort Awesome!]]></title>
            <link>https://medium.com/fort-awesome/no-more-doc-blocking-shareable-doc-more-in-fort-awesome-a9228c792ae9?source=rss----e3c6b1226ade---4</link>
            <guid isPermaLink="false">https://medium.com/p/a9228c792ae9</guid>
            <category><![CDATA[design]]></category>
            <category><![CDATA[announcements]]></category>
            <category><![CDATA[documentation]]></category>
            <category><![CDATA[fort-awesome]]></category>
            <category><![CDATA[icons]]></category>
            <dc:creator><![CDATA[Brian Talbot]]></dc:creator>
            <pubDate>Thu, 04 Aug 2016 20:32:44 GMT</pubDate>
            <atom:updated>2016-08-09T21:23:13.687Z</atom:updated>
            <content:encoded><![CDATA[<blockquote>“I want to know what happened to the plans they sent you.”</blockquote><p>Our <a href="https://fortawesome.com/">Fort Awesome</a> users are, well, Awesome. They continuously help us take steps to make curating and managing the perfect set of <a href="https://fortawesome.com/sets">icons</a> and design assets easier. We know that using that perfect set effectively is just as important. So we beefed up the documentation included in every Fort Awesome kit. Here’s a rundown of what we rocked in docs…</p><h4><strong>More Comprehensive Documentation Right in Your Kit</strong></h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*cCU6qHQ9vQre7lJ7qk-dbg.png" /><figcaption>Learn how to get started building an awesome set of assets or dive into how to use each one specifically</figcaption></figure><p>We’ve expanded on the guides that show how to easily use your icons and typefaces. Using Fort Awesome-powered typefaces in your projects should be a lot clearer. We’ve also included help on how to get started with a new kit and how to troubleshoot common problems.</p><h4><strong>Shareable Kit Documentation</strong></h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Az-SGAgq3jZkqNDZysQo2w.png" /><figcaption>Sharable kit documentation brings teams together and avoids local file futzing</figcaption></figure><p>Every time you publish, we’ll update a unique URL to your kit that details your icons, typefaces, and how to use them. When you and your team are working on your project, this will be the place to go for how to use your up-to-date kit’s assets!</p><h4>Better Downloadable Demo Files</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4UX2IWTUkdsZ2DQzV8nnNQ.png" /><figcaption>The new downloadable demo is a living example of what your kit can do</figcaption></figure><p>For our <a href="https://fortawesome.com/start">Pro Plan customers and above</a>, we’ve improved the downloadable .zip copy of your kit. This now includes a demo.html file that shows off your kit’s inventory, gives you examples of our support styling, and easy copy+paste use while you’re offline or working locally.</p><h4>Use Icons on Your Desktop with Copy+Paste</h4><p>Fans of <a href="http://fontawesome.io/">Font Awesome</a> know how essential a <a href="http://fontawesome.io/cheatsheet/">desktop cheatsheet</a> is for easily copying and pasting icons into Adobe Creative Suite, Sketch, or other apps. Each kit’s documentation now includes copy controls to make short work of using your custom set of icons in your UI mockups, graphic designs, and presentations!</p><p>The new documentation improvements are on Fort Awesome now. Give them a try on your kit or project today. And remember, sharing (documentation) is caring!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a9228c792ae9" width="1" height="1" alt=""><hr><p><a href="https://medium.com/fort-awesome/no-more-doc-blocking-shareable-doc-more-in-fort-awesome-a9228c792ae9">No More Doc-Blocking: Shareable Doc &amp; More in Fort Awesome!</a> was originally published in <a href="https://medium.com/fort-awesome">Fort Awesome Articles</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How-To: Use Fort Awesome Icons]]></title>
            <link>https://medium.com/fort-awesome/how-to-using-fort-awesome-icons-f50ab11a2d2a?source=rss----e3c6b1226ade---4</link>
            <guid isPermaLink="false">https://medium.com/p/f50ab11a2d2a</guid>
            <category><![CDATA[icons]]></category>
            <category><![CDATA[how-to]]></category>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[fort-awesome]]></category>
            <dc:creator><![CDATA[Brian Talbot]]></dc:creator>
            <pubDate>Thu, 21 Jul 2016 20:14:08 GMT</pubDate>
            <atom:updated>2016-07-22T15:51:41.354Z</atom:updated>
            <content:encoded><![CDATA[<p>Let’s go through some basic steps and cases of using Fort Awesome icons on the web.</p><h4>Set Up</h4><p>Let’s assume you’ve made a Fort Awesome kit, (if not, <a href="https://fortawesome.com/start">its super easy to get started</a>). Make sure you have the most recent version of your kit ready for download by publishing any recent changes (new icons, name changes, etc.).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*DJuh-rpaWY_ceesPmc-GrQ.png" /><figcaption>Make sure to publish your kit if you make any changes or haven’t yet</figcaption></figure><p>After your kit has been published, copy your kit’s unique embed code. This can be found in your kit’s main navigation and will appear for you after your first publish of a kit.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*cAtb0ixtQ-GP802lUa_i2w.png" /><figcaption>Copy and paste your unique kit’s embed code — it’ll go into your project’s HTML</figcaption></figure><p>Paste your embed code into the HTML of your project. Make sure it goes near the top of your &lt;head&gt; tag.</p><pre>&lt;!DOCTYPE html&gt;<br>&lt;html&gt;<br>  &lt;head&gt;<br>    &lt;meta charset=&quot;utf-8&quot;&gt;<br>    &lt;title&gt;&lt;/title&gt;<br>    &lt;script src=&quot;[your_embed_code_goes_here]&quot;&gt;&lt;/script&gt;</pre><pre>    &lt;!-- other styling/JS/metadata goes here --&gt;<br>  &lt;/head&gt;<br>  &lt;body&gt;<br>    &lt;!-- page/view content goes here --&gt;<br>  &lt;/body&gt;<br>&lt;/html&gt;</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/687/1*lCfA2OxmVS_sN8A0gZnGQA.png" /><figcaption>Add your published kit’s embed code into your HTML</figcaption></figure><p><strong>A few notes before we proceed…</strong></p><ul><li>I’ll be using <a href="http://codepen.io/talbs/pen/ZOAVay">this Codepen example</a> throughout this article that you can reference at any time.</li><li>By default your kit’s icons will be given an HTML class attribute that starts with “fa-”. This is customizable and I’ve changed my kit’s icon prefix to be unique to my project (and to <a href="https://medium.com/p/f50ab11a2d2a/#ede7">avoid conflicts with using Font Awesome</a>). My example icons will start with this new prefix (“hwto-”).</li></ul><p>You’re now ready to insert icons into your project’s UI using simple pieces of markup like the following…</p><pre>&lt;!-- include both your icon prefix (hwto) and specific icon (hwto-twitter) --&gt;<br>&lt;i class=&quot;hwto hwto-twitter&quot;&gt;&lt;/i&gt;</pre><p>Its a great time to check out your kit’s unique online documentation, which contains an inventory of all of your icons and how to insert them. Your documentation also contains demonstrations of some of the utility styling bundled with your kit.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LWm7cvJ93hxGdI64TZzNpQ.png" /><figcaption>My example kit’s online documentation</figcaption></figure><h4>Included Styling Support</h4><p>As mentioned, your published kit provides some basic styling utilities. Incremental sizes, 90, 180, 270-degree rotating, and animations are included. <strong>See your kit’s documentation for the full list</strong>. You can add your own sizes (using CSS’s font-size property), transforms, and animations on top of these, of course.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/716/1*pXRWyDLFg0HSq8oRuaYUNw.png" /><figcaption>Using included utility styles to size, rotate, and spin kit icons</figcaption></figure><h4>Adding Color to Icons</h4><p>You can easily add color to your icons using CSS just as you would text. Create new <a href="https://developer.mozilla.org/en-US/docs/Web/CSS/color">CSS color</a> rules for any of the icons or HTML elements in your project.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*DmzJvmsOKHnYP57SA9T8hw.png" /><figcaption>Adding color on top of out-of-the-box icon styling</figcaption></figure><p>For extra credit, other display-related properties like opacity and animations can also be styled on top of the basic styling your Fort Awesome kit provides.</p><h4>CSS Only Icons</h4><p>If you’d prefer to not add extra HTML into your project’s code, you can include icons in your UI using just CSS. This requires 1) a few custom rules and 2) knowing the unicode glyph of the icon you want to use. Your kit’s documentation lists out the latter for all of your icons.</p><p><strong>Custom rules: </strong>You’ll need to target either the :before or :after pseudo element in your CSS selector. In that rule, set the font-family to reference the unique font that your kit’s CSS has set up (you can inspect any basic icon to find it or just remove any spaces and capitalize the words of your kit’s title). After that, for each unique icon you want to show, you’ll need to set the “content” property to that specific icon’s unicode glyph (remember, check your documentation for the value).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5BlGtLvfZ4dAJ0QHNixE3w.png" /><figcaption>Referencing an icon with pure CSS examples</figcaption></figure><p>That’s it! With those few tricks, you should be able to bring your Fort Awesome icons to the next level.</p><h4>Troubleshooting Common Problems</h4><p><strong>My icons aren’t showing up or render as weird boxes</strong>: Make sure you have included the correct embed code in your project’s HTML and are using the right icon prefix and name (we’ve fat-fingered those a bunch of times). If you’re having trouble remembering what those are</p><p><strong>Using </strong><a href="http://fontawesome.io/"><strong>Font Awesome</strong></a><strong> alongside </strong><a href="https://fortawesome.com/"><strong>Fort Awesome</strong></a><strong>: </strong>You can use both your kit’s icon font and Font Awesome’s icon font together. Since they both use the same CSS techniques to render icons, you need to make sure that your kit has a different icon prefix than the default “fa”, which is used by Font Awesome. Change your icon prefix to something else (we recommend a 2–4 letter abbreviation for your project or site) and re-publish. Once that’s done, you can use both side by side. Just remember to change any existing Fort Awesome icon references to use your new prefix.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*KIF3mUErp8hV201z4ahvAw.png" /><figcaption>Changing your icon’s prefixes in Fort Awesome</figcaption></figure><p>Also, did you know that <a href="https://fortawesome.com/sets/font-awesome">Font Awesome is included</a> in Fort Awesome’s icon sets? That means you can add any Font Awesome icons you were using directly into your Fort Awesome kit and improve your site’s performance even more!</p><p>Those are the basics of using Fort Awesome icons. If you’re a Fort Awesome user who’s running into trouble, or has a question, check out <a href="https://fortawesome.com/help">our online help</a> or <a href="https://fortawesome.com/help#contact">give us a shout</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f50ab11a2d2a" width="1" height="1" alt=""><hr><p><a href="https://medium.com/fort-awesome/how-to-using-fort-awesome-icons-f50ab11a2d2a">How-To: Use Fort Awesome Icons</a> was originally published in <a href="https://medium.com/fort-awesome">Fort Awesome Articles</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How-To: Serve Fort Awesome Assets Yourself]]></title>
            <link>https://medium.com/fort-awesome/how-to-serve-fort-awesome-assets-yourself-5419b88ee2d4?source=rss----e3c6b1226ade---4</link>
            <guid isPermaLink="false">https://medium.com/p/5419b88ee2d4</guid>
            <category><![CDATA[how-to]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[fort-awesome]]></category>
            <category><![CDATA[icons]]></category>
            <dc:creator><![CDATA[Brian Talbot]]></dc:creator>
            <pubDate>Thu, 21 Jul 2016 20:13:44 GMT</pubDate>
            <atom:updated>2017-01-16T19:56:56.324Z</atom:updated>
            <content:encoded><![CDATA[<p><a href="https://fortawesome.com/">Fort Awesome’s</a> CDN makes it easy to get your site up and running without fussing about where to serve and load your icons and typefaces from. But what if you or your team already have a CDN or asset pipeline/workflow that works for you?</p><p>Fort Awesome can still be the place that your designers and developers go to for asset management, but when you’re ready to use those assets in code, we’ll let you and your workflow take it from here. Here are some steps and pointers on how use your Fort Awesome kit’s your way.</p><h4>1. Publish Your Kit</h4><p>Let’s assume you’ve made a Fort Awesome kit, (if not, <a href="https://fortawesome.com/start">its super easy to get started</a>). Make sure you have the most recent version of your kit ready for download by publishing any recent changes (new icons, removed typefaces, name changes, etc.). In my case, I added an extra cog or two.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ecK4LwQnsmqAkxuMu1QbSw.png" /><figcaption>A Fort Awesome kit in the middle of publishing</figcaption></figure><h4>2. Download Your Published Kit</h4><p>Using the now active “Download” link in your kit’s navigation, you can download an updated copy of your kit’s contents for use offline. Once complete and unzipped, you’ll have a unique folder (named with your kit’s name + id) on your local hard drive.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xkYypaJH2sER5nX1K-byeQ.png" /><figcaption>Example: Downloaded and unzipped kit’s contents</figcaption></figure><p>Let’s take a look at the files and assets you can integrate into your project and workflow:</p><h4>Kit Demo (demo.html)</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*VuoQjTgRYFt6-vRjxljhSQ.png" /><figcaption>downloaded kit’s demo.html file</figcaption></figure><p>Open the <strong>demo.html</strong> file to see a quick cheatsheet of all of your assets. Not only is this an inventory, but its source code is also an example of how to use and reference the downloaded files in a page or site (so be sure to view the source if you want to see the inner-workings or are stuck).</p><h4>Easy Integration: Included CSS</h4><p>Your downloaded kit contains the supporting CSS you need to get your icons and typefaces up and running quickly in modern browsers. Here are the options you have when using this easy out of the box method:</p><ol><li><strong>CSS with icon fonts + typefaces embedded</strong> (<em>/css/embedded.css</em>): CSS that includes the <a href="https://developer.mozilla.org/en-US/docs/Web/Guide/WOFF">WOFF</a> version of your icons and typefaces embedded using data URIs and base64 encoding. By using this file the browser will not have to make additional requests to your server to get the individual font files. You also won’t need to manage any other icon or typeface files (<em>The only downside is that you can’t use alternative font formats like EOT, needed for older IE support.)</em></li><li><strong>CSS with references to icons + typefaces</strong> (<em>/css/external.css): </em>CSS that includes references to external web fonts files that are also part of your kit download (<em>/typefaces </em>and <em>/icons</em>). Minified versions of this CSS (<em>/css/external-min.css</em>) are included for better performance as well.</li></ol><p>No matter which option you choose, you’ll want to either reference this CSS file independently alongside your project’s existing CSS in your HTML or add the contents of this CSS file manually into your project’s existing CSS.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*li4A_nLx8o-zWr2M6qebXg.png" /><figcaption>Example HTML file with both your specific project and your kit’s referenced —<strong> Using the embedded option</strong></figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*QDshMGx2thcyTXEgZxhSDQ.png" /><figcaption>Example HTML file with both your specific project and your kit’s referenced — <strong>Using the external option</strong></figcaption></figure><p><strong>Extra — Changing folder/directory structures: </strong>You can customize where your kit’s downloaded files are within your project. If you are using the /<em>css/external.css</em> or /<em>css/external-min.css</em>, make sure you update the paths to where you’ve moved the files.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mkBHUMtpuFzVDu_pnfFdpQ.png" /><figcaption>A relatively silly example of customizing your project’s folder with you kit assets. <strong>Note the paths in the external.css file are updated to where we moved things</strong>.</figcaption></figure><p><strong>Extra — Supporting IE 8 and below: </strong>If you need to support Internet Explorer 8 or below, we feel for you :P. And we’ve also got your back. If you’re already using the<em> /css/external.css</em> or /css/<em>external-min.css</em>, you’re covered. If you’re using those, just add an additional CSS reference to the <em>/css/ie-only.css</em> file</p><p>With all of the support styling and assets referenced, check out your kit’s downloaded or online documentation to see how to use your icons and typefaces in your UI through CSS and HTML.</p><h4>Advanced Integration: SVG, and CSS Preprocessors</h4><p>If you’re more familiar with Front End Development, you may have specific preferences and practices to your process. Fort Awesome kit downloads come with a few things to help with that:</p><ul><li><strong>SVG support</strong>: You can find <a href="https://developer.mozilla.org/en-US/docs/Web/SVG">SVG</a> versions of all of your kit’s icons in the downloaded <em>/icons/svg</em><strong><em>/</em> </strong>folder<strong> </strong>if you prefer to manage your icons as images or <a href="https://css-tricks.com/svg-sprites-use-better-icon-fonts/">if you use SVG sprites in your app</a>.</li><li><strong>SCSS/Less: </strong>For CSS Preprocessor users, you can find individual icon-based variables (for use if you’d prefer to render your icons through CSS only) and mixins for our common icon support styling. These are in the <em>/css/scss/</em> and <em>/css/less/ </em>folders. <strong>Move and include these in your compilation file before you call any variables/mixins</strong>.</li></ul><p>Those are the broad strokes to serving Fort Awesome kits yourself. If you’re a Fort Awesome user who’s running into trouble, or has a question, check out <a href="https://fortawesome.com/help">our online help</a> or <a href="https://fortawesome.com/help#contact">give us a shout</a>.</p><p><strong>Note: </strong>You’ll need a <a href="https://fortawesome.com/start">Pro-level Fort Awesome Plan</a> or above to download your kit.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5419b88ee2d4" width="1" height="1" alt=""><hr><p><a href="https://medium.com/fort-awesome/how-to-serve-fort-awesome-assets-yourself-5419b88ee2d4">How-To: Serve Fort Awesome Assets Yourself</a> was originally published in <a href="https://medium.com/fort-awesome">Fort Awesome Articles</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How-To: Use Fort Awesome Icons in Desktop Apps]]></title>
            <link>https://medium.com/fort-awesome/how-to-fort-awesome-assets-on-the-desktop-e3fd15df6f43?source=rss----e3c6b1226ade---4</link>
            <guid isPermaLink="false">https://medium.com/p/e3fd15df6f43</guid>
            <category><![CDATA[fort-awesome]]></category>
            <category><![CDATA[icons]]></category>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[how-to]]></category>
            <dc:creator><![CDATA[Brian Talbot]]></dc:creator>
            <pubDate>Thu, 21 Jul 2016 20:11:38 GMT</pubDate>
            <atom:updated>2017-01-16T20:02:53.687Z</atom:updated>
            <content:encoded><![CDATA[<p><a href="https://fortawesome.com/">Fort Awesome</a> and its CDN make it easy to curate, manage, and build with your icons and typefaces. But what if you or your team need to use your collected assets in your favorite design apps, within desktop apps or presentations or elsewhere?</p><p>Fort Awesome can help you with that as well. Let’s see how…</p><h4>1. Publish Your Kit</h4><p>Let’s assume you’ve made a Fort Awesome kit, (if not, <a href="https://fortawesome.com/start">its super easy to get started</a>). Make sure you have the most recent version of your kit ready for download by publishing any recent changes (new icons, removed typefaces, name changes, etc.). In my case, I added an extra cog or two.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ecK4LwQnsmqAkxuMu1QbSw.png" /><figcaption>A Fort Awesome kit in the middle of publishing</figcaption></figure><h4>2. Download Your Published Kit</h4><p>Using the now active “Download” link in your kit’s navigation, you can download an updated copy of your kit’s contents for use offline. Once complete and unzipped, you’ll have a unique folder on your local hard drive.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xkYypaJH2sER5nX1K-byeQ.png" /><figcaption>Example: Downloaded and unzipped kit’s contents</figcaption></figure><p>This folder contains a lot of assets that are meant for web-use if you’d rather serve your kit’s assets yourself instead of Fort Awesome’s CDN. Let’s take a look at the ones that are specifically for Desktop use and how to use them:</p><h4>Icon Source Files</h4><p>You can find <a href="https://developer.mozilla.org/en-US/docs/Web/SVG">SVG</a> versions of all of your kit’s icons in the <em>/icons/svg/</em><strong> </strong>folder. Adobe Creative Suite, <a href="https://www.sketchapp.com/">Sketch</a>, and open source alternatives can open and work with these types of files. These are also great for native application use, <a href="https://css-tricks.com/svg-sprites-use-better-icon-fonts/">if you use SVG sprites in your app</a>, or as source files for your design team.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7ia_cjNsonQASWglewth8Q.png" /><figcaption>A downloaded .svg icon file in Sketch App</figcaption></figure><p><strong>Pro-tip: </strong>You can edit these files to create new and custom icons. Just remember to name/save the new icon as something different and to upload them back into your Fort Awesome kit for future use.</p><h4>Icon Font Files</h4><p>If you’d rather manage your icons like a set of glyphs or typeface as we do, you can use the included icon font files in your favorite system font manager and Desktop design apps.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Z2BQFjPFCSQ2Q3KS9XDIWw.png" /></figure><p>Find the /icons/<em>icons.otf</em> or /icons/<em>icons.ttf</em> font files in your downloaded folder and import one into your favorite or default operating system’s font manager. Make sure to activate any fonts once you’ve imported them.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*VuoQjTgRYFt6-vRjxljhSQ.png" /><figcaption>downloaded kit’s demo.html file</figcaption></figure><p>You can now use the <strong>demo.html</strong> file included in your downloaded kit as you would the <a href="http://fontawesome.io/cheatsheet/">Font Awesome Cheatsheet</a>. Copy and paste any icon (highlighting the large symbol) from your icon list into a line of text in your document (.psd, .ai, .sketch, .doc, .ppt, etc.).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0WcAAk3WQCh47o5wMLON-w.png" /><figcaption>Pasted icons using an imported icon font in Sketch</figcaption></figure><p>Alternatively, if you’re using Adobe Photoshop or Illustrator, you can see all of your icon font’s symbols at once by viewing the glyphs panel. Create a text layer and select an icon from the panel to insert it into the layer.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/527/1*pv831-JrN_NwHtikGbjqQA.png" /><figcaption>Icons inserted into an illustrator document using the Glyphs panel.</figcaption></figure><h4>Updating over time</h4><p>If you make changes to your Fort Awesome kit and want to update your local versions of things, just make sure to:</p><ol><li>Follow the first steps of publishing and downloading to get a fresh copy of your kit’s contents.</li><li>Re-import and replace any previously imported icon fonts with the same name.</li></ol><p>That’s pretty much it. If you’re a Fort Awesome user who’s running into trouble, or has a question, check out <a href="https://fortawesome.com/help">our online help</a> or <a href="https://fortawesome.com/help#contact">give us a shout</a>.</p><p><strong>Note: </strong>You’ll need a <a href="https://fortawesome.com/start">Pro-level Fort Awesome Plan</a> or above to download your kit.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e3fd15df6f43" width="1" height="1" alt=""><hr><p><a href="https://medium.com/fort-awesome/how-to-fort-awesome-assets-on-the-desktop-e3fd15df6f43">How-To: Use Fort Awesome Icons in Desktop Apps</a> was originally published in <a href="https://medium.com/fort-awesome">Fort Awesome Articles</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Duotone Icons Using Fort Awesome]]></title>
            <link>https://medium.com/fort-awesome/duotone-icons-using-fort-awesome-8bd4c0c23904?source=rss----e3c6b1226ade---4</link>
            <guid isPermaLink="false">https://medium.com/p/8bd4c0c23904</guid>
            <category><![CDATA[fort-awesome]]></category>
            <category><![CDATA[icons]]></category>
            <category><![CDATA[design]]></category>
            <dc:creator><![CDATA[Dave Gandy]]></dc:creator>
            <pubDate>Wed, 04 May 2016 20:43:19 GMT</pubDate>
            <atom:updated>2016-05-04T20:43:08.237Z</atom:updated>
            <content:encoded><![CDATA[<blockquote>Were there monkeys? Some terrifying space monkeys maybe got loose?</blockquote><p>Lets do something simple that looks all fancy. Let’s take a regular icon, split it into 2 layers, and make them 2 different colors. And let’s have them inherit the color of their container, just like regular icon fonts. Et voilà.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/738/1*zaKE0BlcY8Yzv32L5Y8n7Q.png" /></figure><p>Some background reading to get you prepped:</p><ol><li><a href="https://articles.fortawesome.com/advanced-icon-design-whitespace-bdd63e6cde3b">Advanced Icon Design: Whitespace</a></li><li><a href="http://fontawesome.io/examples/#stacked">Font Awesome Examples: Stacking Icons</a></li></ol><h4>Layers and Assembly</h4><p>Just like a regular Font Awesome icon, we’ll be using the :before pseudo-element (we’ll use this for our bottom layer). But we’ll also use :after to set a top layer. For each icon, we’ll upload 2 icons — one for each layer. Throw in a dash of opacity and absolute positioning, and we’ve got it.</p><h4>HTML</h4><pre>&lt;i class=&quot;fa fa-duo fa-chat&quot;&gt;&lt;/i&gt;<br>&lt;i class=&quot;fa fa-duo fa-settings&quot;&gt;&lt;/i&gt;<br>&lt;i class=&quot;fa fa-duo fa-heart&quot;&gt;&lt;/i&gt;</pre><h4>The CSS</h4><pre>.fa-duo:before {<br> opacity: .2;<br> position: absolute;<br>}<br>.fa-chat {<br> &amp;:before { content: &#39;\f001&#39;; }<br> &amp;:after { content: &#39;\f000&#39;; }<br>}<br>.fa-settings {<br> &amp;:before { content: &#39;\f003&#39;; }<br> &amp;:after { content: &#39;\f002&#39;; }<br>}<br>.fa-heart {<br> &amp;:before { content: &#39;\f005&#39;; }<br> &amp;:after { content: &#39;\f004&#39;; }<br>}</pre><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fcodepen.io%2Fdavegandy%2Fembed%2Fpreview%2FQNJoEr%3Fheight%3D600%26amp%3Bslug-hash%3DQNJoEr%26amp%3Bdefault-tabs%3Dhtml%2Cresult%26amp%3Bhost%3Dhttp%253A%252F%252Fcodepen.io%26amp%3Bembed-version%3D2&amp;url=https%3A%2F%2Fcodepen.io%2Fdavegandy%2Fpen%2FQNJoEr&amp;image=https%3A%2F%2Fs3-us-west-2.amazonaws.com%2Fi.cdpn.io%2F20714.QNJoEr.small.af458005-ed36-47c8-9c9f-e5d8c28723a7.png&amp;key=d04bfffea46d4aeda930ec88cc64b87c&amp;type=text%2Fhtml&amp;schema=codepen" width="800" height="600" frameborder="0" scrolling="no"><a href="https://medium.com/media/2cf1408559110ae02eb44a48b3397b54/href">https://medium.com/media/2cf1408559110ae02eb44a48b3397b54/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8bd4c0c23904" width="1" height="1" alt=""><hr><p><a href="https://medium.com/fort-awesome/duotone-icons-using-fort-awesome-8bd4c0c23904">Duotone Icons Using Fort Awesome</a> was originally published in <a href="https://medium.com/fort-awesome">Fort Awesome Articles</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[New Fort Awesome Kit UI]]></title>
            <link>https://medium.com/fort-awesome/new-fort-awesome-kit-ui-c2a175da53b4?source=rss----e3c6b1226ade---4</link>
            <guid isPermaLink="false">https://medium.com/p/c2a175da53b4</guid>
            <category><![CDATA[design]]></category>
            <category><![CDATA[typography]]></category>
            <dc:creator><![CDATA[Brian Talbot]]></dc:creator>
            <pubDate>Mon, 21 Mar 2016 17:48:56 GMT</pubDate>
            <atom:updated>2016-03-21T17:47:59.080Z</atom:updated>
            <content:encoded><![CDATA[<blockquote>Little surprises around every corner, but nothing dangerous. So don’t be alarmed. As soon as your outer vestments are at hand, we’ll begin.</blockquote><p>We’re building Fort Awesome so that you can better curate, optimize, and use your design and front end assets. To do that, we spent time complementing Font Awesome with some of <a href="https://fortawesome.com/sets">the best icon sets</a> out there. We set up <strong>kits</strong> to help you better manage your assets per project or site. And we expanded what a Fort Awesome kit can do by <a href="https://articles.fortawesome.com/peas-in-a-pod-56cf44adafe">adding typefaces</a> and the ability to <a href="https://articles.fortawesome.com/missing-an-icon-want-to-add-you-logo-25cc91431f4">upload your own icons and fonts</a>.</p><p>After working through all that, it felt right to take a step back and look at kits and Fort Awesome as a whole. <strong>We took some time to strengthen the Fort for you. </strong>Here’s what you can expect when you hit your kit.</p><h3>Fort Usability and Navigation</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ndUKILLVOSxyGgWE0dmH7A.png" /></figure><p>As we add more ways to help with your UI and front end, we didn’t want to lose the bigger picture of managing those assets day-to-day. Its now easier to see your kit’s contents at a glance. Also, getting around to its assets and settings should be easier than ever. Oh, and pssst… we made some room for some future kit goodies and features.</p><h3>Top Class Typefaces</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*FhWnhf9W94UiNseO1hvBOw.png" /></figure><p>We wanted to give your project’s fonts the attention they deserve. <strong>Typefaces are now a first class asset in your kit</strong>. They have their own dedicated area for adding, tweaking, and managing. Also, we’ve made finding or uploading just the right typeface for your project as easy as has been for icons.</p><h3>Speedier UI</h3><p><a href="https://medium.com/@robmadole">Rob</a> and <a href="https://medium.com/@supercodepoet">Travis</a> have been leading us through some great <strong>under-the-hood improvements</strong> as well. With <a href="https://facebook.github.io/react/">React</a> at the heart of our UI, you can expect prompt page loads, snappy search results, and more time in your UI, rather than in ours.</p><p>The latest changes are live and available to all kit caretakers. <a href="https://fortawesome.com/"><strong>Have a look, kick the tires, and let us know</strong></a><strong> what you think at Fort Awesome!</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c2a175da53b4" width="1" height="1" alt=""><hr><p><a href="https://medium.com/fort-awesome/new-fort-awesome-kit-ui-c2a175da53b4">New Fort Awesome Kit UI</a> was originally published in <a href="https://medium.com/fort-awesome">Fort Awesome Articles</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Want Font Awesome to be More Awesome?]]></title>
            <link>https://medium.com/fort-awesome/want-font-awesome-to-be-more-awesome-19092ab4e31?source=rss----e3c6b1226ade---4</link>
            <guid isPermaLink="false">https://medium.com/p/19092ab4e31</guid>
            <category><![CDATA[surveys]]></category>
            <category><![CDATA[font-awesome]]></category>
            <category><![CDATA[feedback]]></category>
            <dc:creator><![CDATA[Brian Talbot]]></dc:creator>
            <pubDate>Thu, 25 Feb 2016 16:44:09 GMT</pubDate>
            <atom:updated>2016-02-25T16:42:59.238Z</atom:updated>
            <content:encoded><![CDATA[<blockquote>Yeah, well, you know, that’s just, like, your opinion, man.</blockquote><p><a href="http://fontawesome.io/">Font Awesome</a>, the massive icon collection, will be celebrating its fourth anniversary this March. We’ve added over <strong>600</strong> icons. We’ve helped folks spin, stack, and flip them. And we’ve made it easy for people to use them where they wanted to — be it in Bootstrap, in your favorite graphics editor, or in your own static code.</p><p>Like any birthday or anniversary, this is a moment of reflection for us. Our gang at Fort Awesome is proud and honored to care for a project that so many folks love, value, and contribute to. But that’s not any reason to rest.</p><p>As designers and developers, we know how, where, and what we build changes often. With that in mind, we want to ensure that Font Awesome continues to be, well, awesome to use.</p><p>There’s no one more qualified to help us with that job than people who design and build daily with Font Awesome. <strong>That’s where we need you.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Uy-iyZUuUx_l1vW8nktubA.png" /></figure><p><a href="http://fontawesome.io/survey/"><strong>Fill out our 10-minute survey to give us your feedback about working with Font Awesome</strong></a><strong>!</strong></p><h3>Yearning to learn</h3><p>Aside from everyone’s favorite Font Awesome icon, we’re hoping to learn more about a bunch of stuff such as:</p><ul><li>Who uses Font Awesome? Where are they from? What do they do?</li><li>Where do people use our icons — both in their products as well as their process in making them?</li><li>What’s great, super easy, and puts the awesome in Font Awesome?</li><li>What’s mucho tough to do, missing, or not awesome now?</li></ul><h3>How you can help</h3><p>As we mentioned before, <a href="http://fontawesome.io/survey/"><strong>give us your thoughts via our survey</strong></a>. It shouldn’t take a ton of time. Keep an eye out for some fun questions and Font Awesome trivia in there too.<strong> :)</strong></p><p>And hey! If you’re up for answering follow up questions, testing new features, or hearing about new projects, let us know at the end of the survey.</p><h3>What comes next</h3><p><a href="http://fontawesome.io/survey/">We’ll be listening</a>. The good feedback and information you folks provide will help us build features, solve new and old problems, and set some of the next steps for Font Awesome and <a href="https://fortawesome.com/">other goodies</a>. We’ll also be sharing what we learn with the community, so expect a full “State of the Icons” in the near future.</p><p>Thanks for continuing to make the interwebs more awesome with your work and for using Font Awesome to help you get there.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=19092ab4e31" width="1" height="1" alt=""><hr><p><a href="https://medium.com/fort-awesome/want-font-awesome-to-be-more-awesome-19092ab4e31">Want Font Awesome to be More Awesome?</a> was originally published in <a href="https://medium.com/fort-awesome">Fort Awesome Articles</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Want To Develop Software?]]></title>
            <link>https://medium.com/fort-awesome/want-to-develop-software-b3c24b43b559?source=rss----e3c6b1226ade---4</link>
            <guid isPermaLink="false">https://medium.com/p/b3c24b43b559</guid>
            <category><![CDATA[business]]></category>
            <category><![CDATA[education]]></category>
            <category><![CDATA[entrepreneurship]]></category>
            <dc:creator><![CDATA[Christian Helms]]></dc:creator>
            <pubDate>Wed, 03 Feb 2016 01:06:54 GMT</pubDate>
            <atom:updated>2016-02-02T23:43:10.593Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*cbU0MCE8QTqRPfiI5BcxdA.jpeg" /></figure><p>Being new to anything means there is a lot of work ahead. And when it’s a what you want to do as a career, failure is not an option. There are many ways to become better at something, although all methods take time. The way to make the quickest progress toward becoming better at anything is to have the drive to become better. Becoming better at something that’s worth spending time on should be fun yet challenging.</p><p>As a Software Developer you’ll need to learn every day. Many of the developers I know think things were easier when they were younger. Now things are much more complex. In today’s world the majority of languages are built upon other languages which can be built upon yet another language making it difficult to understand the language which can hinder productivity. Many people become stressed by all the learning required in keeping up. Being overwhelmed by what there is to be accomplished must be resolved quickly to prevent burn out. The solution is simple, by learning what’s expected to be learned in the order that it all builds upon the last thing learned can reduce stress greatly. Somethings won’t fit into this build of learning; you must determine where these outliers best fit. Learning like this will make everything flow smoother.</p><p>There are many languages in use today. Once a person learns their first computer language the majority of others come more fluently. It would be beneficial as a new developer to begin by simply picking a language and learning it. Learning Ruby or Python as a first language is good because their syntax is focused more toward how people think rather than how the computer thinks. It’s possible to learn a new language for little or no money. There are many ways of learning a new language such as books, articles, and some podcasts. Another option would be to watch YouTube videos from YouTubers; such as: <a href="https://www.youtube.com/user/thenewboston">TheNewBoston</a> who puts out videos daily to teach about languages amongst other things, <a href="https://www.youtube.com/channel/UCfWZwsP8trUy5uHJg8gcGIQ">Mackenzie Child</a> who puts out videos aimed at web design with Ruby on Rails, and <a href="https://www.youtube.com/user/elithecomputerguy">Eli The Computer Guy</a> whose videos teach more about career advise, networking, and servers. I’ve learned a lot from these three YouTubers over the years, they all do an amazing job at teaching people who are interested in software development.</p><p>In software development a point must be made to keep up to date with the the tools and languages in use. For example, when the new version of Ruby comes out (the most current version is 2.3.0) you should update and read about changes. Especially when the community is urging the people within it to be up to date. If a developer decides to use tools of the past instead of the new tools he or she is no longer nearly as useful.</p><p>It’s not a bad idea to touch up on languages learned in the past to prepare for software updates. It will keep a previously learned language fresh in mind; this can increase productivity. For example, I learned Ruby a year prior to learning the Rails framework. When learning Rails I had to relearn a few aspects of Ruby. Doing this helped me understand rails much better and learning it went quickly.</p><p>Getting started in software development isn’t as hard as people think it is. It just takes time, dedication, and patience. Once you start development the rest seems to flow naturally. Being persistent when running into a problem is crucial for success in the beginning and for the duration of one’s career as a developer. Developing Software is something that can be used in almost all career paths. Tools can be built to make tasks easier and quicker. Even if you don’t get paid to develop software it can be an extremely useful tool in life that also looks good on resumes.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b3c24b43b559" width="1" height="1" alt=""><hr><p><a href="https://medium.com/fort-awesome/want-to-develop-software-b3c24b43b559">Want To Develop Software?</a> was originally published in <a href="https://medium.com/fort-awesome">Fort Awesome Articles</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>