<?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 Matt LaGrandeur on Medium]]></title>
        <description><![CDATA[Stories by Matt LaGrandeur on Medium]]></description>
        <link>https://medium.com/@mattlag?source=rss-ae609cc873f3------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*nnjKoUL9FwyHkOXx31RlaQ.jpeg</url>
            <title>Stories by Matt LaGrandeur on Medium</title>
            <link>https://medium.com/@mattlag?source=rss-ae609cc873f3------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 11:35:40 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@mattlag/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[I ported my Chrome extension to Edge. TL;DR it was easy.]]></title>
            <link>https://mattlag.medium.com/i-ported-my-chrome-extension-to-edge-tl-dr-it-was-easy-8baee9fa3de5?source=rss-ae609cc873f3------2</link>
            <guid isPermaLink="false">https://medium.com/p/8baee9fa3de5</guid>
            <category><![CDATA[edge]]></category>
            <category><![CDATA[extension]]></category>
            <category><![CDATA[edge-add-on]]></category>
            <category><![CDATA[chrome]]></category>
            <category><![CDATA[chrome-extension]]></category>
            <dc:creator><![CDATA[Matt LaGrandeur]]></dc:creator>
            <pubDate>Wed, 02 Dec 2020 21:46:17 GMT</pubDate>
            <atom:updated>2020-12-02T21:46:17.497Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*cPzq3_wyuF0E6mcKjamONQ.png" /></figure><p>In my professional life I am a UX Designer at Microsoft (supporting the Azure management portal) and I have the opportunity to work with a large talented team of awesome designers. In my spare time I am also something of a JavaScript hobbyist. Something I feel comfortable doing is opening up a browser’s web developer tools and digging into our site’s code. Sometimes this is helpful to see exactly what CSS got shipped, or to pull SVG icons out to use offline.</p><p>Many people I work with, though, are not comfortable digging around in a web page’s guts (in my opinion, a UX Designer can be totally successful at their job without knowing how to code). And, to make things more complicated, almost all of our icons in the Azure management portal use advanced SVG features. Colors and gradients are defined in a central spot, away from the actual SVG code on the page… so it turns into a multi-step process if you want to get portal icons to work as stand-alone SVG files.</p><p>I saw an opportunity! Despite knowing JavaScript, I had never really dug into the world of authoring browser extensions. This, combined with people knocking on my door at regular intervals to have me show them how to grab SVG from our site, gave me a great idea: build a simple browser extension that finds and downloads icons from our website. It would allow me to learn by doing, and I would be helping out a few of my colleges with their day to day work. Fantastic.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/1*gqtQXO3G7NQmJP8unw9wOg.png" /><figcaption>Active Weekly Users</figcaption></figure><p>The Amazing Icon Downloader browser extension was born — for the Chrome browser only. Fast forward about 18 months and somehow there are more than 3,000 active weekly users!</p><h3>The jump from Chrome to Edge</h3><p>Before I get into explaining just how easy this was, I want to emphasize one thing. My browser extension is *<strong>very simple</strong>*. It basically just does a targeted query on the website’s HTML code, grabs all the SVG icons, does some color fill merging, and populates a list of icons to download from a dropdown. There is no backend, no information collected and processed elsewhere, no libraries. If you take away the extension boilerplate, the core JavaScript is less than 300 lines of code.</p><p>With that in mind, the steps to get my Chrome extension into the Edge marketplace was just as simple as I had hoped!</p><p>First I <strong>created a Microsoft partner account</strong> (<a href="https://partner.microsoft.com/en-US/">here</a>) which was easy. And, also free (Google actually charges you to create a developer account 😑)</p><p>Then, the hardest part was dragging and dropping my existing Chrome extension package .zip file:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/1*CxfmjoX5PEA_Rt2Y60DWDw.png" /><figcaption>Edge can just read your Chrome extension package file</figcaption></figure><p>Honestly, I was hoping that this was going to “just work” — and for me it did. There may be some extensions that need a bit of code changes to work on Edge, <a href="https://docs.microsoft.com/en-us/microsoft-edge/extensions-chromium/developer-guide/port-chrome-extension">which you can read about here</a>. But at a basic level, all the work I put into creating a Chrome extension can just be ported directly to Edge 👍</p><p>There are some more options to fill out, but these are very similar to submitting to the Chrome web store. You get to choose <strong>if your extension is publicly visible, what markets it will show up in, give it a category, provide some developer support details, and provide some descriptions, tags, and marketplace images. </strong>This is pretty standard stuff, and easy to provide.</p><p>That’s it! It was like 10 minutes of work, and no coding!</p><h3>Some final thoughts</h3><p>At home I’m a FireFox user, and at work I’m an Edge user… but I also realize that most people mostly use Chrome. In some ways, I was sad when Edge went from their own technology stack and adopted Chromium. But, on the other hand, I lived through the Windows Phone wars, and I know many products live or die by their developer story.</p><blockquote><strong>“Windows Phone will not succeed unless you can run Android apps on it.”</strong><br> — Me, a few years ago when Windows Phone was clearly losing</blockquote><p>In many ways I feel like there are parallels between Windows Phone / Android and Edge / Chrome… except this time Microsoft is doing things right. As a web developer who started around the 2000’s, IE was frankly an embarrassment. Original Edge was a much needed break from the past… but it still suffered from the same Windows Phone problem (yet another development target that people will probably ignore). The new Chromium Edge has all the benefits of Chrome’s technology stack, which benefits developers… and the Edge user experience laid in on top of Chromium is good, while maintaining differentiation for Microsoft.</p><p>Even before developers could port their Chrome extensions to Edge to show up in the Edge Add-ons store, you could just go to the Chrome Web Store <em>in Edge</em> and install add-ons.</p><p>Making the extension story easy for end users and developers is key to the success of Edge.</p><h3>Link-a-palooza</h3><p>I wanted this article to focus on my developer experience for add-ons. But, in the off chance that you use the Azure management portal, and you want to download icons from it, check out the links below. <em>The extension only works after you have logged into portal.azure.com!</em></p><p><strong>Amazing Icon Downloader </strong>in the Edge Add-ons store:</p><p><a href="https://microsoftedge.microsoft.com/addons/detail/amazing-icon-downloader/goanjjfecbakkdmbchgoooajnbiafong">Microsoft Edge Addons</a></p><p><strong>Amazing Icon Downloader</strong> in the Chrome Web Store:</p><p><a href="https://chrome.google.com/webstore/detail/amazing-icon-downloader/kllljifcjfleikiipbkdcgllbllahaob">Amazing Icon Downloader</a></p><p><strong>Amazing Icon Downloader</strong> on GitHub — this could be useful if you want to see how a basic browser plugin works:</p><p><a href="https://github.com/mattlag/Amazing-Icon-Downloader">mattlag/Amazing-Icon-Downloader</a></p><h3>Thanks!</h3><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8baee9fa3de5" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[ES6 Modules: Getting Started Gotchas]]></title>
            <link>https://mattlag.medium.com/es6-modules-getting-started-gotchas-2ad154f38e2e?source=rss-ae609cc873f3------2</link>
            <guid isPermaLink="false">https://medium.com/p/2ad154f38e2e</guid>
            <category><![CDATA[es6]]></category>
            <category><![CDATA[modules]]></category>
            <category><![CDATA[javascript]]></category>
            <dc:creator><![CDATA[Matt LaGrandeur]]></dc:creator>
            <pubDate>Mon, 02 Jul 2018 20:37:18 GMT</pubDate>
            <atom:updated>2021-06-04T15:50:22.314Z</atom:updated>
            <content:encoded><![CDATA[<blockquote><strong><em>Hey y’all —just a quick note: this was written in 2018. Hopefully there are still some useful bits in here, but a lot of this functionality may have changed in the years since I wrote this. I haven’t checked! Happy coding 👍</em></strong></blockquote><p>As of Firefox’s release in May of 2018, <a href="https://caniuse.com/#search=modules">all major browsers now support ES6 Modules natively</a>! Never having used Modules extensively, I began some simple tests to get started… and immediately ran into issues. It seems like a lot of random literature out there around Modules is actually about how products like Webpack or Babel use Modules, and there are subtle and crucial differences compared to how it’s been implemented in native JavaScript.</p><p>Here are the issues I ran into, and how I solved them. Hopefully this article will save somebody a bunch of time :-)</p><h3>Blocked by CORS</h3><p>Firefox and Edge seem to be fine with loading Modules across local files, but Chrome throws this error:</p><blockquote>Access to Script at ‘file:///C:/path/to/main.js’ from origin ‘null’ has been blocked by CORS policy: Invalid response. Origin ‘null’ is therefore not allowed access.</blockquote><p>I get many large projects already have a hard requirement for servers to be running while developing (like React) but for many small projects I just use local files at first. Chrome seems to treat Modules with a higher level of security than Firefox or Edge, and throws this <strong>C</strong>ross <strong>O</strong>rigin <strong>R</strong>esource <strong>S</strong>haring error, saying that local files are not from the <a href="https://developer.mozilla.org/en-US/docs/Web/Security/Same-origin_policy">same origin</a>.</p><p>The Fix for this is to run your project files off a server. I use the most basic one from NPM called <a href="https://www.npmjs.com/package/http-server">http-server.</a></p><h3>type = “module”</h3><p>The great thing about Modules is that you can import and export functionality between files. At some point, your main HTML file will have to have at least one script tag that loads your main file. Your script tag in this case has to have a new type attribute equal to module, like this:</p><pre>&lt;script src=&quot;main.js&quot; type=&quot;module&quot;&gt;&lt;/script&gt;</pre><p>If you don’t include type=&quot;module&quot;, you will get an lot of different errors <strong>that are incredibly confusing</strong>:</p><p>Firefox</p><blockquote>SyntaxError: import declarations may only appear at top level of a module</blockquote><p>Chrome</p><blockquote>Uncaught SyntaxError: Unexpected identifier</blockquote><p>Edge</p><blockquote>SCRIPT1086: SCRIPT1086: Module import or export statement unexpected here</blockquote><p>The Firefox one is especially bad, because it describes another error that could be true, but isn’t really the issue here (it’s referring to the fact that, basically, you can’t put an export in an if/else clause, or in any loop).</p><p>Anyway, add type=&quot;module&quot; to your script tag.</p><h3>You must export a default</h3><p>This is almost always left out of “getting started” tutorials that are comprised of little snippits of examples. All Modules must define a default export, and if they don’t, then these errors get thrown:</p><p>Firefox</p><blockquote>SyntaxError: import not found: default</blockquote><p>Chrome</p><blockquote>Uncaught SyntaxError: The requested module ‘./modulename.js’ does not provide an export named ‘default’</blockquote><p>Edge — actually doesn’t throw an error, but also fails to load the module :-\</p><p>It is good practice to think about what your default export will be, but in this case, it’s actually required to do so. You have to be careful how you export, though, as we’ll see in the next section…</p><h3>Export the “right way”</h3><p>For readability, I always do import and export statements at the very top of the file, it’s a nice overview and context setting for what comes below. export and import syntax allows for a few variations, but only some work in certain situations… mostly having to do with variable scope.</p><p>This, for example, gives you errors:</p><pre>export default count;<br>export {ability};</pre><pre>let count = 10;</pre><pre>function ability() { return &#39;hello!&#39;; }</pre><p>Firefox</p><blockquote>ReferenceError: can’t access lexical declaration `count’ before initialization</blockquote><p>Chrome</p><blockquote>modulename.js:1 Uncaught ReferenceError: count is not defined<br> at modulename.js:1</blockquote><p>Edge</p><blockquote>SCRIPT5113: Use before declaration</blockquote><p>There are two things to know here: Firstly, if your default export is a function, you can do this:</p><pre>export default ability;<br>export {count};</pre><pre>let count = 10;</pre><pre>function ability() { return &#39;hello!&#39;; }</pre><p>No problem — the issue only comes with let or const variables. Also, if you really want to export a variable by default at the top of your file, you can do this:</p><pre>export {count as default};<br>export {ability};</pre><pre>let count = 10;</pre><pre>function ability() { return &#39;hello!&#39;; }</pre><h3>Import the “right way”</h3><h4>Imports must end with .js</h4><p>Module type functionality has been available to early adopters for a while now through the use of transpilers. But the syntax for things like require(&#39;modulename&#39;) and ES6 Modules are slightly different. One up-front gotcha is that ES6 Modules must be full file names, otherwise they will throw errors:</p><pre>import {count} from &#39;./modulename&#39;;</pre><p>Firefox</p><blockquote>Loading failed for the module with source “<a href="http://127.0.0.1:8080/">http://127.0.0.1:8080</a>/modulename”.</blockquote><p>Chrome</p><blockquote>GET <a href="http://127.0.0.1:8080/">http://127.0.0.1:8080</a><a href="http://100.64.5.124:8080/start">/start</a> 404 (Not Found)</blockquote><p>Edge — actually doesn’t throw an error, but also fails to load the module :-\</p><p>Simply including the .js suffix fixes this:</p><pre>import {count} from &#39;./modulename.js&#39;;</pre><h4>Named imports get brackets, defaults don’t get brackets</h4><p>This can be very tricky… for the most part when I export something, I import it to another module with the same name. This isn’t required, though. Let’s go back to our super basic example:</p><pre>export {count as default};<br>export {ability};</pre><pre>let count = 10;</pre><pre>function ability() { return &#39;hello!&#39;; }</pre><p>Now, in another file, I import stuff:</p><pre>import ability from &#39;./modulename.js&#39;;</pre><p>The import ability here does not have brackets around it, which means <strong>it will be assigned the default export</strong>. In this case the default export is actually the variable count equal to the number 10, as opposed to the function.</p><p>If we want to import a specific named thing, use curly braces:</p><pre>import {ability} from &#39;./modulename.js&#39;;</pre><p>This now looks through modulename.js&#39;s exports and searches for ability by name, and creates a local imported value with the same name.</p><p>There are many, many other variations on how to export and import things, I encourage you to read through MDN’s <a href="https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Statements/export">export</a> and <a href="https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Statements/import">import</a> pages. This little difference between brackets and default exports was confusing at first, though, so it’s a basic thing to keep in mind.</p><h3>That’s it!</h3><p>Like I said, hopefully that saves somebody some time. Hit me up with questions or comments: <a href="/service/mailto:matt@mattlag.com">matt@mattlag.com</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2ad154f38e2e" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Making your first font with Glyphr Studio]]></title>
            <link>https://mattlag.medium.com/https-medium-com-mattlag-making-your-first-font-with-glyphr-studio-609719ece0b3?source=rss-ae609cc873f3------2</link>
            <guid isPermaLink="false">https://medium.com/p/609719ece0b3</guid>
            <category><![CDATA[typeface-design]]></category>
            <category><![CDATA[fonts]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[design-process]]></category>
            <category><![CDATA[graphic-design]]></category>
            <dc:creator><![CDATA[Matt LaGrandeur]]></dc:creator>
            <pubDate>Fri, 01 Jun 2018 20:27:43 GMT</pubDate>
            <atom:updated>2022-10-27T23:02:26.621Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jmzJrm1BoIlJtLvS_1I0GA.png" /><figcaption>Typeface Design: Online!</figcaption></figure><p>Way back in 2010 I started to have an interest in creating my own font. After a little investigation I discovered that there was no free / open source typeface designer for Windows. <a href="http://fontforge.github.io/">FontForge</a>, at the time, was Linux only… and all the other options were quite expensive. Since that time FontForge is now available on all platforms — if you are looking for an advanced typeface designer that is free and open source, I whole-heartedly recommend it!</p><p>2010 was also around the time that HTML5 Canvas started to become (somewhat) available. Since I couldn’t find an affordable typeface design tool for Windows, I did what any Interaction Designer / JavaScript aficionado would do — I set out to create my own typeface design tool that was web-based. <a href="http://glyphrstudio.com/">Glyphr Studio</a> was born.</p><blockquote>Glyphr Studio’s focus is to make it easy for first-time typeface designers or hobbyists to create font files.</blockquote><h4>Before we begin</h4><p>Glyphr Studio provides a large set of custom-designed vector editing tools for typeface design. So, it could be the only tool you need to create a whole typeface from start to finish. This tutorial, however, will start from a more common scenario. Many people have some glyphs designed in a different program like Adobe Illustrator or <a href="http://inkscape.org/">Inkscape</a>, or maybe prefer to do their design work in those programs. Glyphr Studio has a powerful Import SVG tool, so this tutorial will go through setting up your external tool, creating glyphs in SVG format, then importing them to Glyphr Studio.</p><h3>▶ Step 1: Figure out your glyph metrics</h3><p>To avoid headaches down the road, we are going to do a little work up front to make sure our <strong>graphic design space</strong> (a.k.a. Adobe Illustrator or Inkscape) matches our <strong>typeface design space</strong> (a.k.a. Glyphr Studio).</p><p>Glyphs (or characters) in a typeface exist in what’s called an Em Square. Em’s are the unit of measure for font files, but for simplicity you can think of them as pixels. Glyphr Stuido has a default setting of 1000 Em Units (which is very common for fonts, 2048 Em Units is the other common size) which means from the top of the tallest letter to the bottom of the descender measures a total of 1000 units. Most individual glyphs are not 1000 Em Units tall, or 1000 Em Units wide — but this Em Square is the default overall design space.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/1*BeV9OWm_JO_JM5d_e0_uOQ.png" /><figcaption>Glyph Metrics or Key Metrics</figcaption></figure><p>In typeface design lingo, these main measurements are called <em>glyph metrics</em> or <em>key metrics</em>. Here is a quick run-down, with Glyphr Studio defaults in parenthesis.</p><ul><li><strong>Ascender</strong> (700 Em Units) distance from the baseline up to the tallest letter.</li><li><strong>Descender</strong> (-300 Em Units) distance from the baseline down to the bottom of the lowest letter. The size of the descender is usually shown as a negative number.</li><li><strong>Baseline</strong> — split between the ascender and descender.</li><li><strong>Cap Height</strong> (675 Em Units) distance from the baseline to the top of the tallest capital letter. Many times this is shorter than the overall Ascender.</li><li><strong>X Height</strong> (400 Em Units) distance from the baseline to the top of (not-rounded) lowercase letters.</li><li><strong>Overshoot</strong> (10 Em Units) the distance that rounded letters extend above or below guide lines. This is usually done to visually compensate between rounded letters and squared-off letters.</li></ul><p>Glyphr Studio <em>knows</em> about all of these metrics. When we start to import SVG information later on, you can tell the import tool about overshoots, ascender heights, and descender heights… and Glyphr Studio will do the right thing when it comes to scaling and moving your shapes to the right place.</p><p>At the very least you should decide on an overall Em Square size (either 1000 or 2048) and also decide where the baseline falls within that square.</p><h3>▶ Step 2: Set up your workspace</h3><p>The first decision for setting up your workspace is how to handle all the glyphs. The <a href="http://en.wikipedia.org/wiki/Basic_Latin_(Unicode_block)">Basic Latin Character Range</a> in Unicode has 95 characters — letters, numbers, and symbols. You don’t have to design all of them, but there are a few main ways to handle all these glyphs:</p><ol><li>Create a single artboard with 95 layers</li><li>Create 95 artboards to show all glyphs at once</li><li>Use one wide artboard to show glyphs side by side</li></ol><p>The pros for #1 and #2 is that there may be some automated way to save single artboards or layers as individual SVG files. Glyphr Studio can import glyphs as individual SVG files, but it can also accept pasted SVG code as text. In practice, I’ve always opted for option #3 — I find that seeing all my glyphs side by side actually helps me design the glyphs themselves.</p><blockquote>Much of typeface design is about how a single glyph looks, but it is also very much about how all the glyphs look <em>together</em>.</blockquote><p>So I would recommend the third option. This does assume that we can copy a subset of shapes in our document that correspond to a single glyph. Adobe Illustrator does this by default — if you multi-select shapes and copy them, you can paste them back in Illustrator as shapes… but if you jump over to a text editor or the Import SVG page in Glyphr Studio and hit paste, it will actually paste the SVG Code equivalent of the shapes you copied. Inkscape has similar functionality through a plugin called <a href="https://inkscape.org/en/%7Ejabiertxof/%E2%98%85object-to-and-from-string">Object to and from String</a>.</p><p><strong>In all 3 cases you’ll be making an artboard or document that is 1000px tall.</strong> The directions below are specifically for options #1 or #2, but the only difference for option #3 is making the width of the artboard or document really wide.</p><p><strong>Adobe Illustrator</strong></p><ul><li>Create a new document and set the <strong>units dropdown</strong> to <strong>Pixels</strong> and set <strong>Width</strong> and <strong>Height</strong> to <strong>1000px</strong>. Or select the the artboard tool to adjust the dimensions of an existing artboard.</li><li>Make sure the upper-left corner of your artboard is 0,0 — with the artboard tool selected the X and Y coordinates should be 0.</li><li>If you move the artboard later, be sure to re-zero the coordinates of the artboard. The artboard coordinates affect the position of the exported shapes.</li><li>Make sure the rulers are visible either through the view menu or right-clicking the canvas. From the top ruler, drag down a guide line and place it at 700px — this will be your baseline.</li><li>If you select a guide, you can set it’s Y value directly from the properties bar.</li><li>Optionally place guide lines for X Height at 300px and Cap Height at 25px (see note below about coordinate systems).</li><li>It’s probably a good idea to lock your guidelines in place, either individually via the Layers Panel, or globally via Right Click &gt; Lock Guides.</li></ul><p><strong>Inkscape</strong></p><ul><li>Create a new document and go to File &gt; Document Properties &gt; Page (tab)</li><li>Under General, set the <strong>Display Units</strong> to <strong>px</strong></li><li>Under Custom Size, <em>first</em> set the <strong>Units</strong> to <strong>px</strong></li><li><em>Then</em> set the <strong>Height</strong> to <strong>1000</strong> and the <strong>Width</strong> to <strong>1000</strong></li><li>Under Scale, set <strong>Scale x</strong> to <strong>1</strong>, Scale y should automatically change to 1</li><li>If you expand the Viewbox section, X and Y should be 0 and Width and Height should be 1000</li><li>From the top ruler, drag down a guide line and place it at 300px — this will be your baseline.</li><li>You can double-click the guide line to adjust it’s Y value and to lock individual guides.</li><li>Optionally place guide lines for X Height at 700px and Cap Height at 975px (see note below about coordinate systems).</li><li>It’s probably a good idea to lock your guidelines in place.</li></ul><h4>A note about coordinate systems</h4><p>Measuring where things are is important to any design process, and unfortunately graphic design spaces are measured differently than typeface design spaces. Making Em Units equal to Pixels is a great first step to make things easier.</p><p>The origin of the coordinate system is a little more tricky. In the typeface design space the origin 0,0 is relative to the baseline, which is part of the way down the overall Em Square. So X=0 is the left hand edge, and moving to the right increases the X value. Y=0 is the baseline, so moving up from the baseline increases the Y value, and moving down from the baseline creates negative Y values.</p><p>In Adobe Illustrator, the 0,0 point is in the upper left, and in Inkscape, the 0,0 point is in the lower left. In the end, they both save as SVG (which has the 0,0 point in the upper left) so importing to Glyphr Studio works from both programs. Depending on what you use, you may have to do a bit of math to figure out where your various guides should be to match the glyph metrics in your font. The instructions in the previous section match the defaults Glyphr Studio uses, so that’s a good place to start.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/1*r_c6k38SpcepMpIrE_6mrQ.png" /><figcaption>Coordinate systems</figcaption></figure><h3>▶ Step 3: Design your glyphs</h3><p>This part is up to you! I would recommend starting with just a few glyphs — maybe 5 or so — and trying to go through the next export / import steps to get a feel for the overall process. There may be some quirks in your design tool or in Glyphr Studio that are better discovered and worked out <em>before</em> you’ve gone off and designed a hundred glyphs.</p><p>Right away you’ll probably need to know how to create <strong>compound shapes</strong>. This is how you achieve a shape like an ‘o’ — this glyph is just two circles. Compound shapes are how we tell the design program we want the center of the o to be transparent.</p><ul><li><strong>Adobe Illustrator</strong> — multi-select two shapes and either Right Click &gt; Make Compound Path, or use the Pathfinder panel.</li><li><strong>Inkscape</strong> — multi-select two shapes and do Path &gt; Combine, or press Ctrl + K</li></ul><h3>▶ Step 4: Prepare your designs for import</h3><p>Here are a few things you may want to do before jumping into Glyphr Studio’s SVG Import page. In my typeface projects, I usually start with a <em>design</em> file. When I’m pretty happy with everything, I make a copy of it and call it something like <em>flattened</em> or <em>export</em>. In the copied file I can make all kinds of destructive actions, like remove guide lines or random shapes, flattening shapes, outlining strokes… basically all the stuff outlined below.</p><h4>Flatten your glyphs</h4><p>Many times it’s easy to design glyphs using lots of shapes. For example, a Capital H is pretty easy to make with 3 rectangles. In a Font File, these same three rectangles are perfectly valid, but it’s a best practice to try to minimize the number of shapes in your glyphs as much as possible. In the H example, those three rectangles can be combined to one path with 12 points.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5MSWKx5Rh7kXcSpGrNPAFw.png" /></figure><p>Partially this is for font file efficiency, but there is also a very strange bug with certain programs that read font files — sometimes overlaps are shown as white at small font sizes… there is no way to fix this besides having a well-formatted font file to begin with.</p><h4>Outline any strokes</h4><p>Shapes in fonts don’t have strokes with weights, they are just simple filled shapes. You may have used stroke weights on paths in your design file, but you’ll need to convert these to shapes before you import them.</p><ul><li><strong>Adobe Illustrator</strong> — Select the path and do Object &gt; Path &gt; Outline Stroke</li><li><strong>Inkscape</strong> — Select the path and do Path &gt; Stroke to Path</li></ul><h4>Reset bounding boxes</h4><p>In Adobe Illustrator, it’s possible to rotate a shape and have that rotation be ‘remembered’. You can tell these shapes if the bounding box is at an angle when the shape is selected. This, unfortunately, is read as a Transform in SVG, and Glyphr Studio does not honor Transforms.</p><p>If you have rotated shapes with rotated bounding boxes, Right Click that shape and select Transform &gt; Reset Bounding Box. Your shape will look the same, but the selection bounding box should be at right angles.</p><h4>Export Layers or Artboards to Files</h4><p>If you are going the route of handling all your glyphs in layers or artboards then now would be a good time to run the script that exports individual SVG files. There is no native way to do this, so you’ll have to find an Extension or Plug-in. A good place to start your search is either the official <a href="https://inkscape.org/en/gallery/%3Dextension/">Inkscape Extensions</a> page or the <a href="https://helpx.adobe.com/illustrator/plug-ins.html">Adobe Illustrator Plug-ins</a> page.</p><p>If you are doing Option #3 from the Step 2 above — directly copying shapes from your design program to Glyphr Studio — you can skip this step.</p><h3>▶ Step 5: Import to Glyphr Studio</h3><p>By this point you should either have individual SVG files for each glyph you have designed, or you can copy/paste SVG code that corresponds to a single glyph.</p><p>It’s time to head on over to <a href="http://glyphrstudio.com/online">glyphrstudio.com/online</a> and do the following:</p><ul><li>On the <em>New Project</em> page, give your project / font a name, then press <strong>Start a new font from scratch</strong>.</li><li>By default you land on the <em>Glyph Edit</em> page, but go to the upper left hamburger menu (three horizontal lines) and navigate to the <em>Font Settings</em> page.</li><li>Review the <strong>Key Metrics</strong> and make sure they match your design dimensions. If you started with the default dimensions described in this article, no changes should be necessary.</li><li>Review the <strong>Glyph Ranges</strong> settings. By default Basic Latin is selected, but if you have additional glyphs you can enable those glyph ranges here.</li><li>After you’re done, select <strong>Import SVG</strong> from the left hand navigation menu.</li></ul><h4>Importing SVG</h4><p>There are three main sections to the Import SVG page:</p><ul><li><strong>Glyph Chooser Panel</strong> — down the left hand side is a list and preview of all the glyphs in your font. The selected glyph here is where your imported SVG shapes will end up.</li><li><strong>Target Glyph, Scaling, Moving, and Metrics</strong> — The top of the right hand side shows the name of the glyph where the shapes will be imported. It also shows:</li><li><strong>Scale</strong> — if selected, the imported shapes will be re-sized to fit the <em>height metrics</em> settings.</li><li><strong>Move</strong> — if selected, the imported shapes will be moved to X=0, and moved up to a Y value based on the <em>height metrics</em> settings.</li><li><strong>Height Metrics</strong> — the combination of these three Ascender / Cap Height / Descender checkboxes, and the two Overshoot checkboxes, describe the overall height of the glyph you are importing.</li><li><strong>SVG Code</strong> — this is where you can either drag and drop your .svg file on to the drop zone, or paste SVG code into the text box. Below the text input box is the final <strong>Import SVG</strong> button. Once your SVG code or file is uploaded, and your other options are selected, this button will import the code and add shapes to the selected glyph.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3UZMGf_hPh4raY9pbFD3HQ.png" /><figcaption>Glyphr Studio Import SVG Page</figcaption></figure><h4>Some Notes</h4><ul><li><strong>Uncheck the Scale and Move options!</strong> All that work we did in steps 1 and 2 should mean your glyph data is ready to be imported without resizing or moving.</li><li><strong>Edit the Selected Glyph button</strong> will jump to the Glyph Edit page for the selected Glyph. Use this option to view the imported shapes up close to see if it’s what you expected.</li><li><strong>Code is saved</strong> if you want to import the same shape to many different glyphs, you can. Either drop the file or paste the code, then select the first glyph target and press <em>Import SVG</em>, then select the second glyph target without entering new code, and press <em>Import SVG</em> again.</li><li><strong>Winding is important</strong>, that is the direction, either clockwise or counterclockwise, that your path travels. In graphic design, path winding is not important. But in typeface design, paths with different winding ‘cut out’ each other, or appear transparent in the regions where they overlap. Compound shapes should import to Glyphr Studio as paths with different winding — but if some glyphs seem like they should have transparent regions but don’t, go check that path’s winding. In Glyphr Studio this is called <strong>overlap mode</strong> and can easily be toggled back and forth in the <em>Attributes</em> panel.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/158/1*cgOkwqQdmAt7zVrJyJ6Eew.png" /><figcaption>Paths with different winding</figcaption></figure><h3>Thank you!</h3><p>If you have any questions or feedback, you can check out <a href="https://www.glyphrstudio.com/help">glyphrstudio.com/help</a> or just send me an email at <a href="/service/mailto:mail@glyphrstudio.com">mail@glyphrstudio.com</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=609719ece0b3" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Adobe XD Review]]></title>
            <link>https://mattlag.medium.com/adobe-xd-review-4fb4b6f1c8a3?source=rss-ae609cc873f3------2</link>
            <guid isPermaLink="false">https://medium.com/p/4fb4b6f1c8a3</guid>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[design-tools]]></category>
            <category><![CDATA[adobe]]></category>
            <dc:creator><![CDATA[Matt LaGrandeur]]></dc:creator>
            <pubDate>Wed, 18 Oct 2017 20:50:19 GMT</pubDate>
            <atom:updated>2018-06-01T20:39:32.489Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*D7zQkGD0W7fIZcCWnd0XrQ.png" /></figure><p>Adobe XD <a href="https://blogs.adobe.com/creativecloud/welcome-adobe-xd-cc/">just hit v1.0</a>, so now seems like a good time to share some of our experiences. Over the past two months here at Microsoft, a set of Designers and Program Managers on our product team have been using Adobe XD to design a new large feature for the <a href="http://portal.azure.com/">Microsoft Azure Portal</a>. Even as a Beta, Adobe XD has been gaining features at a rapid pace. <strong>At this point, in my opinion, it is ready to be used as our primary design tool.</strong></p><h3><strong>What we need from interaction design software</strong></h3><p>In recent years, it seems like there have been a lot of new design and prototyping tools popping up. As a design team, we usually try them out — and overall, we use these high-level requirements to evaluate them:</p><p><strong>Graphic design</strong> — capability to create vector and/or pixel-perfect screens.</p><p><strong>Prototyping</strong> — capability to connect screens in non-linear flows via interaction points.</p><p><strong>Collaboration</strong> — program managers, developers, and other team members must view our designs and leave comments.</p><p><strong>Research</strong> — designs must either be usable or exportable to some format that can be consumed by Design Researchers and usability participants.</p><p>We use PowerPoint a lot because it makes collaboration with non-designers very easy… but it is lacking in the design and prototyping department. Tools like Photoshop and Illustrator are fantastic graphic design tools, but have nothing in the way of prototyping. Newer tools that focus on prototyping often lack basic design tools, or are too difficult for non-designers to access.</p><p>As of a few months ago we felt that there wasn’t a solid UX tool that satisfied all our main requirements. But after evaluating and using Adobe XD for the past two months, we have a good idea of the pros and cons.</p><h3><strong>What we liked</strong></h3><p><strong>It’s like Illustrator Lite</strong> — The design tools are familiar, albeit a somewhat simplified version of other Adobe products.</p><p><strong>Artboards</strong> — XD is made to spin off copies of artboards easily, so user flows come together quickly. Our scenarios started to come together as groups of artboards, and the non-linear organization helped us think about scenario flows.</p><p><strong>Prototyping is extremely easy</strong> — flip over to prototype mode, select any object or group, drag a line to the screen where it should navigate. It’s so easy that you will likely turn all of your designs into prototypes.</p><p><strong>Symbols and Shared Assets</strong> — groups of shapes can be turned into symbols and re-used. Colors and type styles can be defined and reused as well — and shared across your team with CC Libraries.</p><p><strong>Repeat Grid!!!!</strong> — any kind of repeating UI element (think List Views, or gallery views) — just design one row or item, and expanding via Repeat Grid intelligently creates duplicates. This is a small feature, but it’s amazing how much of a time saver it is. You can drag text files to populate columns of data in list views, and photos from file explorer to populate gallery grids.</p><p><strong>Very active community and development </strong>— some rough edges in the Beta are annoying, but each month or two brings <a href="https://blogs.adobe.com/creativecloud/tag/adobe-xd-updates/">new updates and features</a>. Looking into their <a href="https://adobexd.uservoice.com/forums/353007-adobe-xd-feature-requests/filters/top">UserVoice page</a> shows what the XD team is working on next.</p><p><strong>Performance </strong>— XD opens fast, and files load very quickly. Zooming/panning was very smooth even for 100+ artboards. PowerPoint becomes difficult/time consuming to navigate when the number of screens get large. Illustrator does not perform well for large numbers of artboards.</p><p><strong>Cross-platform</strong> — XD works for anybody who already has an Adobe CC license (which is most of us UX folks, and even some PM folks) on Windows or Mac.</p><h3><strong>What was not so great</strong></h3><p><strong>Hover states / little interactions</strong> — how it’s set up now, *any* change to the UI is a new screen. Hover states are not possible. Simple controls like dropdowns suddenly become 3 or 4 screens. <a href="https://adobexd.uservoice.com/forums/353007-adobe-xd-feature-requests/suggestions/12869229-animate-individual-elements-separately-custom-ani">This feature is on their backlog</a>.</p><p><strong>Scrolling</strong> — right now, if the design goes outside the artboard, the whole screen scrolls in prototype mode. There is no way to have part of the UI stationary and part that scrolls. <a href="https://adobexd.uservoice.com/forums/353007-adobe-xd-feature-requests/suggestions/12869166-scrollable-area-not-scrolling-whole-artboard">This feature is currently being developed</a>.</p><p><strong>Global masters </strong>— Symbols go a very long way, but global backgrounds / masters would replace a lot of the symbols for common chrome elements.</p><p><strong>Published prototypes have public links</strong> — Sharing prototypes to non-Adobe CC team members is good, but it’s only available via links available to the general internet. <a href="https://adobexd.uservoice.com/forums/353007-adobe-xd-feature-requests/suggestions/12932118-password-on-shared-prototypes">Password protected links are in the backlog</a>.</p><p><strong>Export to local prototype</strong> — even though you can publish a prototype to a public link (which may have confidentiality concerns), there is no “save locally as web project”.</p><p><strong>Sync comments</strong> — published link prototypes have the option of other people providing comments for each screen (good) but those comments only live online, not in the main application.</p><p><strong>Editability</strong> — People without Adobe CC won’t be able to make edits to the file. Even those with Adobe CC but not very familiar with it, XD’s super large canvas is a unique way to navigate a project, and takes some getting used to.</p><p><strong>Code view / Redlines</strong> — the last stage of any feature is handing off design specs to a developer… there are no features here around Redline views or generating CSS.</p><p><strong>Relatively high barrier to entry for non-designers — </strong>It’s<strong> </strong>much easier to start with than Illustrator or Photoshop, but it’s not PowerPoint. It would be great if there were some free web editor, or text-only editing mode that helps collaborate with content owners / program managers (who aren’t necessarily designers).</p><p><strong>Project scaling</strong> — performance is pretty good, but projects get large very quickly. This is almost a pro — being able to explore ideas in bulk — but it also means we have to keep an eye on file sizes, and how many projects we have open at once.</p><p>With the update cadence, I feel like a lot of these issues will be resolved quickly. The XD UserVoice page is a good sneak peek into <a href="https://adobexd.uservoice.com/forums/353007-adobe-xd-feature-requests/status/1868694">features they have started developing</a> and <a href="https://adobexd.uservoice.com/forums/353007-adobe-xd-feature-requests/status/1868691">features in their backlog</a>.</p><h3><strong>How we tested Adobe XD</strong></h3><p>Most of our current features have existing design assets in PowerPoint or Illustrator, so switching over for current features seemed costly. When a new feature came along, we decided to use it as an opportunity to design with Adobe XD from the start. Over the course of a few weeks we were up to a large project with over 150 screens, encompassing a couple main scenario flows, some A/B brainstorming ideas, and some other miscellaneous stuff.</p><p>There were two designers and a PM working on the feature — we had daily scrums to divvy out work, and somebody was in charge of manually merging sections of artboards into a master iteration for that day (a similar process we’ve used with larger PowerPoint files). Over the course of the project we also grew a stand-alone UI Toolkit, which allowed us to get new screens and sections up and running quickly. At its peak, we hit the Outlook attachment file size limit of 35MB, at that point we started to pare down some of the extra screens. In larger-team reviews we would switch between the design view (shown below) and the prototype / clickthrough mode. XD also has a “Generate link” capability that creates a publicly-accessible URL — we tended to share these out, so people could see our progress even if they weren’t in meetings with us.</p><p>The size of this project certainly stress-tested the application. The August XD update had a large performance improvement, so even with our 150ish screens the app is reasonably well performant.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1_sw2Yp_Bx_s6PAyn6fQwg.png" /><figcaption>A ten-thousand-foot view of our project</figcaption></figure><h3><strong>That’s it!</strong></h3><p>Since we started this project we’ve been getting lots of questions, so hopefully this little review helps.</p><p>Thanks!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4fb4b6f1c8a3" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>