<?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 James D. LaCroix on Medium]]></title>
        <description><![CDATA[Stories by James D. LaCroix on Medium]]></description>
        <link>https://medium.com/@lacroixdesign?source=rss-ddb71778f3f5------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*T7eUtQAm2h4Zf3RFzuUvRw@2x.jpeg</url>
            <title>Stories by James D. LaCroix on Medium</title>
            <link>https://medium.com/@lacroixdesign?source=rss-ddb71778f3f5------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 09:05:08 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@lacroixdesign/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[All in Sync: How our designers keep up with the latest design system assets]]></title>
            <link>https://medium.com/twitter-design-research/all-in-sync-how-our-designers-keep-up-with-the-latest-design-system-assets-98687925d7e?source=rss-ddb71778f3f5------2</link>
            <guid isPermaLink="false">https://medium.com/p/98687925d7e</guid>
            <category><![CDATA[design]]></category>
            <category><![CDATA[design-systems]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[sketch]]></category>
            <dc:creator><![CDATA[James D. LaCroix]]></dc:creator>
            <pubDate>Fri, 29 Jun 2018 16:45:44 GMT</pubDate>
            <atom:updated>2018-06-29T16:46:02.043Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Qh7hhDdl7KtHPF_fB1YjbA.png" /></figure><h4>Horizon Design System, Part 2</h4><p>Design systems empower designers to focus on the many unique problems that they’re solving while providing a consistent experience. Given the array of products that are being worked on at Twitter, we have two design systems: <a href="https://medium.com/twitter-design-research/looking-to-horizon-why-we-built-a-design-system-841d0a9125be">Horizon</a>, that provides a cohesive experience for Twitter consumer products across multiple platforms, and Feather, which encompasses a much larger set of components designed to provide a consistent web experience for all of our professional tools, including internal tools, revenue, and developer applications.</p><p>But for any design system to succeed, it needs to be evangelized and effectively embraced by the various members of the team. Designers serve a unique role in being able to communicate the use of the system throughout their work. However, designers need to be aware and have access to the most up-to-date components. Documentation is a must, but providing designers with ready-to-use art files makes the design system readily accessible and easy to put into action.</p><h3>Defining the solution</h3><p>When I first joined the design team at Twitter, we had an <a href="https://subversion.apache.org/">SVN</a> system in place for getting designers up-to-date <a href="https://www.sketchapp.com/">Sketch</a> assets for our Feather design system. Unfortunately, that solution only worked when designers remembered to pull the latest resources and, let’s be honest, not all of us were consistent, so we ended up using previous versions of components instead of taking advantage of the most recent updates. As we started to grow our design systems with Horizon, we needed a better way. Since I’m notorious for experimenting with new design tools and making tweaks to improve them, it’s no wonder that I gravitated toward the challenge.</p><p>A small team of us met to identify the criteria for a successful solution and came up with the following:</p><ul><li>We needed to limit the number of people who could make changes to the design system Sketch files.</li><li>Design assets needed to be updated in the background so the process didn’t require extra effort or an opportunity to forget to fetch the latest assets.</li><li>The assets should live in a place that would be easily accessible in the design workflow.</li><li>There had to be a low barrier to entry for setup so the current team and future members could onboard efficiently.</li></ul><p>We were already using Google Drive for storing and sharing files amongst the team so we could leverage that service to do a lot of the heavy lifting and then all we had to do was to make the assets easily accessible. In the past, I’ve used <a href="https://en.wikipedia.org/wiki/Symbolic_link">symbolic links</a> to sync personal settings for various applications across different machines, so I implemented the same solution for sharing design assets to the team.</p><h3>How it works</h3><p>We created a .Design directory that stores the design assets for both Feather and Horizon. On a Mac, the . prefix hides the directory by default in Finder to avoid any confusion. This directory is stored in Google Drive and only those working on the component systems have access to write to the directory — anyone else with the URL has access to read the files.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/792/1*a0UX9Cwtjm_2poRsNuo7aQ.png" /><figcaption><em>We’ve structured our directory to include assets for both design systems, fonts, plugins, colors, and various other tools.</em></figcaption></figure><p>Google Drive handles the task of making sure that our designers have the most up-to-date Sketch files on their computer, but we needed a way to make those files easily accessible. So, we created an executable installer using Bash that handles the difficult parts of the setup.</p><p>You just need to follow a handful of steps:</p><ol><li>Install <a href="https://dl.google.com/drive-file-stream/googledrivefilestream.dmg">Google Drive File Stream</a> or <a href="https://www.google.com/intl/en-GB_ALL/drive/download/backup-and-sync/">Google Backup &amp; Sync</a> and make sure the application is running.</li><li>Visit the URL to the .Design directory and select Add to Drive.</li><li>Give the application a few minutes to sync.</li><li>Download and double-click the installer.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/566/1*AGJtdL7RaaUEneP9PvrKjw.png" /><figcaption><em>Once a designer has completed the process, they’ll always have access to the most up-to-date files in their Sketch templates.</em></figcaption></figure><h3><strong>Creating the installer</strong></h3><p>This was my first time creating an executable Bash script for others to use, so there was a fair amount of trial and error. I’ll break down the decision making that went into the creation of our script and I’ll also provide a general template for creating your own.</p><p>The basic premise of the script is that it breaks down tasks into functions that are then executed based on your setup. As I walk through these functions, you may notice that I am using $VARIABLES to store reusable data. These variables are defined later on in the process.</p><h4><strong>Establish directories</strong></h4><p>The establishDirectories function looks into Sketch’s Application Support to see if the directories for Templates and Plugins exist. If you’ve already added plugins or templates, then this function won’t perform any actions, otherwise it will create a place to store the assets. This is achieved through the commands below.</p><pre>establishDirectories () {<br><em># Create templates directory if it does not exist<br></em>mkdir -p &quot;$SKETCH_TEMPLATES&quot;</pre><pre><em># Create plugins directory if it does not exist<br></em>mkdir -p &quot;$SKETCH_PLUGINS&quot;<br>}</pre><h4><strong>Clean previous</strong></h4><p>The next task that the script needs to accomplish is to clean any previous installations. This way, you can use the script to update the install if you ever have any problems. The clean function below moves the symbolic links from previous installs in your trash. This helps to avoid any conflicts.</p><pre>clean () {<br><em># Use mv to test and then switch to rm -rf when directories are correct</em></pre><pre><em>if</em> [ -e &quot;$FEATHER_DESTINATION&quot; ]<br><em>then<br># mv &quot;$FEATHER_DESTINATION&quot; &quot;$TRASH&quot;<br></em>rm -rf &quot;$FEATHER_DESTINATION&quot;<br><em>fi</em></pre><pre><em>if</em> [ -e &quot;$HORIZON_DESTINATION&quot; ]<br><em>then<br># mv &quot;$HORIZON_DESTINATION&quot; &quot;$TRASH&quot;<br></em>rm -rf &quot;$HORIZON_DESTINATION&quot;<br><em>fi<br></em>}</pre><h4><strong>Install assets</strong></h4><p>Most importantly, the script needs to be able to install the assets. Thus, the install function symbolically links the directories for both design systems from Google Drive to the Templates directory in Sketch.</p><pre>install () {<br><em># Symlink Feather templates<br></em>ln -s &quot;$FEATHER_SOURCE&quot; &quot;$FEATHER_DESTINATION&quot;</pre><pre><em># Symlink Horizon templates<br></em>ln -s &quot;$HORIZON_SOURCE&quot; &quot;$HORIZON_DESTINATION&quot;<br>}</pre><p>This function is also used to copy plugins, fonts, and a color palette file from the .Design directory in Google Drive directory to your computer.</p><pre>install () {<br><em># Symlink Feather templates<br></em>ln -s &quot;$FEATHER_SOURCE&quot; &quot;$FEATHER_DESTINATION&quot;</pre><pre><em># Symlink Horizon templates<br></em>ln -s &quot;$HORIZON_SOURCE&quot; &quot;$HORIZON_DESTINATION&quot;</pre><pre><em># Copy Paddy plugin<br></em>/bin/cp -rf &quot;$PLUGIN_SOURCE/Paddy.sketchplugin&quot; &quot;$SKETCH_PLUGINS&quot;<br>  <br><em># Copy Sketch Palettes plugin<br></em>/bin/cp -rf  &quot;$PLUGIN_SOURCE/Sketch Palettes.sketchplugin&quot; &quot;$SKETCH_PLUGINS&quot;</pre><pre><em># Copy SendToSlack plugin<br></em>/bin/cp -rf &quot;$PLUGIN_SOURCE/SendToSlack.sketchplugin&quot; &quot;$SKETCH_PLUGINS&quot;</pre><pre><em># Copy color palette to desktop<br></em>/bin/cp -rf &quot;$COLOR_PALETTE_SOURCE&quot; &quot;$DESKTOP&quot;</pre><pre><em># Copy icon fonts<br></em>/bin/cp -rf &quot;$EDGE_ICONS_SOURCE&quot;/*.ttf &quot;$FONTS_DESTINATION&quot;<br>}</pre><h4><strong>Establish directories, clean existing installs, and install assets</strong></h4><p>Now that the core functions are created, the install script needs to run them in sequence. The cleanInstall function is responsible for this task. It begins by setting more defined variables. Eventually, the script has a final function that sets the $1 variable to the path on your computer, but these variables set the paths for the sources and destinations of what is being installed.</p><p>There is also some messaging set in a variable for providing feedback to the to anyone installing the assets. Many of our computers are have a <a href="https://github.com/julienXX/terminal-notifier">terminal-notifier</a> installed so I’m taking advantage of the ability to provide a macOS notification, but the same message is repeated in the terminal for instances when terminal-notifier is not installed. Setting these messages as variables allow them to be reused.</p><p>Once the variables are set, the previous functions are executed, Font Book is opened to recognize the newly installed fonts and a success message is triggered.</p><pre>cleanInstall () {<br><em># Set Source Variables<br></em>DESIGN_PATH=$1<br>FEATHER_SOURCE=$DESIGN_PATH/Feather<br>HORIZON_SOURCE=$DESIGN_PATH/Horizon<br>PLUGIN_SOURCE=$DESIGN_PATH/Plugins<br>ICON_SOURCE=$DESIGN_PATH/Tools/&quot;Install Script&quot;/Icon.png<br>COLOR_PALETTE_SOURCE=$DESIGN_PATH/Colors/twittercolors.sketchpalette<br>EDGE_ICONS_SOURCE=$DESIGN_PATH/Fonts/&quot;Edge Icons&quot;</pre><pre><em># Set Destination Variables<br></em>SKETCH_TEMPLATES=$HOME/Library/&quot;Application Support&quot;/com.bohemiancoding.sketch3/Templates</pre><pre>SKETCH_PLUGINS=$HOME/Library/&quot;Application Support&quot;/com.bohemiancoding.sketch3/Plugins</pre><pre>FEATHER_DESTINATION=$SKETCH_TEMPLATES/Feather<br>HORIZON_DESTINATION=$SKETCH_TEMPLATES/Horizon</pre><pre>FONTS_DESTINATION=$HOME/Library/Fonts</pre><pre>DESKTOP=$HOME/Desktop<br>TRASH=$HOME/.Trash</pre><pre><em># Set messaging<br></em>SUCCESS_TITLE=&quot;🤘 You did it!&quot;<br>SUCCESS_MESSAGE=&quot;Twitter design assets have been successfully installed.&quot;</pre><pre><em># Make sure directories exist<br></em>establishDirectories</pre><pre><em># Clean previous installations<br></em>clean</pre><pre><em># Install the assets<br></em>install</pre><pre><em># Open Font Book to recognize new fonts<br></em>open -a &quot;Font Book&quot;</pre><pre><em># Success Message<br></em>terminal-notifier -title &quot;$SUCCESS_TITLE&quot; -message &quot;$SUCCESS_MESSAGE&quot; -appIcon &quot;$ICON_SOURCE&quot;<br>echo &quot;$SUCCESS_TITLE&quot;<br>echo &quot;$SUCCESS_MESSAGE&quot;<br>exit<br>}</pre><h4><strong>Checking for previous requirements</strong></h4><p>Since we’re using Google Drive to supply every designer with the newest versions of files, we need to ensure they’ve installed one of the Google Drive syncing products and added the .Design directory to their drive. Then the script runs a final checkCleanInstall function that verifies these criteria are met before proceeding with the install.</p><p>To further complicate things, both Google Drive File Stream and Google Backup &amp; Sync store files in different locations. The function accepts either app install, but gives preference to the Google Drive File Stream product since that is the most recent release.</p><p>Basically, the function first checks to see if you’re using Google Drive File Stream and has the .Design directory added. If that’s true, then it will execute the cleanInstall function while passing in the correct asset location to the $1 variable. If it fails, it checks to see if you have Google Backup &amp; Sync installed with the .Design directory added and then goes through the same process. If neither of those criteria are met, it checks to see if either syncing service is installed and gives a message to add the .Design directory to your drive. Finally, if none of the criteria are met, it gives instructions to start the process from the beginning. Once again, this messaging is set in variables to take advantage of macOS notifications as well as echoing text in the terminal.</p><p>This script can be used with other syncing services like <a href="https://www.dropbox.com/">Dropbox</a> and the major change would be the directory that you’re setting. Additionally, we support people using either one of Google Drive’s syncing products. Having a single solution allows us to remove the second if statement from the function. Here’s the final function.</p><pre>checkCleanInstall () {<br><em># Set variables<br></em>GOOGLE_DRIVE_FILE_STREAM_LOCATION=&quot;/Volumes/GoogleDrive/My Drive&quot;<br>GOOGLE_DRIVE_LOCATION=$HOME/&quot;Google Drive&quot;</pre><pre>DIRECTORY_FAIL_TITLE=&quot;🤔 Hmm…It appears that you haven’t added the assets to your drive.&quot;<br>DIRECTORY_FAIL_MESSAGE=&quot;Make sure to add the .Design directory to your drive.&quot;<br>DIRECTORY_FAIL_URL=&quot;https://drive.google.com/open?id=0B9fABTNKWq4TRTFGZkhYcTFkMlk&quot;</pre><pre>SYNC_FAIL_TITLE=&quot;🤔 Hmm…It appears that you haven’t installed Google Drive File Stream.&quot;<br>SYNC_FAIL_MESSAGE=&quot;Install Google Drive File Stream and add the .Design directory to your drive.&quot;<br>SYNC_FAIL_URL=&quot;https://dl.google.com/drive-file-stream/googledrivefilestream.dmg&quot;</pre><pre><em># Check to see if .Design directory exists in Google Drive File Stream<br>if</em> [ -e &quot;$GOOGLE_DRIVE_FILE_STREAM_LOCATION&quot; ] &amp;&amp; [ -e &quot;$GOOGLE_DRIVE_FILE_STREAM_LOCATION/.Design&quot; ];</pre><pre><em>then<br># .Design directory exists in Google Drive File Stream, proceed with install<br></em>cleanInstall &quot;$GOOGLE_DRIVE_FILE_STREAM_LOCATION/.Design&quot;</pre><pre><em># Check to see if .Design directory exists in Google Backup &amp; Sync<br>elif</em> [ -e &quot;$GOOGLE_DRIVE_LOCATION&quot; ] &amp;&amp; [ -e &quot;$GOOGLE_DRIVE_LOCATION/.Design&quot; ];</pre><pre><em>then<br># .Design directory exists in Google Backup &amp; Sync, proceed with install<br></em>cleanInstall &quot;$GOOGLE_DRIVE_LOCATION/.Design&quot;;</pre><pre><em>elif</em> [ -e &quot;$GOOGLE_DRIVE_FILE_STREAM_LOCATION&quot; ] || [ -e &quot;$GOOGLE_DRIVE_LOCATION&quot; ];</pre><pre><em>then<br></em>terminal-notifier -title &quot;$DIRECTORY_FAIL_TITLE&quot; -message &quot;$DIRECTORY_FAIL_MESSAGE&quot; -appIcon &quot;$ICON_SOURCE&quot; -timeout &quot;30&quot; -open &quot;$DIRECTORY_FAIL_URL&quot;<br>echo &quot;$DIRECTORY_FAIL_TITLE&quot;<br>echo &quot;$DIRECTORY_FAIL_MESSAGE&quot;<br>echo &quot;$DIRECTORY_FAIL_URL&quot;</pre><pre><em>else<br></em>terminal-notifier -title &quot;$SYNC_FAIL_TITLE&quot; -message &quot;$SYNC_FAIL_MESSAGE&quot; -appIcon &quot;$ICON_SOURCE&quot; -timeout &quot;30&quot; -open &quot;https://dl.google.com/drive-file-stream/googledrivefilestream.dmg&quot;<br>echo &quot;$SYNC_FAIL_TITLE&quot;<br>echo &quot;$SYNC_FAIL_MESSAGE&quot;<br>echo &quot;Google Drive File Stream: $SYNC_FAIL_URL&quot;<br>echo &quot;.Design Directory: $DIRECTORY_FAIL_URL&quot;</pre><pre><em>fi<br></em>}</pre><p>To make the install script easy to run, all of these functions are included in a single file with a command to execute checkCleanInstall at the end. While building the script, I save the file as Install Design Assets.bash for proper syntax highlighting. Once tested and completed, I save the file as Install Design Assets.command with the extension hidden. The final file looks like the example below.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/3e7703d840efc54a444e66a26991a06f/href">https://medium.com/media/3e7703d840efc54a444e66a26991a06f/href</a></iframe><p>The next step is to make the command executable. This just requires typing chmod +x followed by the path to the file in the terminal. Pressing return will make the file executable.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mlhgt8YsfYkYGG6GJfBscg.png" /><figcaption><em>This allows you to double-click the script to install it like an application.</em></figcaption></figure><p>Finally, an icon is added to the executable file to make it easy for people to discover. The file is then compressed and shared along with the instructions to the team.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/816/1*FcI5cVrYtdq0LBkr2j_rfQ.png" /><figcaption><em>Compressing the script protects it from being rendered as text when shared in applications like Slack.</em></figcaption></figure><h4><strong>Bare-bones template</strong></h4><p>To get you started, I’ve removed a lot of the items that are unique to our team at Twitter and provided a bare-bones template.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/e3046e123ffb526140c8d7a827cbf814/href">https://medium.com/media/e3046e123ffb526140c8d7a827cbf814/href</a></iframe><h3>So how did we do?</h3><p>For the past year and a half, this solution has worked really well for our team. It helped designers to quickly adopt our evolving design systems in their daily work and made onboarding new designers so much easier. The benefit to scripting the solution has made it quick to make minor changes in the rare case that something goes awry. Once the script has been updated, you just need to run it again to get everything back to working order.</p><p>But this solution isn’t perfect. Instead of single action, you’re still required to complete a few steps to get everything set up, so there’s always an opportunity to miss a step. And there are instances when Google Drive or Sketch may change file locations or a Sketch update changes how directories work in their templates folder.</p><p>We’re always looking for ways to keep improving how we use our design systems at Twitter. If you’ve come across anything that works well for your team or have any questions, please leave a comment or reach out to me on <a href="http://www.twitter.com/">Twitter</a> <a href="https://twitter.com/lacroixdesign">@LaCroixDesign</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=98687925d7e" width="1" height="1" alt=""><hr><p><a href="https://medium.com/twitter-design-research/all-in-sync-how-our-designers-keep-up-with-the-latest-design-system-assets-98687925d7e">All in Sync: How our designers keep up with the latest design system assets</a> was originally published in <a href="https://medium.com/twitter-design-research">Twitter Design &amp; Research</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Far From Finished]]></title>
            <link>https://medium.com/lacroix-design-co/far-from-finished-5ee7ea4d5ae7?source=rss-ddb71778f3f5------2</link>
            <guid isPermaLink="false">https://medium.com/p/5ee7ea4d5ae7</guid>
            <category><![CDATA[web-design]]></category>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[product-design]]></category>
            <dc:creator><![CDATA[James D. LaCroix]]></dc:creator>
            <pubDate>Wed, 21 Oct 2015 15:38:23 GMT</pubDate>
            <atom:updated>2015-10-21T15:38:23.767Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*RocADvaBP4ij-NMu2gnZig.jpeg" /></figure><h4>For us, a launched product rarely means that we are done and it is often future iterations that produce the best results. Nowhere is this more evident than on our own site.</h4><p>As it turns out, finding contentment is not one of my stronger traits and this is especially evident when it comes to design. There’s always been the excitement when something Michael and I have made is released to the world. That moment is fleeting once we begin to dissect every minute detail in search of opportunities for improvement.</p><p>Critique is important and I wouldn’t have it any other way. Although, this was quite problematic when I began my career as a print designer and everything that I designed was more permanent. As a web and product designer, I delight in the flexible and iterative qualities of the medium.</p><p>In the business of client services, you do not always get the opportunity to continually improve upon everything that you ship. Very often, the client is happy, the project ends, you get paid and the thing that you created goes on without you. Sadly, these projects miss out on the beneficial iterations that happen after your have been able to assess how the visitors or users interact with the product.</p><p>Luckily, we have had the pleasure to work with a number of clients who allow us to return to previous projects and tackle new challenges. I’m consistently assured that these experiences will continue to improve if we never treat them as finished. Nowhere is this more evident than in our personal projects. For example, our own website is never finished and we are constantly trying to improve the our visitors’ experience.</p><p>Nearly a year ago, I wrote a <a href="http://www.lacroixdesign.net/blog/doing-more-with-less/">post for the launch of our new website</a> about how a simpler solution provides us with the freedom to iterate. Our current website utilizes <a href="https://middlemanapp.com/">Middleman</a> to generate a static site upon deployment and this provides a fantastic venue for exploring and implementing new solutions. Earlier this year, we made some improvements to our website. In this post, I’d like to share the decision making behind these changes and the results that we’ve received.</p><h3>The Homepage Welcome Section</h3><p>First of all, no other place on the site has received more copy revisions than the first section of our homepage. When you tackle a wide variety of design problems with a range of solutions and tools, describing your business in one sentence is far from easy.</p><p>For the first time in a long time, I feel pretty good about what we have on there now. We love to design solutions that establish a connection and allow our clients to engage the audience in a very human way. We decided this copy needed more emphasis, so we adjusted the typography accordingly.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/0*-J4UvUlCOFRTVn-Y.gif" /></figure><p>Our previous background for this section was my desk. I believe that we have a nice workspace and I do tend to keep a tidy desk. However, this was far from being a compelling image for the homepage. We explored a number of solutions for this that included illustrations, solid colors, SVG animation and we eventually decided to use video. We love the personal proximity with which people use mobile devices and found that this created a visual connection to what we value. We also explored various methods of tinting the video to match our pink brand color, but we will cover that in a future post.</p><h3>Featured Work &amp; Services Section</h3><p>Another area of our site we were never content with was the featured work section of the homepage. For a while, Michael and I were pretty set on trying to contain these in an interesting shape. After exhausting nearly every option we could think of, we eventually determined it was not the best solution and opted to go with a layout that is more consistent with the case studies on our site. In the end, this provides visitors with a more cohesive experience.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/0*MwcFsvsqzf89mN8c.jpg" /></figure><p>Previously, we also used an angled container for our services section. On a micro level, we enjoyed this concept, but it did not quite fit with everything else on our website. We determined that our previous image of my workspace might be appropriate in this space. It connects to the collection of tools and devices that we use solve our clients problems. We also made some typography changes to the headers in both of these sections.</p><h3>Improving Visitor Engagement on Blogs &amp; Case Studies</h3><p>Blog posts drive a lot of traffic to our site and this has made writing them a much more enjoyable process. Plus, the increased traffic makes examining the analytics more interesting. We found that many visitors were spending time on the site to read the entire post, but were bouncing off of the page once they finished.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/0*gSQO1IUcGRUHftcu.jpg" /></figure><p>Thus, we decided to implement a solution that encourages visitors to explore more content. Each post now concludes with a call to action followed by previews for three other posts. We also decided to add a similar experience to the individual case studies pages. The result? We are now seeing visitors land on individual blog or case study and diving deeper into the site.</p><h3>Keeping the Conversation Going</h3><p>Since our website is deployed as a static build, commenting functionality is not a feature of our blog, nor do we really desire to manage comments. However, we do want to keep the conversation going, and Michael and I want to be available for any questions or responses. For this reason, we built a Twitter intent option into our post structure.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*99wDeCjuagV1D4DP.png" /></figure><p>We have also found that some of our blog posts garner a lot of readers from <a href="https://news.layervault.com/">Designer News</a>. As a result, we decided to add a posting option so that our readers can continue the conversation through comments on Designer News.</p><h3>Increasing Email Newsletter Signup</h3><p>In August of last year, we added a subtle newsletter call to action to the footer of our site. Although we began to see subscribers trickle in, this was in no way a successful solution. Therefore, we decided to redesign this call to action to give it more visual weight.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/0*jnG0aXWpD-xpHxtw.jpg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/0*Cqc03Yt1fgAaSRDA.jpg" /></figure><p>The more prominent call to action has more than doubled our list, and we are regularly adding new subscribers. This, in turn, leads to a new challenge of keeping up with our monthly delivery. Due to a busy workload, we have been a bit lax over the past several months, but we plan to pick back up soon.</p><h3>We’re Still Far from Finished</h3><p>Michael and I have an ongoing <a href="https://trello.com/jameslacroix/recommend">Trello</a> board where we regularly add new ideas and discuss solutions for improving our website. In doing so, we are also gaining clients who learn to value the process and set aside budgets for continual improvement.</p><p><em>Originally published on May 21, 2015 at </em><a href="http://www.lacroixdesign.net/blog/far-from-finished/"><em>www.lacroixdesign.net</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5ee7ea4d5ae7" width="1" height="1" alt=""><hr><p><a href="https://medium.com/lacroix-design-co/far-from-finished-5ee7ea4d5ae7">Far From Finished</a> was originally published in <a href="https://medium.com/lacroix-design-co">LaCroix Design Co.</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Lessons Learned From Working Remotely]]></title>
            <link>https://medium.com/lacroix-design-co/lessons-learned-from-working-remotely-436a6c72ed7?source=rss-ddb71778f3f5------2</link>
            <guid isPermaLink="false">https://medium.com/p/436a6c72ed7</guid>
            <category><![CDATA[design]]></category>
            <category><![CDATA[communication]]></category>
            <category><![CDATA[remote-working]]></category>
            <dc:creator><![CDATA[James D. LaCroix]]></dc:creator>
            <pubDate>Mon, 19 Oct 2015 14:26:48 GMT</pubDate>
            <atom:updated>2015-10-19T16:49:22.088Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*NLTddLu2APzbhzfvmcHZiw.jpeg" /></figure><h4>How a year of remote work transformed our operation.</h4><p>From day one, my business has been a laboratory for experimentation. My time spent working in the music industry piqued my interest in entrepreneurship and small business ventures, but I initially knew very little about running a design studio. With no previous experience as a design employee, my company was a blank canvas for how a design studio could be run. Of course, this has resulted in plenty of mistakes and hard lessons but over time, I’ve continually welcomed the opportunity to experiment with all aspects of the business.</p><p>In the same manner that we use design thinking to deliver successful solutions for our clients, we believe that design thinking can be applied to the process that leads us to those results. Experimentation and iteration provides continual improvement in the way we operate. One such experiment meant moving my company nearly 500 miles from Nashville to Chicago. The relocation provided us with an opportunity to move out of our comfort zone in order to improve as designers and developers. It also made me grow as a business owner. Leaving a small market where my business was established and operating successfully to a much larger market where we would be virtually unknown offered its fair share of opportunities and risk.</p><p>To ease the transition, Michael remained in Nashville for a year and we began working remotely. Operating out of separate locations meant that we had to adjust our workflows to ensure that the quality of our work would not slip but rather improve as we began to enter a larger market. As with any new experiment, our foray into remote work had its bumps and bruises. Before long, we had adapted and found ourselves relishing in our newfound workflows.</p><p>Twelve months ago, this year-long experiment came to an end as Michael made the move to Chicago so that we could once again work within the same office. Now, with a full year of working beside one another, we have realized that the lessons learned from working remotely have made us better designers, developers and communicators.</p><p><strong>We became better writers.</strong> Remote work eliminated the opportunity for casual conversation. Phone calls and video chats consume too much time so we chose to limit those to important occasions. Writing became our main source of communication. This required articulation with our thoughts in order to get our points across clearly and efficiently. Whether using email, project management software or our internal chat software, working remotely demanded deliberate thought when sharing our ideas and critiques.</p><p>In turn, this helped with client correspondence as well. We devised systems for reviewing and editing proposals or any long-form communications with clients. This required that initial contributor took the time to encompass all of the finer details of the project so that the reviewer would be able to provide edits that helped to clarify the material. Often, we would review documents several times to assure that our correspondence represented the same thoughtfulness that we give to our work.</p><p><strong>We had to be more organized.</strong> When working remotely, little things that slip through the cracks can’t happen. Thus, we had to develop a bulletproof set of systems that we still use today. Completed tasks needed to be recorded so that both partners were keenly aware of what needed to be accomplished. Additionally, keeping files and resources organized was crucial for streamlined workflow at both offices.</p><p>We relied on our project management software to meet these needs. The tool that we were already using, <a href="https://basecamp.com/">Basecamp</a>, was our initial solution. Utilizing email as its notification channel, Basecamp allowed us to also bring clients into the project management software. This way, our clients could observe and communicate as their project was progressing. We have since progressed to using <a href="https://trello.com/jameslacroix/recommend">Trello</a> for all internal projects and have begun testing it on some client projects. Trello provides us with a more visual view of the project status. Additionally, tasks can proceed through a series of stages rather than simply complete or incomplete.</p><p>While working in remote offices, we still needed to have a channel for regular conversation — enter chat service. We initially used <a href="https://campfirenow.com/">Campfire</a>, followed by <a href="https://www.hipchat.com/">Hipchat</a> and then happily landed on <a href="https://slack.com/r/024l00bf-02533q4k">Slack</a>. To this day, the majority of our conversations still take place in Slack. The service provides separate channels to keep our thoughts organized and the ability to search through these communications at a later time. Seamlessly working with third-party applications, Slack will notify us of Trello updates or Git commits. It will also parse the information from shared links which allow us to quickly share screenshots of ideas using <a href="http://www.getcloudapp.com/">CloudApp</a>.</p><p><strong>We learned to be more decisive.</strong> One of the fallbacks of being a designer or developer is overthinking our solutions. We are all guilty of this from time to time. Self-doubt will sometimes creep in and minor iterations end up consuming hours of work only to return to where you first started. When working in the same office, it is quite convenient to distract a co-worker for feedback on every little step. In this circumstance, self-doubt begins to paralyze your workflow. Working remotely required proactive and confident decisions.</p><p>All in all, this experiment in working remotely has had a lasting, positive effect on our non-remote workflows. After working in the same office for a year now, we’ve found that these changes have improved the productivity and quality of our work.</p><p><em>Originally published on </em>August 19, 2014 <em>at </em><a href="http://www.lacroixdesign.net/blog/lessons-learned-from-working-remotely/"><em>www.lacroixdesign.net</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=436a6c72ed7" width="1" height="1" alt=""><hr><p><a href="https://medium.com/lacroix-design-co/lessons-learned-from-working-remotely-436a6c72ed7">Lessons Learned From Working Remotely</a> was originally published in <a href="https://medium.com/lacroix-design-co">LaCroix Design Co.</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Streamlining Our Proposal Writing Process]]></title>
            <link>https://medium.com/lacroix-design-co/streamlining-our-proposal-writing-process-fad7542ded10?source=rss-ddb71778f3f5------2</link>
            <guid isPermaLink="false">https://medium.com/p/fad7542ded10</guid>
            <category><![CDATA[markdown]]></category>
            <category><![CDATA[writing]]></category>
            <category><![CDATA[proposal]]></category>
            <dc:creator><![CDATA[James D. LaCroix]]></dc:creator>
            <pubDate>Fri, 16 Oct 2015 17:39:54 GMT</pubDate>
            <atom:updated>2015-10-16T18:52:49.442Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*__Wd33xS4Y-MzEJv7t1QCw.jpeg" /></figure><h4>How we are using Git, Markdown, CSS and Marked to create proposals more quickly.</h4><p>As designers and developers, it is our innate desire to spend time making things. Nevertheless, when you are running your own business, there are many other responsibilities required before, during and after a project.</p><p>One of these essential duties is writing proposals. After nearly 10 years of running LaCroix Design Co., the role of proposal writer is still one of my least favorites. A great deal of thought and effort goes into every proposal we send out. As a result, many hours are typically spent compiling notes from meetings and phone calls into a well-formulated document that not only proposes the most optimal solution, but also outlines the best process for arriving at that solution. Needless to say, it can be quite disheartening when a proposal is rejected or not even considered.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/480/0*QwtcTEnr8deoFw7h.gif" /></figure><p>Proposals, however, serve a crucial role in the relationship between the client and designer. It defines scope, boundaries, expectations and, of course, payment. As a result, writing proposals is a task that cannot be avoided. In our studio, we are always seeking to optimize processes for a more efficient workflow in every business aspect. Therefore, we have sought to develop a proposal writing process that is more streamlined. Although we may continue to iterate on this process as time goes on, we have arrived at a solution using Git, Markdown and CSS that works very well for our small studio.</p><h3>Where We Started</h3><p>When I first began writing project proposals, the studio was mainly focused on providing print design and illustration services. Indesign was the obvious tool to create fantastic looking documents that were on-brand. Although it is poor practice, I often did all of my writing and editing in the application as well.</p><p>Later on, it became beneficial to have a second set of eyes review each proposal. At this time, Michael had begun working with me on web projects and had zero familiarity with Indesign. We were both already using <a href="http://daringfireball.net/projects/markdown/syntax">Markdown</a> for taking notes, so it seemed like the obvious transition was to also use this for the drafting phase. We would take turns editing the Markdown file. Then, I would transfer all of the content block by block into the Indesign document. Although the Markdown syntax clearly delineated the different elements, this was still an arduous task.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/480/0*6_PE8Uy-HD7fqyHv.gif" /></figure><p>We also tried out <a href="https://www.bidsketch.com/">Bidsketch</a>, <a href="http://www.quoteroller.com/">Quote Roller</a> and several other web applications designed at solving the proposal creation issue. While these are all fine pieces of software that provided some nice features, none of them really seemed to fit our needs. The editing process was still sluggish since content was separated into different admin sections and often the WYSIWYG editors caused more problems than they were worth. Every time we would abandon one of these tools, we would return to our Indesign process.</p><h3>Our Current Process with Git, Markdown &amp; CSS</h3><p>Approximately one year ago, we were approached by a number of prospective clients that required a fair amount of proposals to be delivered within a short amount of time. It was at this time that we finally decided we had to find a better process. We were already writing and editing our proposals in Markdown, so it only made sense that we should utilize the strengths of the syntax.</p><p>Since we were already using Git for collaborating on website and software projects, using it for documents seemed like a sensible choice for this new process. Today, I begin by creating a draft of the proposal using Markdown — I prefer to use <a href="http://writer.pro/">IA Writer Pro</a> for this and Michael prefers <a href="https://atom.io/">Atom</a> — and commit it to a private <a href="https://github.com/">Github</a> repository. We then have a <a href="https://slack.com/r/024l00bf-02533q4k">Slack</a> notification set for any updates to this particular repo. Michael can then pull the document and provide any edits that he sees fit. We are able to continue this process until we have solidified the proposed solution.</p><p>Once the editing phase is completed, we use <a href="http://marked2app.com/">Marked 2</a> to create a final document. One of Marked’s key features is the ability to style your content with a custom CSS style sheet. We slightly modified the <a href="https://gist.github.com/jamesdlacroix/d574d925c157114c2d7c">base stylesheet</a> that came with the software to fit our brand’s proposal style. Additionally, with a snippet of HTML, we are able to create a cover page for each document that displays our logo using an SVG.</p><pre>&lt;div class=&quot;cover&quot;&gt; &lt;div class=&quot;cover-logo&quot;&gt; &lt;img src=&quot;../assets/images/logo.svg&quot; alt=&quot;LaCroix Design Co.&quot; /&gt; &lt;/div&gt; # Project Name ### Client Company Name ##### Prepared For: Client Name *13 March, 2015* &lt;/div&gt;</pre><p>Marked offers a few key features that allow us to dynamically create some elements of the proposal. For example, a table of contents can be inserted anywhere in the document using the <a href="http://marked2app.com/help/Special_Syntax.html">software’s special syntax</a>.</p><pre>&lt;!--TOC--&gt;</pre><p>The same also applies to page breaks.</p><pre>&lt;!--BREAK--&gt;</pre><p>However, we are primarily automating page breaks through the apps settings by adding page breaks before every h1 and h2 element. Through the settings, we are a adding dynamically created headers and footers as well.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*clrZ-MslccYcNOEh.jpg" /></figure><p>Once we are ready to send over the proposal, we output it using the paginated PDF feature and quite often deliver it to the client using <a href="https://www.hellosign.com/?ref=92f9561f&amp;s=S">HelloSign</a>. This allows them to digitally sign the delivered proposal with ease.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*3kcOBf8TC_xYEMhJ.jpg" /></figure><p>I have put together an example proposal using <a href="http://www.monocleipsum.com/">Monocle Ipsum</a> and <a href="http://www.docracy.com/2822/standard-agreement-for-design-services-interactive-web-works-exclusive-license-no-modification">AIGA’s Standard Agreement for Design Services</a>. The files are available via the following links:</p><ul><li><a href="https://gist.github.com/jamesdlacroix/5a99eec3d11a5c745504">Markdown Proposal</a></li><li><a href="http://cloud.lacroixdesign.net/2I2H2h3h2e17">Example PDF</a></li><li><a href="http://cloud.lacroixdesign.net/3k3h1n023E28">Logo SVG</a></li><li><a href="https://gist.github.com/jamesdlacroix/d574d925c157114c2d7c">Marked Stylesheet</a></li></ul><h3>Benefits</h3><p>The main benefit of this workflow has been timed saved. We are now able to go straight from the editing process into a final proposal, and no longer have to copy and paste content into an Indesign file. Furthermore, many of our proposals are often read online and include links pointing toward recommended services. We are able to utilize the Markdown syntax to generate these links, which is far easier than applying them using Indesign’s interactive hyperlinks panel.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/480/0*obY8QXE-Ger9MEhg.gif" /></figure><p>Adding visual elements to the proposal also became a lot easier. With Markdown, we are able to quickly add in figures with captions to help explain the solution or provide context to the scope of the project. As you will see in the example, we are creating tables in markdown for the project timeline. Timeline tables provide a great visual reference for our potential clients. Creating tables like these in design software would be much more time consuming, whereas our current solution allows for easy editing and implementation.</p><h3>Future Enhancements</h3><p>As with nearly everything we work on, we are far from finished and are always looking to further iterate our solutions. We are eventually looking at breaking the reusable pieces of our proposals out into partials so that they can easily be inserted into a document. This would include basic contract definitions, intellectual property provisions, interactive provisions and basic elements such as a signature form.</p><p>Marked has a special syntax for <a href="http://marked2app.com/help/Multi-File_Documents.html">multi-file documents</a> which would allow us to begin testing this process out. We have also contemplated creating a local build tool that would provide more customization for this process. A major advantage of creating the reusable components is that we could make changes and have it automatically applied to all future proposals.</p><p>Finally, our initial stylesheet relied heavily on Marked’s base CSS. In the future, I’m certain that we will look into further customizing and expanding the styles to create better presentations for our clients.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/480/0*8BDwRzkpqw3T_s56.gif" /></figure><p>Let us know if you have found any ways to streamline your proposal writing process and, as always, contact us if you have any questions about ours.</p><p><em>Originally published on March 13, 2015</em> <em>at </em><a href="http://www.lacroixdesign.net/blog/streamlining-our-proposal-writing-process/"><em>www.lacroixdesign.net</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=fad7542ded10" width="1" height="1" alt=""><hr><p><a href="https://medium.com/lacroix-design-co/streamlining-our-proposal-writing-process-fad7542ded10">Streamlining Our Proposal Writing Process</a> was originally published in <a href="https://medium.com/lacroix-design-co">LaCroix Design Co.</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>