<?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 Robin Granqvist on Medium]]></title>
        <description><![CDATA[Stories by Robin Granqvist on Medium]]></description>
        <link>https://medium.com/@shapedbyrobin?source=rss-946e52f2852c------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*rGBA5Ggo8u4eddp6pfqNVA.png</url>
            <title>Stories by Robin Granqvist on Medium</title>
            <link>https://medium.com/@shapedbyrobin?source=rss-946e52f2852c------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 23:11:27 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@shapedbyrobin/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’m Building a Tiny Open Source Webflow Component Library]]></title>
            <link>https://shapedbyrobin.medium.com/im-building-a-tiny-open-source-webflow-component-library-769b92936734?source=rss-946e52f2852c------2</link>
            <guid isPermaLink="false">https://medium.com/p/769b92936734</guid>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[webflow]]></category>
            <category><![CDATA[web-design]]></category>
            <category><![CDATA[webflow-component]]></category>
            <category><![CDATA[webflow-design]]></category>
            <dc:creator><![CDATA[Robin Granqvist]]></dc:creator>
            <pubDate>Sun, 15 Dec 2024 18:48:54 GMT</pubDate>
            <atom:updated>2024-12-15T18:48:54.673Z</atom:updated>
            <content:encoded><![CDATA[<p>So I’ve spent quite a few hours the last couple of weeks building out a (currently quite tiny) open source component library for Webflow.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*x0kNinsuTnIB0PlYQ-uwTA.png" /><figcaption>The component library in question. <a href="https://www.shapedbyrobin.com/components">Check it out</a></figcaption></figure><p>It’s basically just a section of my personal site (made in Webflow) on which I upload a few semi-styled, minimalist, typography focused Webflow components every day that users are able to copy &amp; paste directly into their own Webflow projects without having to sign up or pay any premiums.</p><p>The site is fully static using the Webflow CMS, which is hosting all the data needed for all components. This means that there’s no external databases, servers or applications needed.</p><p>This is a short article going through how I developed the whole thing. Let’s go.</p><h3>Developing the components</h3><p>All components are developed in one large Webflow project. This project contains a super-simple style guide (for now) and a separate page for each component category.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*yK2GZgaq7uV2VigSbTA8kQ.png" /><figcaption>The current component style guide, it’s not pretty</figcaption></figure><p>Each component is then developed as regular, with the exception of using a prefix for all classes, as well as creating unique classes for most element of each component.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*VJrNbokv0X9DrroLsRKaTg.png" /><figcaption>The <a href="https://www.shapedbyrobin.com/components/type/list">List 003 component</a></figcaption></figure><h4>Prefix</h4><p>My <em>SBR</em> (Shaped by Robin) prefix is used for both <em>Classes </em>and <em>Interactions </em>for all components. The prefix is used in order to not interfere with any of the current classes in a users Webflow project.</p><h4>Unique classes</h4><p>I’m using unique classes for each element in each component so that a user can customize a component without having to worry about any of the other components getting messed up.</p><p>This does indeed create a huuge, somewhat unnecessary, stylesheet, but I feel like it’s important to make sure more “beginner-level” developers can use the library properly (which I’m guessing will be the main user base).</p><p>It also decreases the use of multi-layered combo classes and class interference / class duplication when pasting a component into a project.</p><p>There are however some classes that I re-use, such as:</p><ul><li>Button groups</li><li>Icon sizes</li><li>Display headings</li><li>Body paragraphs</li><li>Containers</li></ul><h3>Developing the library itself in Webflow</h3><p>It’s actually quite simple to develop a site like this in Webflow, especially by using the CMS. In this case, I only have two collections:</p><ol><li>Components</li><li>Component categories</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*aaSG3zbuKLDVOc5X3eL2rQ.png" /><figcaption>The <strong>Components</strong> collection</figcaption></figure><p>On my <a href="https://www.shapedbyrobin.com/components">components page</a> I’m listing out all components in a grid with pagination. Each category gets its own template page listing out components of a specific category in the same type of grid.</p><p>Simple.</p><h4>The copy &amp; paste functionality</h4><p>If you look closely at the image above, you can see that there’s a field called <em>TXT</em>. This is a file field in which I’m uploading a <em>TXT file</em> of the component in question.</p><p>If you need help on how to do this, <a href="https://www.flowout.com/blog/create-your-own-component-sharing-app">Flowout has written a great guide</a> on basically everything you need to know:</p><ol><li>Export components from a Webflow project into JSON files</li><li>Upload components</li><li>Create the copy &amp; paste functionality</li></ol><p>The only thing I’m doing different is turning my all JSON files into TXT files, since JSON files aren’t supported by the Webflow CMS. My setup basically goes like this:</p><ol><li>A user clicks on a button to copy a component</li><li>The components’ TXT file is fetched through the Webflow CMS URL of the uploaded file</li><li>The content is converted back to JSON</li><li>The converted JSON content is pushed to the users clipboard</li></ol><p>This makes users able to paste the component into their own Webflow projects seamlessly.</p><h4>Component ID</h4><p>On my component library pages I render a grid of cards, each card having its unique copy button. Every rendered component card also has a Code Embed element, containing all the code needed for a user to copy each component.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LEX_PIxhiJwW659uSfWMhQ.png" /><figcaption>A component card component in my library</figcaption></figure><p>If you take a look at the collection in the image two images above, you might notice a field called <em>Component ID. </em>The <em>Component ID</em> is a string that has to be unique for each component.</p><p>This ID is used to:</p><ol><li>Make variable names in each Code Embed unique</li><li>Give each copy button element a unique ID</li></ol><p>The Code Embed for a component looks like so:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/854/1*iItY8mfYrOHgtG02SRaX9A.png" /><figcaption>The Code Embed for a component</figcaption></figure><p>It’s basically a copy of the <a href="https://www.flowout.com/blog/create-your-own-component-sharing-app">setup code by Flowout</a>, but using the <em>Component ID </em>wherever it’s needed.</p><p>You might also notice that I’m using the URL from my text file field called <em>TXT</em>, turning the URL of it into a string stored in a variable and using it to fetch the component using the fetch API in Javascript. This is slighly different than how Flowout is doing it, but seems to work great.</p><h3>Conclusions</h3><p>Hopefully this guide gave you a few pointers on how you could develop something like this yourself in Webflow.</p><p><a href="https://www.shapedbyrobin.com/components">Feel free to check out the whole library over here</a>, and send in some feedback or component requests through the little “Send Request” button in the dark announcement bar.</p><p>Also feel free to write a comment or <a href="https://www.shapedbyrobin.com/profile">send me an email</a> if you have any questions.</p><p>Bye bye.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=769b92936734" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Logging my Webflow Template Sales using N8N, Airtable and Outlook]]></title>
            <link>https://shapedbyrobin.medium.com/logging-my-webflow-template-sales-using-n8n-airtable-and-outlook-9eb7cc9b14ea?source=rss-946e52f2852c------2</link>
            <guid isPermaLink="false">https://medium.com/p/9eb7cc9b14ea</guid>
            <category><![CDATA[analytics]]></category>
            <category><![CDATA[automation]]></category>
            <category><![CDATA[n8n]]></category>
            <category><![CDATA[airtable]]></category>
            <category><![CDATA[webflow]]></category>
            <dc:creator><![CDATA[Robin Granqvist]]></dc:creator>
            <pubDate>Wed, 30 Oct 2024 19:05:59 GMT</pubDate>
            <atom:updated>2024-10-30T19:05:59.717Z</atom:updated>
            <content:encoded><![CDATA[<p>Over the past year, I’ve been designing Webflow templates, and there’s been one big problem that’s been bugging me: the absence of a dashboard for sales analytics.</p><p>Although a dashboard existed previously, it was discontinued with the transition to Stripe Express earlier this year. While there’s rumors that a new dashboard may be in development, the current Stripe Express setup only provides total monthly sales volume without offering insights into individual template performance — a super-important element for understanding what works.</p><p>So I created one.</p><p>In this guide, I’ll walk through the basics of using n8n in combination with Airtable to track and display sales analytics for individual templates. This approach can also be easily adapted to log other types of data. Let’s gooo.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*GTA3pX6NO9a_he-C-IhtZg.png" /><figcaption>My super-simple n8n workflow</figcaption></figure><h3>The basics</h3><p>The setup looks like this:</p><ol><li>A template sales generate an automated email containing information such as the template’s name, price and date of sale.</li><li>A <a href="https://shapedbyrobin.medium.com/self-hosting-n8n-the-free-zapier-alternative-a00ce91adf06"><em>self-hosted n8n instance</em></a> fetches the new email from my email client (Outlook).</li><li>An <em>Edit fields</em> node parses the email for the templates’s name, price and date.</li><li>The parsed data is sent to an <a href="https://www.airtable.com/"><em>Airtable</em></a> table as a new row.</li><li>A separate table combines all sales for templates by name, showing the total sales for each template.</li></ol><p>Simple, right?</p><p>Well yes, it is. Let go through how to implement this.</p><h3>Self-hosted n8n instance</h3><p>I’ve written a full guide on how you can get going with setting up a free, self-hosted instance of n8n on the cheapest DigitalOcean tier while having it hosted on a subdomain of your choice.</p><p>Go read it here.</p><h3>Outlook rules</h3><p>The first problem I came across was to filter out all template sales emails in my Outlook inbox. Luckily Outlook makes it super easy to automate sending certain emails into a specific folder.</p><p>In my case, I filter by both sender and topic and send them all into a folder called “<em>Webflow Templates</em>” using Outlook rules. Read more about rules in the official documentation <a href="https://support.microsoft.com/en-us/office/set-up-rules-in-outlook-75ab719a-2ce8-49a7-a214-6d62b67cbd41">over here</a>. It’s super easy, I swear.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*k3hhRWDNjYivhGnwgdh-SA.png" /><figcaption>Outlook rules for sales emails</figcaption></figure><h3>Fetching Outlook emails in n8n</h3><p>The second step was to fetch all new sales emails in n8n. This is super-simple to do using the <em>Microsoft Outlook Trigger</em>, triggered once an hour.</p><p>The node does an hourly check if a new email is received in my <em>Webflow Templates</em> Outlook folder. The email also has to contain certain keywords in the topic in order for the node to trigger, very similarly to how the Outlook rule works.</p><p>Please note that you need a Microsoft Azure account, and a few minutes to setup your credentials in order to work with the Outlook trigger. Read more about this in the <a href="https://docs.n8n.io/integrations/builtin/credentials/microsoft/">n8n documentation</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*o_ehFxiDT48UriIO_0SqNw.png" /><figcaption>Outlook trigger node in n8n</figcaption></figure><h3>Parsing the data in n8n</h3><p>Now we need to parse the data from the email we fetched. In my case, all the data I need is in the topic of a sales email, so that’s the one I’m parsing in an <em>Edit Fields</em> node.</p><p>In this node, we need to write some Javascript, and this is a perfect time to utilize ChatGPT to write the snippets for you.</p><p>If you look at the image below, I’m simply parsing out the <em>Name</em> and <em>Price</em> of the template, both from the subject line of the received email.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YhTXLtDXDxyx2eLieAb48Q.png" /><figcaption>Parsing the data in an Edit Fields node in n8n</figcaption></figure><h3>Creating Airtable tables</h3><p>Now we need to setup a table in Airtable. The first table — <em>Sales — </em>has 4 columns:</p><ul><li>Template name (String)</li><li>Price (Currency)</li><li>Date (Date)</li><li>Summary (Linked)</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_L1vOmKVVA7XguisU0x87A.png" /><figcaption>The Sales table in Airtable</figcaption></figure><p>The first three columns are quite self-explanatory. The fourth one however, is a column that links each row with another table — <em>Summary</em>.</p><p>The <em>Summary</em> table has 3 columns:</p><ul><li>Template name (String)</li><li>Sum (Rollup)</li><li>Count (Rollup)</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mLfRRHammeN13lF-ZE8UbQ.png" /><figcaption>The Summary table in Airtable</figcaption></figure><p><em>Sum</em> and <em>Count</em> are <a href="https://support.airtable.com/docs/rollup-field-overview">rollup fields</a>, meaning that they sum up data from another column, in my case both are using the <em>Price</em> column in the <em>Sales</em> table:</p><ul><li>Sum is the total sum of sales per template</li><li>Count is the times a template has been sold</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*btH34VDtGW96lgAd8AllIA.png" /><figcaption>My Sum rollup field setup in Airtable</figcaption></figure><h3>Sending data from n8n to Airtable</h3><p>Okay, so now we have our columns. Let’s send the data fetched from Outlook into Airtable in n8n.</p><p>This is the third n8n node, and it looks like this:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*K_ie6nBOyvoqUxmhARewXA.png" /><figcaption>Airtable node in n8n</figcaption></figure><p>I’m simply sending the variables from the previous nodes as is, except for the fourth one; <em>Summary</em>.</p><p>Summary is the field that links the Sales table together with the Summary table, and it requires an array instead of a string.</p><p>That’s why I’ve wrapped the <em>json.name </em>inside brackets<em>, </em>turning it into<em> [json.name] </em>for the <em>Summary</em> field.</p><p>The last little hickup we want to fix is to turn on <em>Typecast</em> under the node options . This makes sure the <em>Date</em> field is sent in its proper way over to the Airtable table.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Rj7yRw3wQ2ga-q8teop0dA.png" /><figcaption>Turning on the Typecast option in the n8n Airtable node</figcaption></figure><h3>Inserting all old sales into Airtable</h3><p>Now we have a system that inserts all ongoing new template sales into our table. However, we also want to look at historical data of our sales.</p><p>That’s why I’ve created a separate workflow that I’ve ran only once to fetch all previous sales (all template sale related emails from the last year) before starting the previous hourly polling workflow for new sales emails.</p><p>This n8n workflow looks something like this:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Mu_S8TCyJZnnd2uwM9ExDg.png" /><figcaption>Fetching previous sales emails workflow in n8n</figcaption></figure><p>It’s very similar to the previous workflow, however there’s I’m doing a few different things.</p><h4>1 — Fetching all previous emails</h4><p>Instead of the workflow being triggered by newly received emails, it fetches all previous emails in my <em>Webflow Templates</em> forlder in Outlook and inserts them into my Airtable table.</p><p>This is done by selecting the <em>Get Many</em> operation in the Outlook node and hitting the <em>Return All</em> switch. Otherwise it’s identical to the Outlook node in the previous workflow.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*JNtG6PSS91j4pEQcmXanxg.png" /><figcaption>Get Many operation &amp; Return All switch flipped in Outlook node</figcaption></figure><h4>2 — Airtable Create or Update node</h4><p>The <em>Summary</em> table has to be setup before it can be used, and that happens after all emails have been fetched, but before the data is being sent to <em>Airtable</em>.</p><p>Basically what happens here is that the name of each template gets its own row in the <em>Summary</em> table, which later on therefore can be linked together with the rows matching the name in the <em>Sales</em> table.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*41Nd_-SC63vfYu5EfE3Pyw.png" /></figure><h4>3 —Triggered by click</h4><p>Since we only need to run this workflow once at the start, it’s triggered by clicking the <em>Test workflow</em> button instead of when a new email arrives in the Outlook folder.</p><p>This is done by using the <em>When clicking test workflow</em>-node in n8n.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Mu_S8TCyJZnnd2uwM9ExDg.png" /><figcaption>The full workflow</figcaption></figure><p>Please note that Airtable recently added an API call limit on the free tier with a 1000 action limit per month. This means that if you’ve got more than 1000 sales emails, or if you’re running the workflow multiple times, you will hit the API limit and might receive an email like this.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*G6SqKDXD_8wPXax1cfU3UQ.png" /><figcaption>Airtable API call limit email</figcaption></figure><p>Lesson: upgrade your Airtable tier if you’re doing stuff like this. It’s worth it.</p><h3>Conclusions</h3><p>Now we’re finally done and I have nothing more to say. Let me know if you found this article helpful or <a href="https://shapedbyrobin.com/">if you have any questions</a>.</p><p>Feel free to check out my <a href="https://webflow.com/templates/designers/robin-granqvist">Webflow templates on the marketplace</a>, <a href="https://www.instagram.com/shapedbyrobin/">follow me on Instagram</a> or maybe take a look at <a href="https://webflow.com/@robingranqvist">my Webflow profile</a>.</p><p>Byebye.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9eb7cc9b14ea" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Building a Solid Slider Component in Webflow]]></title>
            <link>https://shapedbyrobin.medium.com/building-a-solid-slider-component-in-webflow-a7311ed97181?source=rss-946e52f2852c------2</link>
            <guid isPermaLink="false">https://medium.com/p/a7311ed97181</guid>
            <category><![CDATA[web-design]]></category>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[webflow-design]]></category>
            <category><![CDATA[webflow]]></category>
            <dc:creator><![CDATA[Robin Granqvist]]></dc:creator>
            <pubDate>Wed, 23 Oct 2024 12:44:12 GMT</pubDate>
            <atom:updated>2024-10-23T12:44:12.864Z</atom:updated>
            <content:encoded><![CDATA[<p>Sliders can be an amazing element to share lots of information in a small amount of space on your website.</p><p>However, they can also be quite hard to work with in Webflow. They’re clunky, have strange pre-styled elements to them and refuse to work they way you want half of the time.</p><p>This article is a short guide of building a super-minimal, nice looking slider for testimonials in Webflow. The component is available as a cloneable on my Webflow profile, so feel free to <a href="https://webflow.com/made-in-webflow/website/simple-slider-component">clone it over here</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*X1eep8I69QnerDEbVKfdcg.png" /><figcaption>The testimonial slider component in question</figcaption></figure><h3>Getting started</h3><p>A typical, unstyled native slider in Webflow consists of the following elements:</p><ul><li>The main slider wrapper</li><li>A slider mask</li><li>One or more slides</li><li>Slider arrows</li><li>Slider navigation</li></ul><p>These elements are pre-styled in various ways. For example, the slider arrows are absolute positioned left and right relative to the slider wrapper, the slider navigation is absolute positioned to the bottom, the slider has a background color and so on.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3cSl0wcCv3udcdonyK0LQw.png" /><figcaption>A typical, unstyled native slider in Webflow</figcaption></figure><h3>Styling the slider</h3><p>So let’s start by giving each element its own class. The slider might now look something like this:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*r2ko3rfsFcZVEuShjdKerQ.png" /><figcaption>Giving classes to each slider element</figcaption></figure><p>Notice that I’m sharing classes between:</p><ul><li>Slide Wrapper</li><li>Slider Arrow</li><li>Slider Arrow Icon</li></ul><p>This is a good starting point, since we want to keep all shared elements styled consistently. Later on, we’re able to customize them further using combo classes.</p><p>Also notice that I added a div called <em>Slide</em> inside the <em>Slide Wrapper</em>. This is done since we want to turn each slide into its own component later on, something that’s not possible to do with the <em>Slide Wrapper</em>.</p><h4>Slider</h4><p>I’m simply gonna give my <em>Slider</em> class a set height of 35 REM’s and that’s it.</p><h4>Slide</h4><p>The slide class is gonna get a height of 100% to fill the total height of the slider, as well as a background color and some border radius.</p><h4>Slider Nav</h4><p>I really dislike the Webflow slider navigation, so I’m just gonna hide it all together using display none.</p><h4>Slider Arrow Icon</h4><p>I’m gonna replace both default slider icons with new icons (just images) and giving them a set width of 1 REM.</p><h4>Slider Arrow</h4><p>The slider arrow class now needs to center the icons vertically, so I’m gonna use flex with a vertical &amp; horizontal centering to achieve that.</p><p>After doing all these changes, our slider might now look something like this:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*N5bxge8eTm9Mf85ls6IXTw.png" /><figcaption>The slider after a bit of styling</figcaption></figure><p>Looks good, right?</p><p>Yes it does. And that was really simple. So let’s continue with the slides themselves.</p><h4>Slide</h4><p>Since the content is gonna sit inside the Slide-elements themselves, let’s give them some centered vertical flex with a bit of vertical flex gap.</p><p>Inside the slide, I’m just gonna add some styled text for this example. This might look something like this:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*yYlpe1uKi4eCqnAGP2KW_g.png" /><figcaption>The slide after a bit of styling and a bit of text</figcaption></figure><h3>Turning our slider into a component</h3><p>Now, there are two ways we could turn this slider into a component:</p><ol><li>Turn the whole slider into one single component with all slides pre-created inside</li><li>Turn each slide into a component and have them nested inside the slider component</li></ol><p>Since we want to keep consistent, turning the <em>Slide</em> into a component and having it nested inside the <em>Slider</em> will be the better option. This allows us to customize a single <em>Slide</em> and have every other <em>Slide </em>updated in the same way.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-WSkrafDU5EeAm8inZJ7tA.png" /><figcaption>The slider with a couple Slide components inside</figcaption></figure><p>If you look closely, you can see that I turned the main <em>text</em> into a prop for the <em>Slide</em> component. If the slides would have more elements, I would have turned them into props as well.</p><p>Now let’s turn the whole <em>Slider</em> into its own component.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*d5DQPrcn4-nOHFiOkDQOzQ.png" /><figcaption>The whole Slider is now a component</figcaption></figure><p>Okay, there we go. Now the <em>Slider</em> is a component, and I’m lifting the props of both <em>Slides</em> as props for the <em>Slider</em> component.</p><p>This makes it super easy to customize each <em>Slide</em> without having to navigate through the <em>Slides</em> inside the <em>Slider</em>.</p><h3>Conclusions</h3><p>Hopefully this little guide helped you create some super-cool slider components in Webflow. If you want to clone the example shown above, feel free to clone in through my Webflow profile by <a href="https://webflow.com/made-in-webflow/website/simple-slider-component">clicking here</a>.</p><p>If you have any questions, feel free to write a comment down below or <a href="https://shapedbyrobin.com/">contact me</a>. Also, make sure to check out my <a href="https://webflow.com/templates/designers/robin-granqvist">Webflow templates on the marketplace</a> and follow me on <a href="https://www.instagram.com/shapedbyrobin/">Instagram</a>, I’m posting some cool things over there.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a7311ed97181" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Using Layout Grids in Webflow]]></title>
            <link>https://shapedbyrobin.medium.com/using-layout-grids-in-webflow-87694df4d1b9?source=rss-946e52f2852c------2</link>
            <guid isPermaLink="false">https://medium.com/p/87694df4d1b9</guid>
            <category><![CDATA[grid-layout]]></category>
            <category><![CDATA[webflow-developer]]></category>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[web-design]]></category>
            <category><![CDATA[webflow]]></category>
            <dc:creator><![CDATA[Robin Granqvist]]></dc:creator>
            <pubDate>Wed, 16 Oct 2024 11:19:04 GMT</pubDate>
            <atom:updated>2024-10-16T11:19:04.173Z</atom:updated>
            <content:encoded><![CDATA[<p>Grids are an essential tool for creating layouts that adapt seamlessly across different devices. They also offer a flexible solution for designing more complex or unconventional layouts.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*hUt_3EooIp54TwpI.jpeg" /><figcaption>My portfolio Webflow template — <a href="https://webflow.com/templates/html/kennedy-portfolio-website-template">Kennedy</a></figcaption></figure><p>In Webflow, the <em>Grid element</em> mirrors the functionality of <em>CSS grid</em>, providing a great set of tools to easily build responsive and dynamic grids.</p><p>This article is a short exploration into how you can use grids in Webflow to streamline your design process, especially layouts, saving both time and effort.</p><h3>How Grids work in Webflow</h3><p>The grid element is actually super simple to use. As default, it gives you a normal grid with 2 columns and 2 rows with a 16px gap (read more about the Webflow grid <a href="https://help.webflow.com/hc/en-us/articles/33961365794451-Grid">over here</a>).</p><p>All settings for the grid can be found in the right hand settings panel. Here you can basically change any CSS property, similarly to a <a href="https://css-tricks.com/snippets/css/complete-guide-grid/">“real” CSS grid</a>, only much simpler to use and understand.</p><h3>My layout grid</h3><p>In every project I do, I usually have a single layout grid. This grid usually has 12 columns and 0 rows (all needed rows gets auto-generated) on the desktop breakpoint, giving me everything I need to build cool layouts.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*AfKs4nAh9qsCFkHfJGyKKg.png" /><figcaption>The layout grid in my portfolio template — <a href="https://webflow.com/templates/html/kennedy-portfolio-website-template">Kennedy</a></figcaption></figure><p>If you look at the screenshot above, you can see that my columns all have a Min/Max of <em>0.5 REM</em> to <em>1FR</em>.</p><p>This is done so that all columns can “fit” horizontally inside whatever contains they exists in while taking up at least <em>0.5 REM</em> in width<em>.</em></p><p>The settings for the size of each column can be changed by clicking each individual column in the settings (see image below).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fP1ydLX39wr6tgC1LzkKOw.png" /><figcaption>Changing column width in <a href="https://webflow.com/templates/html/kennedy-portfolio-website-template">Kennedy</a></figcaption></figure><h4>Making the grid responsive</h4><p>If you’ve ever seen other tutorials on using layout grids, having the columns span down on smaller breakpoints is often mentioned.</p><p>This isn’t really needed, since you’re totally able to use a 12-column grid on any breakpoint, but it definitely simplify things.</p><p>For my layout grids, I usually use the following columns:</p><ul><li>12 columns on desktop</li><li>8 columns on tablet</li><li>4 columns on mobile landscape</li><li>4 (or 2) columns on mobile</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5RsaEOzRbHu3YUcEkrNEMQ.png" /><figcaption>8 columns on the tablet breakpoint in <a href="https://webflow.com/templates/html/kennedy-portfolio-website-template">Kennedy</a></figcaption></figure><h4>Changing column amount between breakpoints</h4><p>Changing the amount of default columns between breakpoints is super-simple. Simply select your breakpoint and delete any number of columns in your layout grid class.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*DKlT0iwToTRU9njFs90EtA.png" /><figcaption>4 columns on the mobile breakpoint in <a href="https://webflow.com/templates/html/kennedy-portfolio-website-template">Kennedy</a></figcaption></figure><h4>Keeping grid layouts responsive</h4><p>The easiest way of keeping your grid based elements responsive is to simply drag your elements by the corner and give them the amount of columns that they need (see image below).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*lWuSJMTb95mmsn-9mGnFpQ.png" /><figcaption>Dragging div element to fit 7 columns in <a href="https://webflow.com/templates/html/kennedy-portfolio-website-template">Kennedy</a></figcaption></figure><p>If your layout is more complex with multiple elements inside a single grid for example, you can also give individual elements their column &amp; row positions using the settings to the right in the designer.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*GfN6NZYCsAeCuRKjKL4Gog.png" /><figcaption>Giving a div element 4 columns in a more complex layout grid in <a href="https://webflow.com/templates/html/kennedy-portfolio-website-template">Kennedy</a></figcaption></figure><h4>Giving elements a custom grid column position</h4><p>The cool thing about grids is that you’re able to give any element their own custom position, making it super easy to build more complex layouts.</p><p>For example, in the image below, I wanted to place my element between column 4 and 10.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*bSLn5omJMBbi8oKk_m-8Cw.png" /><figcaption>Giving a div element a custom placement in a grid in <a href="https://webflow.com/templates/html/kennedy-portfolio-website-template">Kennedy</a></figcaption></figure><p>If you look at the grid settings in the image below, you can see that the element indeed is placed between column 4 and 10.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YsWHE-4HGhUzkVq04qxMIQ.png" /><figcaption>Giving a div element a custom placement in a grid in <a href="https://webflow.com/templates/html/kennedy-portfolio-website-template">Kennedy</a></figcaption></figure><p>The same element wraps down on the tablet breakpoint to span between column 1 and 7, taking up almost the full width of the grid.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*yB7wyVPZreCLK0rE2pJzbg.png" /><figcaption>Spanning an element in a grid in <a href="https://webflow.com/templates/html/kennedy-portfolio-website-template">Kennedy</a></figcaption></figure><h4>Layout grids help layouts stay consistent</h4><p>By sharing my grid class between multiple grids on a page, I’m able to create layouts that stay in a consistent “place” on the page, even if they’re placed in separate grids.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*JBjo22MW75oQ18KTFajEDw.png" /><figcaption>Placing elements consistently inside two grids in <a href="https://webflow.com/templates/html/kennedy-portfolio-website-template">Kennedy</a></figcaption></figure><p>Another example of this is the image placed in the layout grid below, which starts at column 4 but spans all the way to column 12.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_97lwmrmTr5mKsqBtISw2w.png" /><figcaption>Placing an image inside a grid in <a href="https://webflow.com/templates/html/kennedy-portfolio-website-template">Kennedy</a></figcaption></figure><h3>Conclusions</h3><p>If you’re interested in learning more about the technical parts of using grids in Webflow, make sure to <a href="https://help.webflow.com/hc/en-us/articles/33961365794451-Grid">take a look at the official documentation</a>.</p><p>Hopefully this short guide helped you out on whatever project(s) you’re working on. Grids, and especially grids used for layouts, are a great tool to level up as both a designer and a developer.</p><p>Feel free to check out my templates <a href="https://robn.link/templates">on the Webflow marketplace</a>. And also feel free to follow me on <a href="https://www.instagram.com/shapedbyrobin/">Instagram</a> and <a href="https://www.youtube.com/@shapedbyrobin">YouTube</a>, I’m posting some cool stuff over there (mostly related to Webflow, design &amp; illustrations).</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=87694df4d1b9" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Building a Documentation Site in Webflow]]></title>
            <link>https://shapedbyrobin.medium.com/building-a-documentation-site-in-webflow-dd92b77dbd9b?source=rss-946e52f2852c------2</link>
            <guid isPermaLink="false">https://medium.com/p/dd92b77dbd9b</guid>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[webflow]]></category>
            <category><![CDATA[web-design]]></category>
            <category><![CDATA[documentation]]></category>
            <dc:creator><![CDATA[Robin Granqvist]]></dc:creator>
            <pubDate>Wed, 09 Oct 2024 16:57:33 GMT</pubDate>
            <atom:updated>2024-10-10T11:34:40.429Z</atom:updated>
            <content:encoded><![CDATA[<p>If you own a service or a digital product, having a robust and well-organized documentation website can be crucial for the user experience of your customers.</p><figure><img alt="NetDocs Webflow Documentation Template" src="https://cdn-images-1.medium.com/max/1024/1*5rr2VRoGCzNvOu0mlwvJBw.png" /><figcaption><a href="https://webflow.com/templates/html/netdocs-documentation-website-template">NetDocs</a> Webflow Documentation Template</figcaption></figure><p>Webflow can be a great platform to use for your documentation sites without having to touch a single line of code. On top of that, it offers a full-fledged integrated CMS to manage all of your content.</p><p>In this guide, I’ll write down few pointers and tips which hopefully can help you out while building a documentation site in Webflow — from designing &amp; planning your site’s structure to utilizing Webflow’s features.</p><p>I’ve built a few documentation templates for the Webflow marketplace. These are Webflow approved projects that can quite valuable, especially if you’re new to Webflow or just want to save time. Feel free to check them out.</p><ul><li><a href="https://webflow.com/templates/html/netdocs-documentation-website-template">NetDocs</a> ($49)</li><li><a href="https://webflow.com/templates/html/dyno-documentation-website-template">Dyno</a> ($49)</li><li><a href="https://webflow.com/templates/html/docket-documentation-website-template">Docket</a> ($29)</li></ul><h3>1 — Layout</h3><p>The typical layout of a documentation site is quite simple. You usually have a vertical navigation bar on the left hand side, and all readable content to the right. It might look something like this:</p><figure><img alt="NetDocs in Webflow" src="https://cdn-images-1.medium.com/max/1024/1*UP1dRLMKoyiPVlK_9g6dnQ.png" /><figcaption>NetDocs in Webflow</figcaption></figure><p>The easiest way of achieving this layout, while still keeping everything responsive and super-simple, is to use a simple two column container or grid.</p><p>This might look something like this inside the Webflow designer:</p><figure><img alt="Dyno documentation template in Webflow" src="https://cdn-images-1.medium.com/max/1024/1*tRUJMqz-j8ZVbN1wS8rDYA.png" /><figcaption>Dyno documentation template in Webflow</figcaption></figure><p>In the case of the template above, <a href="https://webflow.com/templates/html/dyno-documentation-website-template">Dyno</a>, I’m using a container that utilizes flex box to horizontally space out the left side navigation and the right side content wrapper.</p><p>The container also restricts the width of the whole page at the same time, in this case at a 1240px max-width.</p><p>On smaller breakpoints, the container simply spans down with a horizontal flex direction. Super simple. As it should be.</p><figure><img alt="Dyno on tablet" src="https://cdn-images-1.medium.com/max/1024/1*KHwIvtlTQRB64gOlWXgw9g.png" /><figcaption>Dyno on tablet</figcaption></figure><p>Since this layout will be used on every page of the documentation site (most likely), we can turn the whole layout “skeleton” into a single component.</p><p>This component can then have a blank <em>slot</em> element in place of the content, in which we can drop all content needed for the specific page.</p><p>If you’re unfamiliar with slots in Webflow components, take a look at <a href="https://university.webflow.com/lesson/slots">the documentation</a> (hah).</p><h3>2 — CMS Structure</h3><p>The simplest way of managing a content heavy site is by using the CMS. The CMS collections needed for a documentation may vary depending on complexity, but you probably need at least one of the following:</p><ul><li>Articles</li><li>Categories</li><li>Tags</li><li>Authors</li></ul><p>If we take my <a href="https://webflow.com/templates/html/dyno-documentation-website-template">Dyno template</a> as an example, it contains the following 3 collections:</p><figure><img alt="Dyno CMS collections" src="https://cdn-images-1.medium.com/max/1024/1*QH85xkbTYBV3f3IhjXJgug.png" /><figcaption>Dyno CMS collections</figcaption></figure><p>The Webflow CMS also allows us to build relations between collections. For Dyno, each article has a single category and one or many authors.</p><p>Each category and each author then has their own template page on which all articles related to the category or author is listed using CMS collection filters.</p><p>This is a super simple but straightforward way of making sure the visitor is finding the content they’re looking for.</p><figure><img alt="Picking the article author for an article in Dyno" src="https://cdn-images-1.medium.com/max/1024/1*kKXjnoDaSzIZ9bzCk6qorA.png" /><figcaption>Picking the article author for an article in Dyno</figcaption></figure><h4>CMS Limitations</h4><p><em>As of October 2024, Webflow does not allow us to use any kind of components inside CMS generated content.</em></p><p>For example, if you‘re building a internal documentation for your company’s Webflow components or design system, you won’t be able to display examples of your components inside the rich text content of your CMS generated pages.</p><p>Using <a href="https://university.webflow.com/lesson/create-static-page-templates">static template pages</a> instead of the CMS could be a viable solution to this problem though.</p><h3>3 — Menus</h3><p>Left side vertical navigations commonly displays all articles on documentation sites.</p><p>This can be done inside Webflow by having each category be its own collection list of articles, and using a CMS filter to filter out articles in the specific category that we want to load.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Pf0QN4OHaFPX-KgkMESzXQ.png" /><figcaption>The Get Started navigation “section” with filtered articles</figcaption></figure><p>This makes it easy to write new articles and automatically have them show up in the navigation.</p><h3>4 — Table of contents</h3><p>Having a table of contents for each article is an absolute must when it comes to content heavy sites such as a documentation.</p><p>While Webflow doesn’t offer any native solution for this, a simple JS script can solve it pretty quickly.</p><p>If you want a quick table of contents solution, feel free to use my super-small script called <a href="https://github.com/robingranqvist/toc">TOC (available on Github)</a>. All instructions to get started are available on the <a href="https://github.com/robingranqvist/toc">repository page</a>.</p><h3>5 — Search functionality</h3><p>Creating the search functionality for a site is super easy in Webflow. Simply add a search form somewhere on your site, and the search results page will be created automatically.</p><p>The same can be said for styling the search page. You’re easily able to style the search form and the search results however you want.</p><figure><img alt="Netdocs search page" src="https://cdn-images-1.medium.com/max/1024/1*fPGMUmTOYO4K-wdRHTupgw.png" /><figcaption>Netdocs search page</figcaption></figure><p>One tip I discovered embarrassingly late is the ability to change result length, snippet lengths and other settings by going into the search result item settings in the designer. So make sure you make use of that.</p><figure><img alt="Styling search result items" src="https://cdn-images-1.medium.com/max/1024/1*SxaZUD0l1N4Vc0KGMBcNJA.png" /><figcaption>Styling search result items</figcaption></figure><p>If you’re building a huge documentation and need a more robust search system, you should probably take a look at services such as Elastic search or <a href="https://simplystatic.com/tutorials/search-on-a-static-site/#2-Algolia">Algolia</a>, both of which works great together with Webflow.</p><p>With these, you’re able to create more advanced search systems that utilizes AI for example.</p><h3>Conclusion</h3><p>So that’s it. Hopefully this guide helped you out a bit on the way of building your new documentation site in Webflow.</p><p>As mentioned above, if you’re looking for documentation templates to save time or just don’t feel like learning Webflow from scratch, feel free to take a look at my <a href="https://webflow.com/templates/designers/robin-granqvist">Webflow templates on the marketplace</a>.</p><p>If you have any questions, feel free to write them in the comments, contact me through <a href="https://shapedbyrobin.com/">my portfolio</a> or <a href="https://www.instagram.com/shapedbyrobin/">send a DM on Instagram</a>.</p><p>Bye bye</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=dd92b77dbd9b" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[A Few Tips on Working With Interactions in Webflow]]></title>
            <link>https://shapedbyrobin.medium.com/a-few-tips-on-working-with-interactions-in-webflow-e72d72f9bf27?source=rss-946e52f2852c------2</link>
            <guid isPermaLink="false">https://medium.com/p/e72d72f9bf27</guid>
            <category><![CDATA[webflow-interactions]]></category>
            <category><![CDATA[web-design]]></category>
            <category><![CDATA[webflow]]></category>
            <category><![CDATA[webflow-animation]]></category>
            <category><![CDATA[web-development]]></category>
            <dc:creator><![CDATA[Robin Granqvist]]></dc:creator>
            <pubDate>Wed, 02 Oct 2024 14:58:13 GMT</pubDate>
            <atom:updated>2024-10-02T14:58:13.952Z</atom:updated>
            <content:encoded><![CDATA[<p>Webflow’s interactions offer a great interface to bringing life and movement into your websites without the need for custom code.</p><p>Whether you’re creating subtle micro-interactions or advanced, multi-step scroll animations, they can all help elevate your designs and engage your users.</p><p>However, working with them requires a good understanding of its possibilities and nuances. In this article, I’ll share a few tips on how to work efficiently and avoid common pitfalls when creating interactions in Webflow.</p><h3>1 — Finish your interactions before turning elements into components</h3><p><em>TL;DR — The title.</em></p><p>As of October 2024, there’s this <a href="https://discourse.webflow.com/t/interactions-in-components-grrr-please-help/250022">frustrating bug</a> that breaks working with interactions within an already-created Webflow component. This bug makes it difficult to apply or modify interactions inside a component, which makes everything super frustrating.</p><p>One of the most annoying scenarios is when you’re trying to animate an element that exists outside the component, or something that exists within another component.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2dIM1bX6ojuBzIqlyYwYrA.png" /><figcaption>Unable to select elements outside the component itself</figcaption></figure><p>This leaves you with two inconvenient choices: either unlink the component, apply the interaction, and rewrap the component afterward, or duplicate the element outside the component to work with it separately.</p><p>To add to the complexity, there’s also a <a href="https://discourse.webflow.com/t/webflow-interaction-not-useable-with-components/268694">strange bug</a> that causes interactions to be duplicated when unlinking a component, forcing you to delete the duplicated interaction and re-applying the original one.</p><p><strong><em>Until this is fixed, just finish all your interactions on an element before turning it into a component.</em></strong></p><h3>2 — Easily reverse secondary interactions</h3><p>Have you ever created a hover in / out interaction (or similar two-part interaction) and felt frustrated having to remember each element that’s being animated on the <em>hover in</em> interaction required to replicate the <em>hover out</em> interaction?</p><p>Of course you have. Luckily there’s a quite smart solution to that. And it’s super simple.</p><ol><li>Start by duplicating your hover in interaction.</li><li>Delete all but the initial key frames (shift + click to select multiple).</li><li>Deselect the “initial” setting for all remaining key frames.</li><li>Apply any delay, easing or timing that’s required.</li><li>Done.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ME9y2jg70Yf3k_68kenLrQ.png" /><figcaption>A reversed hover out interaction without initial keyframes</figcaption></figure><h3>3 — Prohibit page load animations getting stuck</h3><p>Since I’m a template designer, I get a few support emails every now and then. One of the most common problems customers seem to face is related to breaking load animations.</p><p>What usually happens is that the animation gets triggered on page load, but somewhere in the middle it breaks down and refuses to play the remaining key frames.</p><p>This is most often caused by elements animated in the load animation having changed or being deleted in the designer. If you face this problem, the solution is to go through each key frame in your load interaction and delete the one(s) that aren’t connected to an element on your page.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7bd8giTj7csg2SJRu40LMw.png" /><figcaption>Making sure every key framed element exists on the page</figcaption></figure><h3>4 — Proper navbar interactions</h3><p>It’s almost embarrassing how long it took me to discover the navbar interaction trigger in Webflow. But once I did, it solved so many issues with the native navbar that I hadn’t even noticed before, especially when animating lottie icons.</p><p>You see, I always assumed that on lower breakpoints, you should put the open and close navbar interactions on the menu button itself, in which I animated my lottie icon animations.</p><p>However, this is wrong. Instead, you should use the built-in “navbar opens” trigger.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ZsfA-8HxUGb-7sTIUqDsZA.png" /><figcaption><strong>Navbar opens</strong> interaction trigger in Webflow</figcaption></figure><p>This trigger will automatically triggers whenever the navbar open or closes, and will consistently play whatever lottie / other animation you’re using in your navbar without having to rely on specific button clicks.</p><p>Please note that the “Navbar opens” trigger only exists on the native navbar element inside Webflow.</p><h3>Class based triggers</h3><p>Have you ever want to use the same animation on multiple elements and places in your Webflow project? Well, maybe a class based trigger could help you out.</p><p>What I mean by class based trigger is to create a specific class, of which an interaction is placed on, and use this class on multiple elements in your project.</p><p>This simplifies your Webflow project, as well as decreases the Javascript rendered by having multiple of the same interaction in a project.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8R0t4Bv9uwhbgop6y38IsA.png" /><figcaption>A heading containing a class of <strong>“Animate On Load</strong>” which has a simple opacity reveal animation attached</figcaption></figure><h3>Conclusions</h3><p>This was a rather short, but hopefully somewhat helpful guide on working with interactions in Webflow.</p><p>If you have any questions, feel free to ask them in the comments, or send me an email <a href="https://shapedbyrobin.com/">over at my website</a>.</p><p>Also make sure to take a look at <a href="https://webflow.com/templates/designers/robin-granqvist">my minimal Webflow templates</a> on the marketplace, or <a href="https://www.instagram.com/shapedbyrobin/">follow me on Instagram</a> if you wish.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e72d72f9bf27" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[A Short Guide on Using Components in Webflow]]></title>
            <link>https://shapedbyrobin.medium.com/a-short-guide-on-using-components-in-webflow-3ee4ae1ccc3b?source=rss-946e52f2852c------2</link>
            <guid isPermaLink="false">https://medium.com/p/3ee4ae1ccc3b</guid>
            <category><![CDATA[webflow]]></category>
            <category><![CDATA[webflow-development]]></category>
            <category><![CDATA[webflow-component]]></category>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[web-design]]></category>
            <dc:creator><![CDATA[Robin Granqvist]]></dc:creator>
            <pubDate>Wed, 25 Sep 2024 18:17:26 GMT</pubDate>
            <atom:updated>2024-09-25T18:17:26.951Z</atom:updated>
            <content:encoded><![CDATA[<p>If you’ve been using Webflow for a few years, you’ve likely come across one of my (and many others’) favorite “new” feature: components.</p><p>It’s actually not a new feature. <a href="https://webflow.com/updates/symbols-evolved-to-components">Components were previously named symbols</a> and were used quite similarly to how components are used today (but with a lot less features such as <a href="https://university.webflow.com/lesson/component-properties?topics=layout-design">props</a>), but that’s long gone now.</p><p>Even though components are a fairly well known pattern in web development, there seems to be some confusion about how, and when, to use them effectively.</p><p>And that’s why this article is written. This guide will go through the basics on how you can use components in Webflow effectively and hopefully provide some clarity. Let’s go.</p><figure><img alt="A Service Item component inside my portfolio template — Kennedy" src="https://cdn-images-1.medium.com/max/1024/1*sDCS7TAJzMQU5UCl8jas_g.png" /><figcaption>A Service Item component inside my portfolio template — <a href="https://webflow.com/templates/html/kennedy-portfolio-website-template">Kennedy</a></figcaption></figure><h3>What is a Webflow component?</h3><p>A component is a <em>reusable building block that encapsulates a piece of design or functionality</em> in your Webflow project.</p><p>With components, you can encapsulate a specific part of the design — whether it’s a simple element like a button or a more complex structure like a full section — so that they can be reused throughout different sections or pages.</p><p>When you make a change to a component, every instance of it across your project updates automatically, allowing you to save time and keep your design consistent.</p><figure><img alt="A “Content List Item” component inside my portfolio template — Kennedy" src="https://cdn-images-1.medium.com/max/1024/1*0BM-AnB5IXk-12N1vyo7Cg.png" /><figcaption>A “Content List Item” component inside my portfolio template — <a href="https://webflow.com/templates/html/kennedy-portfolio-website-template">Kennedy</a></figcaption></figure><h4>Component props</h4><p>An instance of a component can be customized using props (properties), which let you adjust specific content or settings (such as text, images, links or visibility) uniquely to a specific component instance, while keeping the core structure intact.</p><figure><img alt="Multiple unique “Content List Item” component instances inside my portfolio template — Kennedy" src="https://cdn-images-1.medium.com/max/1024/1*aIHV3UN9sw_XLDA_o3pVpw.png" /><figcaption>Multiple unique “Content List Item” component instances inside my portfolio template — <a href="https://webflow.com/templates/html/kennedy-portfolio-website-template">Kennedy</a></figcaption></figure><p>Props are setup by linking any element inside your component to a property and giving it a property name. This element can now be customized uniquely on any instance of the component.</p><figure><img alt="The “Title” prop in the “Content List Item” component inside my portfolio template — Kennedy" src="https://cdn-images-1.medium.com/max/1024/1*o57EdaG8LVqtAJX5ijW1Ow.png" /><figcaption>The “Title” prop in the “Content List Item” component inside my portfolio template — <a href="https://webflow.com/templates/html/kennedy-portfolio-website-template">Kennedy</a></figcaption></figure><h4>Nested components</h4><p>Webflow allows us to nest components as deeply as needed, meaning you can place a component inside another component, and so on.</p><p>Each property of a nested component can be “lifted” to the parent component, allowing you to customize the nested component through the parent’s interface.</p><p>For example, the breadcrumbs of the title component in the image below is its own component. All breadcrumb links are lifted to the title component, making them customizable through the interface of the title component.</p><figure><img alt="Breadcrumb component inside the title component of my documentation template — NetDocs" src="https://cdn-images-1.medium.com/max/1024/1*YyaXXB84allGaL3REAxCMA.png" /><figcaption>Breadcrumb component inside the title component of my documentation template — <a href="https://webflow.com/templates/html/netdocs-documentation-website-template">NetDocs</a></figcaption></figure><h3>Why should you use components?</h3><p>There are so many good reasons to start using components in your Webflow projects.</p><p>Let’s briefly break a few of them down.</p><h4>1 — Components make things reusable</h4><p>As mentioned above, any change made to a component’s design or functionality will automatically update in every instance where that component is used.</p><p>This makes components ideal for any design element you want to reuse across your site, even if they’re small.</p><p>Let’s take a simple button as an example. The hypothetical button in question only contains some text an a little icon on the left side.</p><p>If it’s not encapsulated as a component, what happens when you decide that you actually want your button icons on the right side?</p><p>That’s right — you’ll have to update every single button one by one. Don’t do that.</p><figure><img alt="Reusing a FAQ item in my documentation template — NetDocs" src="https://cdn-images-1.medium.com/max/1024/1*L6J8E_lXmDpuP9FM-8YiOg.png" /><figcaption>Reusing a FAQ item in my documentation template — <a href="https://webflow.com/templates/html/netdocs-documentation-website-template">NetDocs</a></figcaption></figure><h4>2 — Clean interface for customization</h4><p>Imagine being a client with no Webflow experience trying to customize a slider in the beautiful project you just developed for them.</p><p>How long do you think it would take for them to figure out how to modify the slider when each slide in the slider involves a slide mask, a slide wrapper and the content inside each slide?</p><p>I bet it would likely take quite a while.</p><p>Now, instead picture a custom slider component where the slide image, title, and link are neatly organized in the settings panel, ready to be easily customized.</p><p>Doesn’t that sound amazing? Absolutely. And that’s one of the biggest advantages of turning elements into components — it greatly simplifies the development process for everyone.</p><figure><img alt="Customizing the “Content Article Card” component in my documentation template — NetDocs" src="https://cdn-images-1.medium.com/max/1024/1*STbwxNhsuCiyaXKvlT0Zcw.png" /><figcaption>Customizing the “Content Article Card” component in my documentation template — <a href="https://webflow.com/templates/html/netdocs-documentation-website-template">NetDocs</a></figcaption></figure><h4>3 — Consistency in design</h4><p>Since all instances of a component update when a change is made to one of them, your design is basically forced to remain consistent across all pages and sections.</p><p>If you notice you’ve made a mistake in some part of your design, you won’t have to hunt down every single instance of it and fix them individually. And I think that’s great.</p><h3>Conclusion</h3><p>Hopefully that little guide helped you out on your Webflow development endeavours. If you have any questions, feel free to post them in the Medium comments, or <a href="https://shapedbyrobin.com/">send me an email</a>.</p><p>Also, feel free to <a href="https://webflow.com/templates/designers/robin-granqvist">check out my Webflow templates on the marketplace</a>, and <a href="https://www.instagram.com/shapedbyrobin/">follow me on Instagram</a> if you want. Byebye.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3ee4ae1ccc3b" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Super-Easy Table of Contents (Rich Text) in Webflow]]></title>
            <link>https://shapedbyrobin.medium.com/super-easy-table-of-contents-rich-text-in-webflow-18feed988ad2?source=rss-946e52f2852c------2</link>
            <guid isPermaLink="false">https://medium.com/p/18feed988ad2</guid>
            <category><![CDATA[webflow-development]]></category>
            <category><![CDATA[webflow-table-of-contents]]></category>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[table-of-contents]]></category>
            <dc:creator><![CDATA[Robin Granqvist]]></dc:creator>
            <pubDate>Fri, 14 Jun 2024 12:00:58 GMT</pubDate>
            <atom:updated>2024-06-14T12:00:58.772Z</atom:updated>
            <content:encoded><![CDATA[<p>When building content heavy sites, having a table of contents for each article or post is absolutely crucial for the user experience.</p><p>However, there isn’t any native way of creating a dynamic one in Webflow. That’s why I wrote a tiny script to help you set one up in seconds.</p><figure><img alt="A table of contents for my Webflow template — Netdocs" src="https://cdn-images-1.medium.com/max/1024/1*LIE171-LseObb3Fni4Jupg.png" /><figcaption>A table of contents for my Webflow documentation template — <a href="https://robn.link/netdocs">Netdocs</a></figcaption></figure><h3>1 — Github</h3><p>The first thing you should do is to visit my <a href="https://github.com/robingranqvist/toc">Github repo for Toc.js</a>. There you’ll find all the instructions you need to get going, but feel free to read this article if you need a more detailed overview.</p><h3>2 — Initialize</h3><p>Start by importing the script using the import script in the repo. This should be placed before the body tag on all the pages you want to add a table of contents on.</p><p>Copy the initialization code from the Github repo and place it inside script tags underneath your import. This creates a new instance of Toc.js.</p><h4>Text source</h4><p>The first option is the <em>text source</em>, meaning the class name of your rich text element in Webflow.</p><h4>Target</h4><p>The second option is the class name of whatever div element you want to place your table of contents in. You can place this div wherever you want on your page.</p><h4>Included heading types</h4><p>The third option is an array of all heading types you want included in your toc.</p><h4>Indent size</h4><p>Sometimes, you might want to indent lower heading (H3, H4 etc.) to visualize the hierarchy of headings in your table of contents. This number is the pixel based value of how large you want your indentations to be.</p><h3>3 — Setup your table of contents</h3><p>There are three classes that are required for this script to work correctly.</p><h4>Toc</h4><p>This is the main “list” element for your toc. Typically you’d want to use a vertical flex gap to space out the children of this div element.</p><h4>Toc Item</h4><p>This is a “list item” of the toc list. You can style this one however you want, but it can also be left as is.</p><h4>Toc Heading</h4><p>These are the generated heading links of your toc. Feel free to style them however you see fit. In my example video, I make them blue &amp; small and that’s pretty much it.</p><figure><img alt="A typical Toc.js setup in Webflow" src="https://cdn-images-1.medium.com/max/1024/1*u-0XZ9nrDT0rJ7ZVBvGpNQ.png" /><figcaption>A typical Toc.js setup in Webflow</figcaption></figure><h3>4 — Conclusion</h3><p>That’s it, that’s all. Hopefully this script can help you save some time for your next project(s). If you need help, feel free to comment down below or hit me up <a href="https://shapedbyrobin.com/">through my site</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=18feed988ad2" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[CMS-driven Data Visualization Charts in Webflow]]></title>
            <link>https://shapedbyrobin.medium.com/cms-driven-data-visualization-charts-in-webflow-bb8340d5b4bf?source=rss-946e52f2852c------2</link>
            <guid isPermaLink="false">https://medium.com/p/bb8340d5b4bf</guid>
            <category><![CDATA[no-code]]></category>
            <category><![CDATA[charts-and-graphs]]></category>
            <category><![CDATA[data-visualization]]></category>
            <category><![CDATA[charts]]></category>
            <category><![CDATA[webflow]]></category>
            <dc:creator><![CDATA[Robin Granqvist]]></dc:creator>
            <pubDate>Thu, 06 Jun 2024 15:01:24 GMT</pubDate>
            <atom:updated>2024-06-06T15:01:24.715Z</atom:updated>
            <content:encoded><![CDATA[<p>Have you ever needed to visualize some data on your Webflow website, but didn’t know how to get started? Well, then you’ve found the perfect article.</p><p>Today you’re gonna learn how to use <a href="https://www.chartjs.org/docs/latest/">Chart.js</a> in Webflow to visualize your data directly through the Webflow CMS. It requires some custom code, but trust me, it’s super easy. Let’s go.</p><figure><img alt="Chart.js bar chart" src="https://cdn-images-1.medium.com/max/1024/1*XrCn-oWsGZRkd9BVTrLZkg.png" /><figcaption>Chart.js bar chart</figcaption></figure><p><em>Before we start, I’ve made an example Webflow project for integrating Chart.js with Webflow that you can clone &amp; check out by </em><a href="https://webflow.com/made-in-webflow/website/cms-driven-charts"><em>clicking here</em></a><em>.</em></p><h3>Chart.js</h3><p>Chart.js is a quite small, easy-to-use data visualization Javascript library. It has tons of different charts and options to choose from, but in this article we’ll focus on just creating a simple bar chart with a few data points and labels.</p><figure><img alt="Charts.js" src="https://cdn-images-1.medium.com/max/1024/1*8P3jXFSoGhEGzblTF5xEOQ.png" /><figcaption>Charts.js</figcaption></figure><h3>CMS Setup</h3><p>Let’s setup a new CMS collection that can be used as a dynamic database for multiple unique charts on the same page. We’ll go through each field needed one by one.</p><h4>Title</h4><p>As the Webflow CMS requires us to give each collection item a name or a title, we can use this as the title for our chart.</p><h4>Chart ID</h4><p>Each chart needs a unique ID. We can use a simple <em>text field</em> for this, but make sure that each ID is unique.</p><h4>Chart type</h4><p>Chart.js decides what type of chart to render by an option called type. It accepts text strings such as:</p><ul><li>bar</li><li>doughnut</li><li>line</li><li>etc.</li></ul><p>We can use a simple <em>text field</em> for this option as well.</p><h4>Data points</h4><p>In order to render a chart, we need some data. We can use a <em>text field</em> for this as well, but we’ll insert each data point as a comma separated string like this:</p><p>5, 92, 43, 123, 16</p><h4>Labels</h4><p>The last field we need is for the labels. This should be a <em>text field</em> as well, and similar to the data points, we’ll insert a comma separated string like this:</p><p>Horses, Ducks, Dogs, Cats, Capybaras</p><h4>The collection</h4><p>When we’re finished, an item in the collection should look something like the image below.</p><figure><img alt="The collection" src="https://cdn-images-1.medium.com/max/1024/1*yignt3ak0yEhmkCQzin6hA.png" /><figcaption>The collection</figcaption></figure><h3>The code</h3><p>Okay, now it’s time to write some code. The first step is to actually import the Chart.js library. You can do that by copying the <a href="https://www.chartjs.org/docs/latest/getting-started/">CDN link from their documentation</a>, and place it before the end body tag in the page/site settings of your Webflow project.</p><p>For each chart (or each collection item) we’ll need to add an embed element, where we’ll write the following code.</p><h4>Creating a new canvas element</h4><p>Chart.js renders each chart in a HTML canvas element. Therefore, we need to create a new canvas for each chart we want to render.</p><p>We can easily do this with the following line of code in our embed:</p><pre>&lt;div&gt;&lt;canvas id=”chart-id”&gt;&lt;/canvas&gt;&lt;/div&gt;</pre><p>The chart ID has to be dynamic thought, since each chart needs its own unique canvas. We can use Webflow’s CMS embed fields and place our chart ID as the canvas id.</p><figure><img alt="Webflow CMS embed fields" src="https://cdn-images-1.medium.com/max/999/1*KJHlACbN1uWDFVz04GigvA.png" /><figcaption>Embed fields</figcaption></figure><h4>Converting a string to an array of integers</h4><p>The first thing we need to understand is that Chart.js works with actual numbers (integers) in an array as data points.</p><p>When we’re using a text field for our data in the CMS, the data is actually a comma separated string, which Chart.js has no idea how to interpret.</p><p>To solve this, we can use the following function:</p><pre>function intsToArray (data) {<br>  return data.split(‘,’).map(item =&gt; parseInt(item.trim(), 10));<br>}</pre><p>This function will accept the data string as an argument, parse it, and will return an array of integers.</p><h4>Converting a string to an array of strings</h4><p>The second problem we’ll have to fix is to turn the labels string into an array of string. We can easily do this by writing another simple function:</p><pre>function stringsToArray (data) {<br>   return data.split(‘,’).map(item =&gt; item.trim());<br>}</pre><h4>Initializing Chart.js</h4><p>Feel free to reference the <a href="https://www.chartjs.org/docs/latest/getting-started/">Chart.js documentation</a> for this step.</p><p>A simple version of the needed boilerplate setup code looks like this:</p><pre>new Chart(document.getElementById(&quot;chart-id&quot;), {<br>  type: &#39;bar&#39;,<br>  data: {<br>    labels: [&#39;Red&#39;, &#39;Blue&#39;, &#39;Yellow&#39;, &#39;Green&#39;, &#39;Purple&#39;, &#39;Orange&#39;],<br>    datasets: [{<br>      label: &#39;# of Votes&#39;,<br>      data: [12, 19, 3, 5, 2, 3]<br>    }]<br>  }<br>});</pre><p>As you can see, we need to fill in:</p><ul><li>The chart ID</li><li>The type</li><li>The labels for the data</li><li>The label for the dataset</li><li>The data</li></ul><p>Since we already setup our CMS collection with all this data, we can use the embed fields to fill in each option.</p><p>As you can see, we’re using the “intsToArray” and “stringsToArray” functions for the data &amp; labels respectively.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1001/1*Jv-6AUsk7KLII7uYtkYaUA.png" /></figure><h3>Publishing</h3><p>That’s it! We’re done. When you publish your site, you’ll now see a pretty bar chart with the data from the CMS. It should look something like this:</p><figure><img alt="A chart.js bar chart" src="https://cdn-images-1.medium.com/max/1024/1*wEhrs2bHrQZU4UTC5URHLA.png" /><figcaption>Bar chart</figcaption></figure><p>If we simply change our chart type to “line”, you should see something like this:</p><figure><img alt="Line chart" src="https://cdn-images-1.medium.com/max/1024/1*eNOV-7H4eQegZ0hI-TcSig.png" /><figcaption>Line chart</figcaption></figure><h3>Conclusion</h3><p>If you visit the <a href="https://www.chartjs.org/docs/latest/getting-started/">Chart.js documentation</a>, there are lots and lots of additional charts &amp; options to play around with. Some of them need additional data, or parameters, but I’m sure you’ll figure it out.</p><p>If you have any questions, feel free to comment down below or hit me up through <a href="https://shapedbyrobin.com/">my website</a>. Enjoy.</p><p><em>Don’t forget that you can </em><a href="https://webflow.com/made-in-webflow/website/cms-driven-charts"><em>clone my Chart.js example project</em></a><em> on the Webflow showcase.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bb8340d5b4bf" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Consistent Spacing using Flex Wrappers in Webflow]]></title>
            <link>https://shapedbyrobin.medium.com/consistent-spacing-using-flex-wrappers-in-webflow-71303722df4d?source=rss-946e52f2852c------2</link>
            <guid isPermaLink="false">https://medium.com/p/71303722df4d</guid>
            <category><![CDATA[web-design]]></category>
            <category><![CDATA[style-guides]]></category>
            <category><![CDATA[webflow]]></category>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[spacing]]></category>
            <dc:creator><![CDATA[Robin Granqvist]]></dc:creator>
            <pubDate>Wed, 05 Jun 2024 09:01:41 GMT</pubDate>
            <atom:updated>2024-06-05T09:01:41.754Z</atom:updated>
            <content:encoded><![CDATA[<p>There is this thing in web development that I’ve always felt was a bit unnecessary complicated to get right — consistent spacing between elements.</p><h3>The problem</h3><p>Imagine you’re developing this simple title component. It contains a heading, a description paragraph and a couple buttons in a horizontal row.</p><p>Now, how would you develop this component?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*oj3jM0u7GfVoSR28lq6RWQ.png" /><figcaption>Title component example</figcaption></figure><p>I would assume that a common solution would be to give the heading a bottom margin, the paragraph a bottom margin and the buttons placed in a div with a right &amp; left margin respectively.</p><p>While this could be a fully functional solution, what would you do when developing the following secondary title component in the same project?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1eHGp9ZndS6v8-sXMQSBSA.png" /><figcaption>Secondary title example component</figcaption></figure><p>As you can see, the elements themselves stay exactly the same, but the spacing between them have changed and become smaller.</p><p>One solution would be to use additional combo-classes for each element, decrease the margins and you’re finished. However, what would you do if you have 25 other title components to develop? If you decide to use this solution, your projects will end up with hundreds and hundreds of classes for every new type of spacing you need.</p><h3>The solution</h3><p>My absolute favorite solution for this problem is…..flex wrappers.</p><p>These are utility classes for div blocks that wraps child elements and decides the spacing between them using horizontal or vertical flex gap.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6WyZhL3khrAJmoTpeRkRJg.png" /><figcaption>Wrappers with flex gap</figcaption></figure><p>It’s a bit hard to visualize this way, but in the image above you can see that:</p><ul><li>The whole component is wrapped in a div with a vertical flex gap.</li><li>The heading &amp; paragraph is wrapped in a div with a smaller vertical flex gap.</li><li>Two buttons that are wrapped in a div with a horizontal flex gap.</li></ul><p>We can also take a look at the secondary title component.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*85j7eZwZHk-ejnMKYrISiw.png" /><figcaption>Wrappers with flex gap</figcaption></figure><p>It setup in the exact same way, except for using wrappers with smaller flex gaps. All the elements are spaced out, but none of the elements has ANY margin set. <em>The parent decides the spacing between its children.</em></p><h3>The system</h3><p>I always setup a system of flex wrapper classes. Ever since Webflow introduced the V &amp; H Flex elements, this has been even simpler to do.</p><p>The system usually looks something like this:</p><ul><li>Vertical Flex 2XS — 2XL (0.25 REM — 10 REM)</li><li>Horizontal Flex 2XS — 2XL (0.25 REM — 10 REM)</li></ul><p>The naming of these classes can be anything, but I just name them V Flex and H Flex. This type of spacing system has worked well so far.</p><h3>Conclusion</h3><p>Hopefully this guide helped you out in your quest to spacing perfection. If you have any questions, feel free to comment down below or hit me up through <a href="https://shapedbyrobin.com/">my website</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=71303722df4d" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>