<?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[Quarkly - Medium]]></title>
        <description><![CDATA[Quarkly (https://quarkly.io) is a mix of a graphic editor, website builder, and classic IDE. Developers can introduce custom components to the system, web designers — manage them visually on the canvas. And vice-versa — the created mockup gets transformed into React code. - Medium]]></description>
        <link>https://medium.com/quarkly?source=rss----b6393ecbb64a---4</link>
        <image>
            <url>https://cdn-images-1.medium.com/proxy/1*TGH72Nnw24QL3iV9IOm4VA.png</url>
            <title>Quarkly - Medium</title>
            <link>https://medium.com/quarkly?source=rss----b6393ecbb64a---4</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 12:38:16 GMT</lastBuildDate>
        <atom:link href="https://medium.com/feed/quarkly" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Quarkly is Looking for a Product Evangelist]]></title>
            <link>https://medium.com/quarkly/quarkly-is-looking-for-a-product-evangelist-2842764a5473?source=rss----b6393ecbb64a---4</link>
            <guid isPermaLink="false">https://medium.com/p/2842764a5473</guid>
            <category><![CDATA[reactjs]]></category>
            <category><![CDATA[react]]></category>
            <category><![CDATA[social-media]]></category>
            <category><![CDATA[marketing]]></category>
            <category><![CDATA[javascript]]></category>
            <dc:creator><![CDATA[Alex]]></dc:creator>
            <pubDate>Wed, 24 Jun 2020 14:40:09 GMT</pubDate>
            <atom:updated>2020-06-24T14:40:09.127Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*EkGZUbr6F9QrKvIPh2mb3Q.png" /></figure><p><a href="https://quarkly.io/"><em>Quarkly</em></a><em> is a unique design tool for creating React based websites and web apps</em><strong><em>. </em></strong><em>It is designed for webmasters, designers, and developers.</em></p><p><em>Here you can create websites as quickly as in website builders and as beautifully as in graphic editors.</em></p><h4><strong>Why are we called Quarkly?</strong></h4><p>Just as in physics where the smallest elements — quarks — build up an atom, with Quarkly, you can manipulate the smallest elements and edit code on the most fundamental level to build an amazing website.</p><blockquote>We are looking for a rock-star evangelist to build and grow Quarkly’s communities, cultivate product awareness, and educate followers on its latest updates and releases.</blockquote><h4><strong>You will:</strong></h4><ul><li>Generate and share content to build Quarkly’s reputation as a leading web design tool.</li><li>Actively participate in Quarkly’s online communities.</li><li>Cultivate awareness of Quarkly’s product within relevant communities of designers and front-end developers.</li><li>Collaborate with Quarkly’s product and marketing teams.</li></ul><h4><strong>Requirements:</strong></h4><ul><li>You have extensive knowledge of front end/web design and have an interest in developing content focused around this.</li><li>You already are an active member of the front-end, web or language communities in your region.</li><li>You have a strong following on social media or online professional communities</li><li>You are able to transform dry technical topics into engaging, informative, and interesting educational materials.</li></ul><p>Quarkly is going to revolutionize the way websites, and apps are created.</p><p>Join us on this journey!</p><p>To apply, email <a href="/service/mailto:pr@quarkly.io">pr@quarkly.io</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2842764a5473" width="1" height="1" alt=""><hr><p><a href="https://medium.com/quarkly/quarkly-is-looking-for-a-product-evangelist-2842764a5473">Quarkly is Looking for a Product Evangelist</a> was originally published in <a href="https://medium.com/quarkly">Quarkly</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why We Gave Up on the Idea of Using Styled System to Create Components]]></title>
            <link>https://medium.com/quarkly/why-we-gave-up-on-the-idea-of-using-styled-system-to-create-components-fb65012e063f?source=rss----b6393ecbb64a---4</link>
            <guid isPermaLink="false">https://medium.com/p/fb65012e063f</guid>
            <category><![CDATA[css-in-js]]></category>
            <category><![CDATA[reactjs]]></category>
            <category><![CDATA[styled-components]]></category>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[react]]></category>
            <dc:creator><![CDATA[Alex]]></dc:creator>
            <pubDate>Tue, 16 Jun 2020 15:26:47 GMT</pubDate>
            <atom:updated>2020-06-16T15:26:47.478Z</atom:updated>
            <content:encoded><![CDATA[<p>Hi everyone! My name is Alex. I’m one of the founders and lead developer at <a href="https://quarkly.io/">Quarkly</a>. In this post, I’d like to share with you how the concept of atomic CSS, which we follow, together with the disadvantages of <em>styled-system</em> functionality (and <em>rebass</em> in particular) inspired us to create our own tool that we call Atomize.</p><h4>A Few Words About Us</h4><p>Our Quarkly project is a mix of a graphic editor (like Figma and Sketch) and website builder (similar to Webflow), complemented by features of traditional IDE. We’ll be sure to elaborate on Quarkly in a separate post, as there is plenty to tell and show, but today we’ll focus on the details of the Atomize tool.</p><p>Atomize is the heart of the whole project, as it allows us to solve tasks that would be difficult or even impossible to handle using <em>styled-system</em> and <em>rebass</em>. At the very least, the latter solution is much less elegant.</p><p>If you don’t have time to read the entire post now, check out a brief description of Atomize on our <a href="https://github.com/quarkly/atomize">GitHub</a>.</p><h4>How It All Started</h4><p>When we got down to developing this tool, our team’s task was to give users the opportunity to code on two components, but without the need to have a separate CSS file. This was to keep the code as minimalistic as possible while retaining all CSS features in contrast to inline styles.</p><p>The task was far from ground-breaking and, at first sight, could be easily solved with the help of <em>styled-system</em> (and <em>rebass</em>). But its functionality turned out to be limited for us. Or rather, we ran into the following problems:</p><ul><li>inconvenient breakpoints</li><li>no option to write styles for <em>hover</em>, <em>focus</em>, and other behaviors</li><li>mechanism for working with themes wasn’t as flexible as we needed</li></ul><h4>Briefly About Atomize</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*drB8hqTuN2jNqRUiyZL00w.png" /></figure><h4>Here are the key Atomize features:</h4><ul><li>option to use variables from the theme in composite CSS properties</li><li>support for <em>hover</em> and any other pseudo-classes</li><li>short aliases for each property (like in <em>emmet</em>)</li><li>opportunity to set styles for a specific breakpoint, all while keeping the markup readable</li><li>minimalistic interface</li></ul><p>That being said, Atomize is intended for two main purposes:</p><ul><li>creation of components that support atomic CSS and themes</li><li>creation of widgets for the interactive editing in the Quarkly project</li></ul><h4>Atomize. A User Manual</h4><p>Before you start working with Atomize, you need to set up dependencies:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/46ed7b22c7a236458813606cd25fd239/href">https://medium.com/media/46ed7b22c7a236458813606cd25fd239/href</a></iframe><p>Atomize serves as a wrapper around a <em>styled-component</em> and has a similar API. Just call the method using the name of the required element:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/15119433335d40d1b6622c11dcb9e4c0/href">https://medium.com/media/15119433335d40d1b6622c11dcb9e4c0/href</a></iframe><p>As a result, we get the React component that can take any CSS in the form of properties.</p><p>To make it easier to use, we developed the system of alias properties. For example, <em>bgc === backgroundColor.</em></p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/18f992ea5ffbccb5bb8e04b06559f167/href">https://medium.com/media/18f992ea5ffbccb5bb8e04b06559f167/href</a></iframe><p>To see the full list of properties and aliases, follow this <a href="https://github.com/quarkly/elementary/blob/master/docs/props.md">link</a>.</p><p>Plus, we added the mechanism of inheritance in React:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/f8114556e0ab40d98b820a84c5c816b3/href">https://medium.com/media/f8114556e0ab40d98b820a84c5c816b3/href</a></iframe><h4>Themes</h4><p>This, I think, should be explained in more detail.</p><p>Quarkly themes are based on CSS variables. The key feature of Quarkly themes is that variables from themes can be reused both in props and themes. You don’t need to use additional abstractions, like template functions, and no additional editing is needed by the user.</p><p>To use variables from a theme, just describe the property in the theme and call this property using the prefix “ — “.</p><p>The variables can be used both in JSX:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/5344401eff0cfa0064d957e618a45568/href">https://medium.com/media/5344401eff0cfa0064d957e618a45568/href</a></iframe><p>And in the theme itself:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/b05de281c82a8e22cc42794b535d1f6d/href">https://medium.com/media/b05de281c82a8e22cc42794b535d1f6d/href</a></iframe><p>The shorter syntax is used for colors in the JSX markup:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/eb7ba4a822602c05904fb3231b461840/href">https://medium.com/media/eb7ba4a822602c05904fb3231b461840/href</a></iframe><p>Themes have breakpoints for working with media expressions.</p><p>Any property can be prefixed with a breakpoint key name.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/3086c765588f19e916dfcc9f011254d9/href">https://medium.com/media/3086c765588f19e916dfcc9f011254d9/href</a></iframe><p>You can find the source code <a href="https://github.com/quarkly/theme">here</a>.</p><h4>Effects</h4><p>The main difference between Atomize and the <em>styled system</em> is the “effects”.</p><p>What are they and why do you need them?</p><p>Well, imagine you create a <em>Button </em>component, change its <em>color</em> and <em>border</em> and then… you realize you don’t know how to assign styles to <em>hover</em>, <em>focus,</em> etc. This is where effects come to the rescue.</p><p>When creating a component, just transfer an object with the configuration:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/2b7e73415d0c89dfe9500204e2221deb/href">https://medium.com/media/2b7e73415d0c89dfe9500204e2221deb/href</a></iframe><p>The key is the prefix in the name of the property, and the value is a CSS selector. This is the same way we implemented pseudo-classes.</p><p>Now, if you specify the <em>hover</em> prefix for any CSS property, it will be applied to a certain effect. For example, when you mouse over it:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/9b2155a43b621bf466257b7210b60bf4/href">https://medium.com/media/9b2155a43b621bf466257b7210b60bf4/href</a></iframe><p>You can also combine effects with media expressions:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/81243f406521d9698a18d3934b83a013/href">https://medium.com/media/81243f406521d9698a18d3934b83a013/href</a></iframe><h4>A Few Examples</h4><p>Let’s build several interesting components to illustrate the features I’ve described above.</p><p>Here are two examples:</p><ul><li><a href="https://codesandbox.io/s/atomize-demo-skhjw?file=/src/Example.js">a simple component that shows all the capabilities of the library</a></li><li><a href="https://codesandbox.io/s/pokemon-card-atomize-9pwom?file=/src/App.js">a more complex example with a Pokémon card</a></li></ul><p>Everybody loves Pokémon, don’t they? :)</p><h4>Wait! There’s More</h4><p>The second purpose of Atomize, as I mentioned above, is to create widgets in Quarkly based on custom React components.</p><p>All you have to do is wrap your component in Atomize and describe its configuration so that Quarkly can understand which properties can be interactively edited:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/4c3bea1812f9b0b22cbda6ab81796faa/href">https://medium.com/media/4c3bea1812f9b0b22cbda6ab81796faa/href</a></iframe><p>The configuration fields for the component look like this:</p><ul><li><em>effects</em> — defines browser pseudo-classes (<em>hover, focus, etc.</em>)</li><li><em>description</em> — component description that will appear when you mouse over its name</li><li><em>propInfo</em> — configuration of controls that will be displayed on the right panel (Props tab)</li></ul><p>How to specify the props to be displayed on the right panel (Props tab):</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/9167f149bed3b2dd209cc62fa28622d6/href">https://medium.com/media/9167f149bed3b2dd209cc62fa28622d6/href</a></iframe><p>Possible control options:</p><ul><li>input</li><li>select</li><li>color</li><li>font</li><li>shadow</li><li>transition</li><li>transform</li><li>filter</li><li>background</li><li>checkbox-icon</li><li>radio-icon</li><li>radio-group</li><li>checkbox</li></ul><p>One more example, where we’ve added our custom component to the system and can now edit it interactively:</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FBzkV_g_q84U%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DBzkV_g_q84U&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FBzkV_g_q84U%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/3e5e835849180dbc023204e98d95cb8d/href">https://medium.com/media/3e5e835849180dbc023204e98d95cb8d/href</a></iframe><p>Yay! You’ve made it to the end :) Thanks for reading!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=fb65012e063f" width="1" height="1" alt=""><hr><p><a href="https://medium.com/quarkly/why-we-gave-up-on-the-idea-of-using-styled-system-to-create-components-fb65012e063f">Why We Gave Up on the Idea of Using Styled System to Create Components</a> was originally published in <a href="https://medium.com/quarkly">Quarkly</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>