<?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 Leandra Silver on Medium]]></title>
        <description><![CDATA[Stories by Leandra Silver on Medium]]></description>
        <link>https://medium.com/@leandrasilver?source=rss-ef5699820dbd------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*jbpawwLm-6tCj0Ihsjkwgw.jpeg</url>
            <title>Stories by Leandra Silver on Medium</title>
            <link>https://medium.com/@leandrasilver?source=rss-ef5699820dbd------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 22:43:55 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@leandrasilver/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[Top 10 Low Effort Improvements for Accessible Web Content]]></title>
            <link>https://medium.com/@leandrasilver/top-10-low-effort-improvements-for-accessible-web-content-13f1e2013113?source=rss-ef5699820dbd------2</link>
            <guid isPermaLink="false">https://medium.com/p/13f1e2013113</guid>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[front-end-development]]></category>
            <category><![CDATA[accessibility]]></category>
            <category><![CDATA[website-development]]></category>
            <category><![CDATA[a11y]]></category>
            <dc:creator><![CDATA[Leandra Silver]]></dc:creator>
            <pubDate>Fri, 14 Dec 2018 15:36:54 GMT</pubDate>
            <atom:updated>2018-12-14T15:41:56.732Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8p1UURaeiClt8PlBp_2w6w.png" /><figcaption>Self closing HTML tag with the a11y logo inside instead of a regular tag.</figcaption></figure><p><a href="#52b0">Skip the introduction and navigate straight to the top ten list here.</a></p><p>The creation of accessible sites is a collaborated dance between designers, user experience specialists, web developers, content editors, and web accessibility auditors. At the end of this dance, the final result is a collection of accessible templates and pages that is ready to be filled out with images and information by content developers.</p><p>Since one of the main purposes of a website is to deliver content, the information must be perceivable, operable, and understandable to as many users as possible. These are actually three of the four concepts fundamental to web accessibility, in which <a href="https://www.w3.org/TR/UNDERSTANDING-WCAG20/intro.html">WCAG 2.0</a> develops it’s technical standards and guidelines from. It’s actually referred to as ‘POUR’, see below:</p><p><strong>Perceivable</strong> — Everyone needs to be able to digest the content of the site. This is done by having content available to at least one of the user’s senses. For example, if you are blind, the screen reader will need to work well with the content available. Or if you are deaf and there is audio present, then there should be an alternative text representation of the same content.</p><p><strong>Operable </strong>— Everyone needs to be able to operate the interface. Only a portion of people use a mouse, some people use screenreaders or keyboards to navigate sites.</p><p><strong>Understandable</strong> — Everyone needs to be able to understand the content, even if you are successfully receiving it. For example, people have a range of cognitive abilities. Using clear language and making sure interfaces are consistent and predictable can really be helpful to many users.</p><p><strong>Robust</strong> — The site must be built in such a way that it works across many combinations of different assistive technologies, older browsers, and devices. This principle is mostly only a concern for the web developers.</p><p>It’s easy to get carried away and excited when handed a brand new website by filling it with legacy content — without any further considerations — so months worth of hard work can be shared as soon as possible.</p><p>However, it is extremely important that a website’s accessibility integrity is maintained once it enters the content entry stage. The maintenance of a site’s long-term accessibility is reliant on it’s new content also being accessible. For instance, an accessible template is useless without accessible content and vice-versa.</p><p>Sam Chandrashekar (<a href="https://twitter.com/sambhavi"><strong>@</strong>sambhavi</a>), an accessibility program manager and professor at the <a href="https://www.ocadu.ca/academics/graduate-studies/inclusive-design.html">OCAD’s Master of Inclusive Design Program</a>, put it into good words at the #a11yTO Conference this past October of 2018,</p><blockquote>“It is the responsibility of every organization to sustain the accessibility that it’s designers, developers, and others work hard to attain.”</blockquote><blockquote>— Sam Chandrashekar</blockquote><p>When developing or migrating content into a website, accessibility should be thought about from the start and continued well into the future. Refurnishing a site’s content later on to become more accessible will burn much more hours than the initial commitment of considering accessibility from the start of the content development process.</p><p>Everyone should be familiar with the analogy of a website being compared to as a building. The HTML is compared to the walls, the CSS is compared to the painting and decorations, and the Javascript is compared to the plumbing, heating, and electrical. Another striking similarity is that both websites and buildings need to follow guidelines to be accessible.</p><p>Imagine a building having to be renovated to become compliant, versus being designed and built with accessibility in mind. It would likely be less effort to be proactive rather than reactive, and incorporate building accessibility in the design.</p><p><a href="https://www.youtube.com/watch?v=O9gCG33icCA&amp;t=5s">Here is a must see video</a>, narrated by AODA Alliance chair David Lepofsky (<a href="https://twitter.com/DavidLepofsky"><strong>@</strong>DavidLepofsky</a>) auditing Ryseron’s Student Learning Centre for accessibility barriers. He mentions the issue of leaning structural pillars that protrude the path of travel, that could easily cause injury to an individual walking by. This could have been easily addressed in the architectural design phase, but sadly overlooked, and now impossible to resolve as the building may rely on the structural integrity of the pillars.</p><p>In terms of web accessibility, for instance, no one wants to fix hundreds of links or images on hundreds of pages. So if content creators create content with the four principles in mind (POUR), it can increase the durability, usability, and overall accessibility of their website.</p><p>Here’s a top ten list for anyone creating or editing content with accessibility in mind. For further reference, links to the relevant WCAG 2.0 success criterions are noted when applicable. These items are relatively low effort and when considered consistently throughout the site, it can really improve any website’s usability. Ultimately delivering content to the widest range of users, which is the primary goal of your site.</p><h3>The Top 10 Low Effort Improvements for Accessible Web Content</h3><h4>1. Use descriptive link text</h4><p>Stay away from the “Click Here” or “Learn More” links. Link texts should be written so they make sense out of context and accurately describe it’s purpose. Screen readers have options to list all the links on the web page, and these are provided out of context.</p><p>Below is an example, from voiceover, of a webpage with descriptive link text. A list of twelve “Learn More” links, would be useless to a screen reader user as it’s provides no information about the destination and purpose of the links.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/722/1*DZ0dE66pnWpkJvMhugXE3A.png" /><figcaption>A screenshot of the web voiceover rotor, listing out links on a webpage.</figcaption></figure><p>If you would like to test this out for yourself with voiceover, here is a guide for more information about <a href="https://www.apple.com/voiceover/info/guide/_1134.html">navigating with voiceover</a> using the rotor.</p><p><a href="https://www.w3.org/TR/UNDERSTANDING-WCAG20/navigation-mechanisms-refs.html">See success criterion: 2.4.4 Link Purpose (In Context) (Level A)</a></p><h4>2. Use unique link text for links with different destinations</h4><p>Users might not know the difference between links with the same link text. Make sure links that go to different destinations have differentiating link text.</p><p><a href="https://www.w3.org/TR/UNDERSTANDING-WCAG20/navigation-mechanisms-refs.html">See success criterion: 2.4.4 Link Purpose (In Context) (Level A)</a></p><h4>3. Fix broken links and broken anchor links</h4><p>Ensure links are not broken and anchor links have destinations on the page that actually exist. Broken links will confuse users and negatively influence other area’s of your site, like SEO. And when using local links they must refer to an existing element on the page.</p><p><a href="https://www.w3.org/TR/UNDERSTANDING-WCAG20/content-structure-separation-programmatic.html">See success criterion: 1.3.1 Info and Relationships (Level A)</a></p><h4>4. Use alt tags correctly</h4><p>If you are reading this article now, this is probably not the first time hearing about adding alt tags to your non-text content. Ensure alt tags are used, but also make sure to use them <strong>correctly</strong>. Every user should receive the same information that the non-text content is portraying.</p><p>Ask yourself, what is the net new information your image is providing to the end user? For example, pure decorative images should have an empty alt tag, since they provide no information. Make sure the alt tag is empty, otherwise the assistive technology will read out the whole file name. Also, alt text is useful as it is displayed for users that have slower connections and do not want to download images, especially on mobile.</p><p>Please refer to <a href="https://webaim.org/techniques/alttext/">https://webaim.org/techniques/alttext/</a> for alt text basics for images.</p><p><a href="https://www.w3.org/TR/UNDERSTANDING-WCAG20/text-equiv-all.html">See success criterion: 1.1.1 Non-text Context</a></p><h4>5. Do not use images with text</h4><p>Images that contain text within them are simply not accessible. Not all users benefit from alternative text used on images with text. For example, low vision users may have magnification applications that enlarge elements on the page, an enlarged image could possibly become pixelated and unreadable.</p><p>To keep it easy, try to steer clear from using images with text. But if there is no way around it, the alt text should include the text in the image.</p><p>See success criterions: <a href="https://www.w3.org/TR/UNDERSTANDING-WCAG20/visual-audio-contrast-text-presentation.html">1.4.5 Images of text (Level AA)</a> and <a href="https://www.w3.org/TR/UNDERSTANDING-WCAG20/visual-audio-contrast-text-images.html">4.9 Images of Text (No Exception) — Level AAA</a></p><h4>6. Heading structure should be correctly nested</h4><p>Similar to links, assistive technologies can use headings to provide in-page navigation.</p><p>If you remove your styles for your website, and view the pure html of your site, the structure of your headings should be a logical outline. Authors should use headings that are properly nested (e.g., h1 followed by h2, h2 followed by h2 or h3, h3 followed by h3 or h4, etc.). Make sure headings levels are not skipped.</p><p><a href="https://www.w3.org/TR/UNDERSTANDING-WCAG20/content-structure-separation-programmatic.html">See success criterion: 1.3.1 Info and Relationships (Level A)</a></p><h4>7. Use correct HTML5 markup</h4><p>When HTML5 is correctly written to spec it allows the content to have programatically determined relationships. For example, if you have a list, use an ‘ul’ or ‘ol’ tags. Do not use regular paragraphs, as that list relationship would be lost to some users. Another example of programatically determined relationships are tables and the cells within them. <a href="https://webaim.org/techniques/tables/data">Please refer to this guide for how to write better markup for tables.</a></p><p>Also, the use of ‘bold’ and ‘i’ tags are deprecated, and should be substituted for the use of ‘strong’ or ‘em’ tag respectively. This ensures a separation between presentation and semantics. Beware of misusing ‘strong’ and ‘h’ tags. If the text is a heading, then be sure to use an ‘h’ tag instead.</p><p><a href="https://www.w3.org/TR/UNDERSTANDING-WCAG20/content-structure-separation-programmatic.html">See success criterion: 1.3.1 Info and Relationships (Level A)</a></p><h4>8. Increase the readability of your page</h4><p>Users with disabilities that make it difficult to decode words and sentences are likely to have trouble reading and understanding complex text. If the page consists of complex information, consider adding a summary paragraph that states the page’s content in a simpler and concise way. Read more about making content more readable through the success technique, <a href="http://www.w3.org/WAI/GL/2016/WD-WCAG20-TECHS-20160105/G153">G153: Making the text easier to read</a>.</p><p>Here is a resource to test the reading level of a web page, called the <a href="https://www.online-utility.org/english/readability_test_and_improve.jsp">Readability Calculator</a>.</p><p><a href="https://www.w3.org/TR/UNDERSTANDING-WCAG20/meaning-supplements.html">See success criterion: 3.1.5 Reading Level (Level AAA)</a></p><h4>9. Use descriptive page titles</h4><p>Page titles are announced by assistive technologies when navigating web pages. This means in order for users to better understand where they are, without reading through a whole page, page titles should be informative. Descriptive page titles will also help with improved SEO.</p><p><a href="https://www.w3.org/TR/UNDERSTANDING-WCAG20/navigation-mechanisms-title.html">See success criterion: 2.4.2 Page Titled (Level A)</a></p><h4>10. Use non-automated captions on media</h4><p>Not everyone can hear audio in every scenario, and users may be missing out on content. You might be viewing a youtube video on a bus without earphones, or a non-native to the language of the media, or neurodivergent, or even hearing impaired. Either way, anyone can benefit from descriptive captions.</p><p>In general, automated captions are not reliable. Automated captions from youtube are choppy and unreliable. These horrible captions are sometimes referred to as “craptions”. Try to add your own captions by following caption standards or use another service, like <a href="https://www.rev.com/?utm_source=zapier.com&amp;utm_medium=referral&amp;utm_campaign=zapier&amp;utm_source=zapier.com&amp;utm_medium=referral&amp;utm_campaign=zapier">Rev</a>.</p><p><a href="https://www.w3.org/WAI/WCAG21/quickref/?versions=2.0&amp;showtechniques=122#time-based-media">See success criterion: 1.2 — Time-based Media (Level A)</a></p><h3>Other useful resources</h3><p>Decision tree for alt text on images: <a href="https://www.w3.org/WAI/tutorials/images/decision-tree/">https://www.w3.org/WAI/tutorials/images/decision-tree/</a></p><p>More examples of accessible table markup: <a href="https://www.w3.org/WAI/tutorials/tables/">https://www.w3.org/WAI/tutorials/tables/</a></p><p>Web Content Accessibility Guidelines (WCAG) 2.0: <a href="https://www.w3.org/TR/WCAG20/">https://www.w3.org/TR/WCAG20/</a></p><p>Information on how to correctly structure headings: <a href="https://www.w3.org/WAI/tutorials/page-structure/headings/">https://www.w3.org/WAI/tutorials/page-structure/headings/</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=13f1e2013113" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Creating Your Own Customizable Skill Bars in Wordpress]]></title>
            <link>https://medium.com/@leandrasilver/creating-your-own-customizable-skill-bars-in-wordpress-efbdf134ff3?source=rss-ef5699820dbd------2</link>
            <guid isPermaLink="false">https://medium.com/p/efbdf134ff3</guid>
            <category><![CDATA[wordpress]]></category>
            <category><![CDATA[web-development]]></category>
            <dc:creator><![CDATA[Leandra Silver]]></dc:creator>
            <pubDate>Sun, 13 Nov 2016 05:09:10 GMT</pubDate>
            <atom:updated>2016-11-13T17:41:02.018Z</atom:updated>
            <content:encoded><![CDATA[<p>My last PSD to responsive project created with Wordpress had a skill bars section. At first glance I thought that this part could never be dynamic for a client. Then at second glance I broke it into smaller steps and took on the challenge to make it dynamic. The goal was to enable the client to enter any skill and how confident they are at this skill, then change the skill bars accordingly. Read below for the steps to make some yourself!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*QWIOuf9S2e4kkptdSf4DVw.png" /></figure><h3><strong>Step 1 — Create your custom fields for the skill bar section.</strong></h3><p>You will need the Wordpress plugins called <a href="https://wordpress.org/plugins/advanced-custom-fields/">Advanced Custom Fields</a> and <a href="https://www.advancedcustomfields.com/">Advanced Custom Fields: Repeater Field</a>. Create a custom field for your skill bars. The field type will be repeater.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*FRfVKCW6LyOGnxhPjVALSg.png" /></figure><h3>Step 2— Create the sub fields within the repeater field.</h3><p>You will need to add field names for the skill name (value is text) and the skill percentage (value is number) .</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*NE6KbvU30IAmgAnGAUkorQ.png" /></figure><h3>Step 3— Call the fields in your PHP.</h3><p>In your html you will want a div with another div inside of it. We will use an inline style to set the width of the bar div, which we can apply like this:</p><pre> style= “width: &lt;?php the_sub_field(‘skill_percentage’) ?&gt; %”</pre><p>Don’t forget to add the percentage after the PHP, so CSS can render it properly. Now this div will represent the percentage of how confident the client is in their skill.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*I6OXhSxxxotkC5fMxV5fbQ.png" /></figure><p>We also need to add the skill title. A nice touch is calling the skill percentage sub field again in the title. Add a heading or p tag with :</p><pre>&lt;h4&gt;&lt;?php the_sub_field(‘skill_name’) ?&gt; — &lt;?php the_sub_field(‘skill_percentage’) ?&gt;%&lt;/h4&gt;</pre><h3>Step 4— Style your bars with CSS.</h3><p>Now, you can style your bars however you may please. You’ll want to make sure the nested div with the dynamic skill bar is the same height as it’s parent div and is absolutely positioned.</p><p>See below for my CSS.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/618/1*t0BiM8fRxQH8tj7uUPWx5A.png" /></figure><p>And thats it!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/100/1*nHskoHa0wAHf2vueleQUtQ.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=efbdf134ff3" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[“Self Drawing” SVG Line Animation]]></title>
            <link>https://medium.com/@leandrasilver/self-drawing-svg-line-animation-a5cac51f6985?source=rss-ef5699820dbd------2</link>
            <guid isPermaLink="false">https://medium.com/p/a5cac51f6985</guid>
            <category><![CDATA[animation]]></category>
            <category><![CDATA[svg]]></category>
            <dc:creator><![CDATA[Leandra Silver]]></dc:creator>
            <pubDate>Sat, 12 Nov 2016 23:05:00 GMT</pubDate>
            <atom:updated>2016-11-14T17:12:52.229Z</atom:updated>
            <content:encoded><![CDATA[<p>See below for an example of a self drawing SVG by @MyXoToD on codepen and continue reading to make one yourself !</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fcodepen.io%2FMyXoToD%2Fembed%2Fpreview%2FvBlfs%3Fheight%3D600%26amp%3Bslug-hash%3DvBlfs%26amp%3Bdefault-tabs%3Dhtml%2Cresult%26amp%3Bhost%3Dhttp%253A%252F%252Fcodepen.io%26amp%3Bembed-version%3D2&amp;url=https%3A%2F%2Fcodepen.io%2FMyXoToD%2Fpen%2FvBlfs%2F&amp;image=https%3A%2F%2Fs3-us-west-2.amazonaws.com%2Fi.cdpn.io%2F22567.vBlfs.small.50c6ca9c-f2ef-488b-9fb2-adeaef48f311.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/206334d68af6e1d03d0e7a390616ad64/href">https://medium.com/media/206334d68af6e1d03d0e7a390616ad64/href</a></iframe><p>Now that everyone has seen one of these self-drawing animations, at first glance they can look very intimidating. However, they are surprisingly easy to recreate. Tackling one yourself is also a great stepping stone into the vast world of SVGs.</p><p>The most difficult part will be finding yourself an actual SVG to manipulate. You can create some more complicated SVG’s in illustrator, sketch, or inkscape. And you can also make SVG’s directly in your html. If you don’t have an SVG, here is a link to a simple SVG on <a href="http://codepen.io/leandrasilver/pen/ZpRvwx">Codepen</a> I created with <a href="http://editor.method.ac/">Method</a>. Feel free to follow along in Codepen.</p><p>To get started, there are four general steps to follow.</p><ol><li>You need an inline SVG with a stroke.</li><li>Create a long dash that covers the length of the SVG’s stroke.</li><li>Offset this dash so it appears off the path of the SVG.</li><li>Animate the dash so it comes back into view.</li></ol><p>Plus there are two new CSS properties to keep in mind —stroke-dasharrayand stroke-dashoffset.</p><ol><li>stroke-dasharray is for creating dashes in the stroke of SVG shapes. The higher the number, the more space in between dashes in the stroke. No units are needed, as pixels are assumed.</li><li>stroke-dashoffset defines the location along an SVG path where the dash of a stroke will begin. The higher the number, the further along the path the dashes will begin. Again, no units are needed, as pixels are assumed.</li></ol><h3><strong>Step 1 — </strong>You need an SVG with a stroke.</h3><p>This SVG code should be inline with your html, so we can target it with CSS. Have a look at your SVG code, the path element must have an attribute called stroke.</p><pre>&lt;path stroke= “#000000”/&gt;</pre><h3>Step 2— Create a long dash that covers the length of the SVG’s stroke.</h3><p>On the SVG’s path in CSS, add the property stroke-dasharray and a whole number value. I suggest starting with a small value like 10. Here you will notice your SVG is covered in small dashes. But we need the whole path to be covered in a long dash, so now we need to increase this value. Start inputting higher values until the entire path is covered with a dash.</p><pre>path {<br> stroke-dasharray:10;<br>}</pre><p>If you are having a difficult time picking a number for the stroke-dashoffset, you can use JavaScript to find the length of the path. For example:</p><pre>var path = document.querySelector(“svg path”); <br>var total_length = path.getTotalLength();</pre><h3>Step 3— Offset this dash so it appears off the path of the SVG.</h3><p>Add the property stroke-dashoffset, and use the same value you got in Step 2. We want to offset the dash by the dash’s entire length, so it is not visible. So for example:</p><pre>path {<br> stroke-dasharray:1000;<br> stroke-dashoffset:1000;<br>}</pre><h3>Step 4— Animate the dash so it comes back into view.</h3><p>Now, here comes the fun part. Keyframe time! In Step 3 we offset the dash so it is no longer visible. Lets animate it back into view. Make a keyframe and set the stroke-dashoffset back to 0.</p><pre>path {<br> stroke-dasharray:1000;<br> stroke-dashoffset:1000;<br> animation: draw 2s linear forwards;<br>}</pre><pre>@keyframes draw {<br> to {<br> stroke-dashoffset:0;<br> }<br>}</pre><p>Yay! Now you can play around with the animation and even target specific paths if you add classes. The possibilities are endless!</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fcodepen.io%2Fleandrasilver%2Fembed%2Fpreview%2FVmaWWy%3Fheight%3D600%26amp%3Bslug-hash%3DVmaWWy%26amp%3Bdefault-tabs%3Dhtml%2Cresult%26amp%3Bhost%3Dhttp%253A%252F%252Fcodepen.io%26amp%3Bembed-version%3D2&amp;url=https%3A%2F%2Fcodepen.io%2Fleandrasilver%2Fpen%2FVmaWWy%2F&amp;image=https%3A%2F%2Fs3-us-west-2.amazonaws.com%2Fi.cdpn.io%2F821921.VmaWWy.small.47a380ec-5730-4caf-b311-22791f2553a8.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/a468ab1c0e75a728b454088c75fcbd87/href">https://medium.com/media/a468ab1c0e75a728b454088c75fcbd87/href</a></iframe><h3><strong>Related Readings</strong></h3><p><a href="https://css-tricks.com/svg-line-animation-works/">CSS Tricks: How SVG Line Animation Works</a><br><a href="https://24ways.org/2013/animating-vectors-with-svg/">Jake Archibald: Animated line drawing in SVG</a><br><a href="https://24ways.org/2013/animating-vectors-with-svg/">24 ways: Animating Vectors with SVG</a></p><h3><strong>Plugins</strong></h3><ol><li>Lazy Line painter</li></ol><p>This plugin allows you to upload SVG line art and animates it in the browser. It gives you the JavaScript code to copy and paste into your own file. However, make sure there are no fills and no closed paths because the lines need a start and end to animate properly!</p><p><a href="http://lazylinepainter.info/">Lazy Line Painter</a></p><p>2. Vivus</p><p>Vivus is a lightweight JavaScript class (with no dependencies) that allows you to animate SVGs, giving them the appearance of being drawn. There are a variety of different animations available, as well as the option to create a custom script to draw your SVG in whatever way you like.</p><p><a href="https://maxwellito.github.io/vivus/">https://maxwellito.github.io/vivus/</a></p><p>Here is a great example on codepen of vivus in use: <a href="http://codepen.io/unpixel/pen/JooWmB">http://codepen.io/unpixel/pen/JooWmB</a>.</p><p>Have fun with the SVGs!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/100/1*nHskoHa0wAHf2vueleQUtQ.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a5cac51f6985" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Top 5 Must Have User Settings in Sublime Text 3]]></title>
            <link>https://medium.com/@leandrasilver/top-5-must-have-user-settings-in-sublime-text-3-f6129e82d0a9?source=rss-ef5699820dbd------2</link>
            <guid isPermaLink="false">https://medium.com/p/f6129e82d0a9</guid>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[sublime-text-3]]></category>
            <category><![CDATA[coding]]></category>
            <category><![CDATA[workflow]]></category>
            <dc:creator><![CDATA[Leandra Silver]]></dc:creator>
            <pubDate>Tue, 27 Sep 2016 00:03:53 GMT</pubDate>
            <atom:updated>2016-09-27T00:04:31.334Z</atom:updated>
            <content:encoded><![CDATA[<p>So you’ve downloaded your text editor (and it happens to be Sublime Text 3). Now you might feel like you are ready to jump in and start coding. But hold on! Before you begin, try editing your user settings so that you increase your work flow and then thank yourself later. These may seem like little changes, but this is your work environment so customize it to your own personal needs and wants.</p><p>First you will need to get to the <em>user</em> preference sublime file : Sublime Text 3 &gt; Preferences &gt; Settings — User on Mac and Preferences &gt;Settings — User on Windows.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/782/1*upGKf-3OE9A9wFr4DI1GIg.png" /><figcaption>How to get to user settings.</figcaption></figure><p>There should be a file called “Preferences.sublime-settings” that opens. This should already have code in it, and it may look a little intimidating. The settings file is stored in JSON, which is a portable way to display and transfer data files.</p><p><strong>Top 5 Must Haves for User Settings Customizations</strong></p><ol><li>“open_files_in_new_window”: false,</li><li>“word wrap”: true,</li><li>“spellcheck”: true,</li><li>“scroll_past_end”: true,</li><li>“highlight_modified_tabs”: true</li></ol><p>See below for how and why the settings should be implemented. Now everyone has different preferences, but these seem like the most helpful. Double check the items are between the curly brackets and the last item does NOT have a comma, or else the code will break.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/978/1*a3NTWIV7uovrQ9G8VpwveA.png" /><figcaption>Top 5 user settings in sublime text</figcaption></figure><blockquote><strong>1. “open_files_in_new_window”: false,</strong></blockquote><p>This is pretty useful, when you open a new file it adds multiple tabs versus multiple sublime text windows.</p><blockquote><strong>2. “word wrap”: true,</strong></blockquote><p>This is a life saver for when your code lines get very long or when you add 5 different gradients on that pretty background! Having the words wrap make code way easier to read and flow.</p><blockquote><strong>3. “spellcheck”: true,</strong></blockquote><p>No one wants spelling errors. Sublime is basically the best word processor now!</p><blockquote><strong>4. “scroll_past_end”: true,</strong></blockquote><p>This is useful when you are at the end of your file and are coding. You can then scroll and code further up on the screen, instead of being stuck at the bottom.</p><blockquote><strong>5. “highlight_modified_tabs”: true</strong></blockquote><p>This reminds you to save your modified tabs as it glows red when something has not been saved.</p><p>For more possible user settings you can open the default preferences and have a look at all the options, there are lots of comments explaining the settings. However, editing it in this file is discouraged as it reverts back with sublime text updates.</p><p>Other ways to increase workflow include adding snippets, packages, key binds, and even adding a theme to make your editor more inviting to look at for hours upon hours!</p><p>If you have any personal favourite user setting customizations that you feel increase your work flow comment below!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f6129e82d0a9" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>