<?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 Barrett Johnson on Medium]]></title>
        <description><![CDATA[Stories by Barrett Johnson on Medium]]></description>
        <link>https://medium.com/@brjohnson?source=rss-1365e5bd85de------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*3dKPdJSstOyXt7eaNGVOng.png</url>
            <title>Stories by Barrett Johnson on Medium</title>
            <link>https://medium.com/@brjohnson?source=rss-1365e5bd85de------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 10:58:04 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@brjohnson/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[Redesigning Webflow.com, part 2]]></title>
            <link>https://medium.com/webflow-design/redesigning-webflow-dot-com-part-2-9f655b38c95b?source=rss-1365e5bd85de------2</link>
            <guid isPermaLink="false">https://medium.com/p/9f655b38c95b</guid>
            <category><![CDATA[webflow]]></category>
            <category><![CDATA[web-design]]></category>
            <category><![CDATA[redesign]]></category>
            <category><![CDATA[marketing]]></category>
            <category><![CDATA[design]]></category>
            <dc:creator><![CDATA[Barrett Johnson]]></dc:creator>
            <pubDate>Wed, 18 Jan 2017 22:05:32 GMT</pubDate>
            <atom:updated>2017-01-26T22:25:55.220Z</atom:updated>
            <content:encoded><![CDATA[<h3>Part 2: Content design and visual direction</h3><h4>Redesigning Webflow.com</h4><p><em>Co-authored by Barrett Johnson and </em><a href="https://medium.com/@ryryjmo"><em>Ryan Morrison</em></a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*MkQMWDwBZwTuxD5YyHl4Yw.png" /></figure><p>Last week, we looked at <a href="https://medium.com/webflow-design/redesigning-webflow-dot-com-part-1-c59a0cef01e#.ittbzmblu">why we decided to redesign Webflow.com</a>, how we approached it, and discussed our goals for the redesign.</p><p>This time, we’ll take a closer look at the actual work of designing the site.</p><p>As we outlined at the end of last post, we’ll discuss how marketing and design worked together on the videos, content, and design of the site before taking the final step and building everything in Webflow. Next week, Ryan will focus on <a href="https://medium.com/webflow-design/redesigning-webflow-dot-com-part-3-30940823d726#.oidmhhgis">how he approached building the site in Webflow</a> and what he learned along the way.</p><h3>Phase 1: Recording the product videos</h3><p>Because we knew that the product videos on the homepage would play a key role in “selling” Webflow, and that they would be among the more labor-intensive aspects of the redesign, we decided to work on these first.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FUVxG3ZDifqc%3Ffeature%3Doembed&amp;url=http%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DUVxG3ZDifqc&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FUVxG3ZDifqc%2Fhqdefault.jpg&amp;key=d04bfffea46d4aeda930ec88cc64b87c&amp;type=text%2Fhtml&amp;schema=youtube" width="640" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/bba49cbfd063badccc9b40362b3ba26b/href">https://medium.com/media/bba49cbfd063badccc9b40362b3ba26b/href</a></iframe><p>Once we had the videos in a presentable place, we could then work on filling out the copy and the layout alongside them, at which point we could present our first pass at the homepage redesign to the larger team for feedback and first impressions.</p><p>Once we had the homepage design far enough along, we’d expand on the points it introduced within the more detailed <a href="https://webflow.com/designer">Designer</a>, <a href="https://webflow.com/cms">CMS</a>, and <a href="http://webflow.com/hosting">Hosting</a> pages.</p><p>But first, we had to answer a question: what should we feature in the videos?</p><p>This question had a couple parts to it. The obvious first half was: What <em>features or aspects of Webflow</em> do we want to highlight in the videos? The second part was: What exactly are we going to be <em>building</em> in the video?</p><p>We knew the videos needed to illustrate the core features of Webflow — the things that make our product uniquely powerful. Among others, we considered these to be:</p><ul><li><strong>The CSS and styling controls in the Designer</strong>, which provides near-complete control over layout and styling in a completely visual interface</li><li><strong>The Webflow CMS</strong>, which lets designers define their own content structure and display it via whatever layout and structure they have in mind</li><li><strong>Our interactions and animations toolset</strong>, which give designers a completely visual way to bring CSS and Javascript style animations to their designs</li></ul><p>A theme that kept cropping up in the team’s initial discussions was how expressive designers can be with Webflow — that “if you can design it, you can build it with Webflow” really is the heart of the matter.</p><p>So, we decided the videos should visually express the precision, power, and expressiveness that Webflow offers designers.</p><p>The second part of the initial question — “What are we going to be <em>building</em> in the video?” — was one of the more fun parts of the process: now we had to “invent” a few fake websites to serve as example projects in the videos themselves.</p><p>In all, we created three dummy sites before settling on those you see on our current site.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*BaR5dQpNe89okUik." /><figcaption><em>A “fake” music blog we built to show off the flexibility of the CMS.</em></figcaption></figure><p>Once Ryan designed and built the fake sites, I went in and used <a href="http://www.telestream.net/screenflow/overview.htm">ScreenFlow</a> to record myself working in the Designer. I then edited these for presentation on the site, splicing clips, speeding some parts up, adding freeze frames where necessary, and so on.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*ibfUMH7y02n54Url." /><figcaption><em>We used </em><a href="http://www.telestream.net/screenflow/overview.htm"><em>ScreenFlow</em></a><em> to record and edit the videos.</em></figcaption></figure><p>In all, we cycled through 8 to 10 versions of each of the five videos featured on the site. Each version varied in terms of what we were building, how we were building it, and how the timing and clip splicing played out.</p><p>Once we had versions that we felt were strong enough to present to our larger team, we exported the videos as MP4s at 1440x900px, using <a href="https://sidbala.com/h-264-is-magic/">H.264 encoding</a> at 1,200 kbits/sec to save space. In the end, the videos ranged in file size from 2.5 to 3.5 MB — a compression result that, given the quality of the videos, we were happy with.</p><h3>Phase 2a: Content structure and copywriting</h3><p>Once we had (nearly) final versions of the videos recorded, I (Barrett) threw screenshots of them into a Sketch file and made a first pass at the copywriting and content structure.</p><p>My goal was to create a simple wireframe of the content and layout I had in mind, which I could then hand off to Ryan for him to polish, using the new visual direction that he was developing in parallel (more on that below).</p><h4>Why I didn’t start copywriting in Google Docs</h4><p>From the beginning, we knew this redesign was as much about <em>what</em> we were saying as <em>how</em> we were presenting it visually. So, when I sat down to wireframe the homepage, I realized that, for me, writing the copy in an isolated Google Doc would divorce the content from the visual story we were telling alongside it.</p><p>At the same time, the tools available were changing before our very eyes. The downside of copywriting in Sketch — when compared to something like Google Docs, Notion, Dropbox Paper, or the many other collaborative writing tools available — is the lack of native commenting, and for many, InVision bridges this gap.</p><p>With InVision, you can upload static mocks and comments on design, content, functionality — whatever. And in the earlier stages of the process, we used InVision to do just that.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4UTs0xY-nJ21jnncH6Og4Q.png" /><figcaption>A screenshot from one of our earlier stage InVision projects.</figcaption></figure><p>But as we moved through the redesign process, we saw Figma launch its real-time collaboration feature in early October. This interested us, but it was the ability to directly comment on artboards that sold us.</p><p>For us, this unified the process of refining copy and design in parallel, since you can instantly make changes in response to comments, and there was no disconnect between the annotation and the corrections, as there is with InVision. Also helpful was the easy Sketch file import feature Figma offered.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*vFjZMkGvVAfkKOnD." /><figcaption><em>Figma’s live annotation tools streamlined the copy editing and design refinement process, and let us comment on and compare versions side by side.</em></figcaption></figure><p>While I worked on the content, copywriting, and structure, Ryan worked on charting out a new visual and creative direction for our site, which I’ll let him get into below.</p><h3>Phase 2b: Charting a new design direction</h3><p>While Barrett worked on copywriting and content structure, I (Ryan) started exploring a new visual language that would help tell the story of what Webflow is now, and where we’re going. In short, this meant devising a visual style and iconography that reflected how Webflow had evolved technically since the last design, as well as how we see it evolving in the future.</p><h4>Picking the right fonts</h4><p>Type offers designers a powerful tool to shape the feeling of a design. We were using Circular and Avenir in our old designs, and although I love both of those, the roundness of Circular didn’t have the technical and professional vibe I was aiming for.</p><p>First, I searched far and wide for typeface candidates, and reached out to both my fellow designers at Webflow and my designer buddies, collecting all of my favorites. After many many iterations of possible type combinations and tweaks, I landed on a combination of Akkurat and Graphik with a little dash of Roboto Mono here and there.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*itzQwXFhbOW5snyT7ZzwWg.png" /><figcaption>A look at the move from Circular and Avenir to Akkurat and Graphik.</figcaption></figure><p>After I locked in my typeface choices, I took some time to freshen up my knowledge of <a href="https://spec.fm/specifics/type-scale">best practices</a>, spacing recommendations, and <a href="http://type-scale.com/">type scales</a>. I spent about a day of tweaking the sizes, weights, line heights, letter spacing, and margins to achieve the desired levels of balance and contrast between all my headings, paragraphs, and other standard web type styles.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/952/1*SP9Apk8BRJYvB3JwhC854Q.gif" /><figcaption>The immediate visual feedback while making edits to font family, size, weight, line height, and letter spacing in Webflow made iterating on fonts super easy.</figcaption></figure><p>I learned along the way that the set of fonts I had defined for our website—though great in a more visual-centric context—was pretty awful for long form reading situations like on our blog. In Webflow, I gotta say, this was really easy to fix. All I had to do to was edit how some of the fonts within rich text elements were styled, such as adding some extra vertical breathing room, and making the headlines smaller with more contrast between the H1’s, H2’s, paragraph’s etc.</p><h4>Choosing a color scheme</h4><p>When it came to colors, I wanted to use a new palette with a lot more blacks, whites, and neutrals, with pops of bolder colors that would make our site stand out and look sharp. As I explored colors, I didn’t just throw colors onto arbitrary squares and compare them side by side. Instead, I tried different color schemes on a quick sample web page that I built in Webflow to see everything in context.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*FKYQghEw8apgXhHiJBVq4Q.png" /><figcaption>Some exploratory sample pages we built to visualize different color scheme options.</figcaption></figure><p>In the end, I came up with a system where each of the main pages features a dominant accent color that contrasts as well as compliments the sharp blacks and whites throughout. This system allows for consistency throughout the site, yet allows each page to be clearly branded as its own.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*iVNo5RzY8mjTnZ8ALxYGqA.png" /><figcaption>New website, new colors.</figcaption></figure><h4>The role of illustration</h4><p>Over the years, I’ve spent many many hours on illustration and icon work, which has given me a lot of time to think about the role that illustrations should play in design. Above all, I believe every illustration and icon should serve a functional role, though I also know that they have at least as much emotion-evoking power as color and type.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0r2L6mian0vJsNzD1hDo-A.png" /><figcaption>A selection of the new icons, which aim to balance meaning with visual creativity.</figcaption></figure><p>As you’ll see in the icons on the site, each is designed to support the copy by adding information — whether it’s literal or abstracting the point — so that it can be more easily understood at a glance. Though I put function first, it was important to me that the illustrations and icons I made were not only interesting and fresh, but also unique to Webflow.</p><p>(For more on this, Meg Robichaud from Shopify does a great job exploring the duality of the functional and emotional role that icons can play in marketing in her article <a href="https://medium.com/shopify-ux/product-vs-marketing-illustration-7ac474dfe2ed#.ttdr3ptxw">Product Vs. Marketing Illustration</a>.)</p><h3>Phase 3: Presentation, feedback, and review cycles</h3><h4>Marketing and design collaboration</h4><p>As our design direction and content collaboration advanced, the two of us went back and forth in Figma quite a bit, with the marketing side refining what we say, in what order, and adding and subtracting pieces as we moved along; and the design side tightening the visual presentation, type hierarchy, and creating a set of components and styles that we could use across the site.</p><p>We also needed to make sure that the four pages communicated well together, and that they had a unified visual style that would be immediately apparent as visitors clicked around and explored our product.</p><p>Once we had everything in a presentable state, we went to the rest of the team for buy-in and feedback.</p><h4>Getting feedback and iterating on design and content</h4><p>Before we could start building the site in Webflow, we needed to present our proposed pages to the larger team, including our content lead, some members of our support team, and the three founders.</p><p>We knew we’d still be able to make more copy edits and design decisions<em> as we built it in Webflow</em>, but we needed buy-in on content, structure, and design direction from the team before moving forward with the build.</p><p>As we discussed in Phase 2a, InVision and Figma played key roles in helping us work out some of the more nitty-gritty details of copy and small design questions. But we also made a point of having regular meetings to encourage discussion as questions came up.</p><p>To be fair, asynchronous tools and communication modes were critical to helping us move this along — especially with almost a third of our team being remote — but getting everyone in the same (proverbial) room and having those discussions live remained an important part of our design review process.</p><h3>Phase 4: Redesigning Webflow.com in Webflow</h3><p>Next week, we’ll take a look at <a href="https://medium.com/webflow-design/redesigning-webflow-dot-com-part-3-30940823d726#.oidmhhgis">how Ryan approached the task of building out the website in Webflow</a>. Along the way, he’ll discuss building a component system to lay out initial styles and elements, deciding on class-naming conventions, and using the previous version of the marketing site as a starting point.</p><p><em>To stay up-to-date with the Webflow design team, follow us on </em><a href="https://medium.com/webflow-design"><em>Medium</em></a><em>, </em><a href="https://dribbble.com/webflow"><em>Dribbble</em></a><em>, and </em><a href="https://www.instagram.com/webflowapp"><em>Instagram</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9f655b38c95b" width="1" height="1" alt=""><hr><p><a href="https://medium.com/webflow-design/redesigning-webflow-dot-com-part-2-9f655b38c95b">Redesigning Webflow.com, part 2</a> was originally published in <a href="https://medium.com/webflow-design">Webflow Design</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Redesigning Webflow.com, part 1]]></title>
            <link>https://medium.com/webflow-design/redesigning-webflow-dot-com-part-1-c59a0cef01e?source=rss-1365e5bd85de------2</link>
            <guid isPermaLink="false">https://medium.com/p/c59a0cef01e</guid>
            <category><![CDATA[design]]></category>
            <category><![CDATA[redesign]]></category>
            <category><![CDATA[marketing]]></category>
            <category><![CDATA[webflow]]></category>
            <category><![CDATA[web-design]]></category>
            <dc:creator><![CDATA[Barrett Johnson]]></dc:creator>
            <pubDate>Thu, 12 Jan 2017 00:51:38 GMT</pubDate>
            <atom:updated>2017-01-26T22:25:27.983Z</atom:updated>
            <content:encoded><![CDATA[<h3>Part 1: Why redesign?</h3><h4>Redesigning Webflow.com</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9z2wm0buXOiWmRZrtcR-1w.png" /></figure><p><em>This is part 1 of a three part series. Read </em><a href="https://medium.com/webflow-design/redesigning-webflow-dot-com-part-2-9f655b38c95b#.kwr28oksw"><em>part 2</em></a><em> and </em><a href="https://medium.com/webflow-design/redesigning-webflow-dot-com-part-3-30940823d726#.oidmhhgis"><em>part 3</em></a><em>.</em></p><p>At the end of December 2016, the marketing and design teams here at <a href="https://webflow.com/">Webflow</a> wrapped up a three-month redesign of our main website. And, yes: we built it all in Webflow 😎. This is the first of three posts about what our goals were, how we made it happen, and what challenges we faced along the way.</p><p>As <em>very</em> active Webflow users, we thought it’d be interesting to share how we approached this project, including our perspectives on planning, goals, workflow, tools, and processes.</p><p>Then, as we discuss the last phase of our redesign — actually building out the new site in Webflow — we’ll look at <a href="https://medium.com/webflow-design/redesigning-webflow-dot-com-part-3-30940823d726#.oidmhhgis">how we approached building a site of our scale in Webflow</a>, techniques we used to make the process flow, and where we saw room for improvement in our own product.</p><h3>Part 1: Why redesign?</h3><p>The first step in our redesign was deciding <em>what</em> we wanted to say as a company, <em>why</em> we needed to say it, and <em>how</em> we wanted to present that message.</p><p>What was the goal of the redesign? Why did we want to invest the time and energy required to redo our website? What did we want to improve?</p><p>These were questions we’d all been thinking about for a long time (as designers and marketers, we<em> all</em> think about these things almost <em>all</em> the time), so when we gathered the team together to discuss redesigning the website, there was <em>a lot</em> to sort out.</p><p>For one, our product had evolved substantially since the last website redesign in late 2015. Since then, we’d introduced the CMS, expanded the CSS properties available in Webflow (including <a href="http://flexbox.webflow.com/">flexbox</a> in April 2016, and <a href="https://webflow.com/blog/new-feature-css-filters">CSS filters</a> in May), started work on a <a href="http://developers.webflow.com/">new CMS API</a>, started a <a href="https://webflow.com/feature/interactions-v2">revamp</a> of our interactions and animations toolset, and developed a new set of hosting features.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*YaQZCRkHI-DQ3RHS." /><figcaption><em>New features and updates to Webflow since our last redesign in 2015.</em></figcaption></figure><p>At the same time, our own thinking about the product had begun to shift as we talked with customers, observed and joined discussions in the Webflow community, and noticed the enthusiasm that more technical people began to show for our product. Considering all this, we knew there were things we could improve.</p><h3>Goals of the redesign</h3><p>We had an extended series of discussions before doing any actual design work, and although these discussions carried on <em>throughout</em> the redesign, we started by agreeing on a core set of principles for what the new site should do:</p><p><strong>1) Bring more focus to the UI and product.</strong> Our then-current site abstracted the core product to focus on <em>what you could do with it</em> — to the point where people weren’t understanding <em>how</em> Webflow actually works.</p><p>From the conversations we had with both current and non-Webflow users, we confirmed our suspicions that most designers want to <em>see</em> a product in action when they visit the website, and our old site simply didn’t do this clearly enough.</p><p><strong>2) Differentiate us from consumer WYSIWYGs.</strong> We wanted to move away from — if not directly contradict — the misleading association we’ve had with consumer WYSIWYGs like Squarespace, Wix, Weebly, etc., and make it clear that Webflow is a modern, professional, and technical tool.</p><p>This serves two purposes: one, it better sets expectations for site visitors, so they know what they’re getting into with Webflow, and, two, improves the quality of leads coming through the site, as they’re better prepared for some of the more technical aspects of Webflow.</p><p><strong>3) Embrace the technical.</strong> On a similar note, while discussing our product, we wanted to cozy up more to the technical language of HTML, CSS, and JavaScript, since many of our most enthusiastic customers are already familiar and comfortable with this type of language.</p><p><strong>4) Create a more distinctive visual language.</strong> To go along with our efforts to give Webflow more professional, technical spin, we wanted to introduce a new, sleeker visual language that would support that messaging.</p><p>At the same time, we wanted our new site to feature more visual creativity, using illustrations to help communicate some of the more complex aspects of our product.</p><p><strong>5) Let our customers speak for us.</strong> We wanted to do a better job surfacing quotes and stories from our more recent, higher-profile customers in the design world.</p><p>We also wanted to sync the release of our new site with the launch of a revised pricing structure (and, of course, a new pricing page) and the release of several big features, including: SSL for all hosted sites, <a href="https://webflow.com/blog/new-feature-per-page-password-protection">per-page password protection</a>, and the public release of our <a href="http://developers.webflow.com/">CMS API</a>.</p><p>All of these components of last month’s release warrant their own posts, and in due time, they will. But for now, we’ll focus on the redesign of our core site, which included: the <a href="https://webflow.com/">home page</a>, the <a href="https://webflow.com/designer">Designer page</a>, the <a href="https://webflow.com/cms">CMS page</a>, and a new page about <a href="https://webflow.com/hosting">Webflow Hosting</a>.</p><h3>Finding inspiration</h3><p>As we considered the goals of the redesign, the stylistic direction we wanted to take, and the visual elements we wanted to emphasize on the new site, we looked to a number of companies that we felt were doing a good job “telling their story” on their website.</p><p>Here are some of the standouts:</p><h4>Framer</h4><p>Framer was one of the first sites we looked at that embraced the direction we were hoping to take with our new website. By scrolling through their website, you can quickly see what working with their tool <em>feels</em> like, and they support these videos with thoughtful copy that expands upon the ideas and features hinted at in their visuals.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*y8jm0PO9KiSmD6NF7Hq17g.gif" /><figcaption>Framer’s product videos were an early source of inspiration during the redesign.</figcaption></figure><h4>Sketch</h4><p>Sketch does a good job educating their visitors about the tool’s features by showing them in context. This was a theme we noticed across many design-tool websites: designers want to <em>see</em> the tool before they try it.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*L_a6T9SH6p1gjAVf." /><figcaption>Sketch does a good job featuring their product in context — a common thread we noticed across design tool websites.</figcaption></figure><h4>Intercom</h4><p>Intercom counterbalances the UI-heavy examples of Sketch and Framer with their playful and engaging illustrations, which inspired our design team to create our own visual language and iconography throughout the site. Of course, these illustrations don’t replace product shots entirely — their deeper product pages also feature clear, informative UI videos.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*lhj2f6Xo3IaGrt8t." /><figcaption>Intercom balanced playful illustrations with informative product videos and screenshots.</figcaption></figure><h3>Doing the work</h3><p>After interviewing users, doing our own research, and coming to consensus internally, the next step was scoping out what work needed to be done, and by whom. We broke the work down into four categories:</p><h4>1. Recording product videos</h4><p>We knew we wanted the new site to feature HTML5 videos of Webflow in action. We knew these videos needed to be visually appealing, but more importantly, they needed to communicate the Webflow’s features and flexibility.</p><p><strong>Owner</strong>: marketing, with support from design</p><h4>2. Content, copywriting, and structure</h4><p>We needed to support the visual story that these videos communicated with the written word. This encompassed not only what we wanted to say, and in what order, but also how we wanted to say it, what tone we would adopt, and what language we’d use to describe our product.</p><p><strong>Owner</strong>: marketing, with indirect support from our community.</p><h4>3. Brand and visual language work</h4><p>With the new website, we had a chance to reconsider our visual language and style, which meant new iconography and illustration styles, a new font set, and a fresh color scheme.</p><p><strong>Owner</strong>: design.</p><h4>4. Building the site</h4><p>Someone needed to build the site in Webflow, obviously.</p><p><strong>Owner</strong>: design, with support from marketing.</p><p>Next week, in <a href="https://medium.com/webflow-design/redesigning-webflow-dot-com-part-2-9f655b38c95b#.dmj45rwxp">part two of this series</a>, we’ll look at how we tackled this work, the tools we used along the way, and how we communicated as the design and content of the new website evolved.</p><p>Finally, in <a href="https://medium.com/webflow-design/redesigning-webflow-dot-com-part-3-30940823d726#.oidmhhgis">part three</a>, we’ll take a closer look at how we built the site in Webflow, discussing the design and workflow strategies we used while building the site, how we collaborated throughout the process, and where we saw room for improvement in our own product.</p><p><em>To stay up-to-date with the Webflow design team, follow us on </em><a href="https://medium.com/webflow-design"><em>Medium</em></a><em>, </em><a href="https://dribbble.com/webflow"><em>Dribbble</em></a><em>, and </em><a href="https://www.instagram.com/webflowapp"><em>Instagram</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c59a0cef01e" width="1" height="1" alt=""><hr><p><a href="https://medium.com/webflow-design/redesigning-webflow-dot-com-part-1-c59a0cef01e">Redesigning Webflow.com, part 1</a> was originally published in <a href="https://medium.com/webflow-design">Webflow Design</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What My History Degree Taught Me]]></title>
            <link>https://medium.com/@brjohnson/what-my-history-degree-taught-me-f0916c87dd2a?source=rss-1365e5bd85de------2</link>
            <guid isPermaLink="false">https://medium.com/p/f0916c87dd2a</guid>
            <category><![CDATA[history]]></category>
            <category><![CDATA[undergraduate]]></category>
            <category><![CDATA[graduation]]></category>
            <dc:creator><![CDATA[Barrett Johnson]]></dc:creator>
            <pubDate>Fri, 20 May 2016 22:45:04 GMT</pubDate>
            <atom:updated>2016-07-22T16:30:27.892Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*EzgbuoaU8NOfHQZfdZOnMQ.jpeg" /><figcaption>The University of Virginia in the late 1800&#39;s—my alma mater and an institution that <a href="http://uvamagazine.org/articles/history_as_lesson">continues to grapple</a> with its own history.</figcaption></figure><blockquote>“The things taught in schools and colleges are not an education, but the means to an education.”</blockquote><blockquote>the <a href="http://www.perfectidius.com/Volume_2%20_1825-1832.pdf">journal</a> of Ralph Waldo Emerson, July 1831</blockquote><p>“What are you going to <em>do</em> with that?”</p><p>It’s a question so familiar to liberal arts majors that by now, it’s all but a cliché — so cliché, in fact, that it was hard to even allow myself to start this essay with it. But still, the question keeps cropping up, and two years after graduating, I’ve begun to understand how I wish I answered that question during my final months in college.</p><p>There are, of course, some obvious things you learn as a history major: how to write and communicate clearly, how to analyze complex ideas and texts, how to think critically — but let me stop there. Enumerating and expounding these familiar “liberal arts skills” is not the point of this essay. Those skills are the “practical” things my history degree taught me, but what has given me the most enduring satisfaction and value as I think about my education is far less obvious.</p><p>In one my last lectures in college, I felt a profound mixture of emotions: nostalgia for the years and semesters that had passed, an uneasiness about the future that lay beyond graduation, pride in the academic path I had chosen, and yet a lingering sadness as I felt the last grains of sand draining from the metaphorical hourglass that was my college career…</p><p>The professor opened class with a simple question: “What does history teach us?”</p><p>After several moments of silence, a few hands began to rise as some of the students pieced together answers that they hoped would be profound enough to legitimize their (and everybody else in the rooms’) decision to study something decidedly “impractical” in college.</p><p>“If we don’t study history, we are doomed to repeat it?” one student offered halfheartedly, wavering near the end because he knew that at best, he was merely reciting a tired platitude that we’d all heard before. The professor didn’t need to say more than, “What else?” to let everyone know that was not enough.</p><p>Several more moments of silence ensued. The pressure of the question weighed heavily on all our minds, since it was certainly a question we’d been forced to defend to our peers, relatives, and countless others throughout the past few years. (“What are you going to <em>do</em> with that?”)</p><p>“History teaches us why and how the world came to be the way it is,” another student offered.</p><p>“An invaluable thing to understand,” the professor responded, “but not what I am looking for. Think deeper. There is more behind that — why do we want to understand how the world came to be in the first place?”</p><p>More silence.</p><p>“History removes illusions from the past,” another student offered. “It teaches us not to accept traditional explanations as fact, instead forcing us to decipher the intricacies involved with human affairs — or really anything that has a disputed past.”</p><p>“Better,” the professor encouraged. “Some vague language, but still, good. What else?”</p><p>“Ideas,” another student cut in. “When we study history, we are exposed to ideas, cultural orientations, and traditions that confront our own. In studying them, we are challenged to reconsider our own points of view.”</p><p>“Very good. More of this. What else?”</p><p>More and more hands were popping up. The ice had been broken, and everyone in class was eager to offer their two cents on the matter. Nobody was about to say, “so we can critically analyze spreadsheets,” or, “so that we can write clear emails after graduation.” These lessons were beside the point.</p><p>“Humility,” I offered. “History teaches you about the billions of people who have come before you, the achievements they’ve made, and the hardships they have been forced to overcome. In light of these examples, you are forced to take a step back and reconsider your own life story in the larger context of human history.”</p><p>After several more ideas and a few side conversations, another silence ensued. It was clear that while the professor wanted us to bring forward a wide range of ideas, he was searching for still something we hadn’t proposed. After giving the students a few more guesses, he offered us his final thoughts.</p><p>“You’ve all impressed me today. I think the true answer to ‘what history teaches us’ will vary with each of you, and of course there is not <em>one</em> answer that I am looking for. But there is an important value that, at least for me, I’ve always considered inseparable from the study of history: empathy.</p><p>“History forces you to think beyond yourself. To succeed in history, you need to step outside of your own thoughts, prejudices, and experiences to understand the thoughts, prejudices, and experiences of others. In doing so, I hope you’ve realized that while it may <em>seem</em> like you have very little, if anything, in common with people who grew up in different centuries and and on opposite sides of the globe, there are certain intuitions, desires, and fears that nearly everyone experiences.</p><p>“This might seem obvious to you guys. Perhaps you entered college with that idea already drilled into your consciousness. But my hope is that at least in some way, at least once, studying history made you <em>feel</em> that.</p><p>“Thank you for taking my class this semester. I wish you all the best of luck. Congratulations.”</p><p>As I walked home after class, I tried to process all of the ideas that my professor and fellow students brought forth over the last hour. Which idea impacted<em> me</em> most? What has my education in history taught <em>me</em>? Sure, I might have said “humility” in class, but all the other ideas my peers proposed resonated with me as well.</p><p>I circled back to my professor’s conclusion. Empathy? I thought about it for a second, then realized that when I study history, I am forced<em> </em>to put myself in other people’s’ shoes, and that while many of the big takeaways from history come in the form of overarching summaries of long developing demographic, economic, or cultural trends, at the end of the day, it is impossible to separate the individuals in these stories from the historical forces they took part in.</p><p>To really understand these times, these places, and the trends that shaped them, it became necessary to dive deep and attempt to put myself in the minds of the people who lived, loved, ate, drank, and slept in them. This exercise, repeated over and over again, semester after semester, led me to a much deeper appreciation of the many “intuitions, desires, and fears” that human beings share across time and space.</p><p>At the end of college two years ago, and at the end of the day today, the most valuable things my history major taught me are not what I expected. At first, history fascinated me because there was so much to learn about human civilization. How did the Roman Empire rise and fall? Where did the ideas that prompted the American, French, and other revolutions stem from? How did the American founders espouse their creed of human equality while owning other human beings? Is there <em>any</em> substance to the claim that “America is a Christian nation”?</p><p>These questions, among countless others, are what initially attracted me to history. This is not to say they’ve gone away — I suspect I am stuck with these curiosities for life — but studying these questions, looking for these answers (much like my “critical thinking skills” and my “ability to communicate clearly”) is a <em>means</em>, not an <em>end</em>. And as I’ve realized over the past few years, these <em>means</em> have no value if they are not applied toward <em>ends</em> that I feel are important.</p><p>What I did not fully grasp at the outset of college was just how important my education would be in helping me shape and determine the ends I hope to pursue. In my case, studying history taught me the irreducible value of understanding and connecting with other human beings, which I now consider to be the main <em>end</em> I pursue on a day to day basis. This driving force has furnished me with some of the most important and sustaining passions in my life, namely, the enduring value of my friends and family, the underlying importance of honesty and communication at work, and most recently, the unexpected joy of reading fiction—which I’ve grown to love so much over the past few years because of it’s <a href="http://www.newyorker.com/books/page-turner/vanishing-point">unique ability</a> to establish emotional connections between distant minds. While I wouldn’t say that my history degree is entirely responsible for these values, I do think it has played a significant role in shaping and crystallizing it.</p><p>Today, equipped with the <em>means</em> that my education has given me and confident in the <em>ends</em> I hope to pursue, I could not feel better equipped to move forward in life. Personally and professionally, I am happy to know that a major portion of that confidence stems from the many lessons my history degree taught me.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f0916c87dd2a" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>