<?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[DatoCMS - Medium]]></title>
        <description><![CDATA[The API-based CMS your editors will love - Medium]]></description>
        <link>https://medium.com/datocms?source=rss----e54f04e323da---4</link>
        <image>
            <url>https://cdn-images-1.medium.com/proxy/1*TGH72Nnw24QL3iV9IOm4VA.png</url>
            <title>DatoCMS - Medium</title>
            <link>https://medium.com/datocms?source=rss----e54f04e323da---4</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 02:46:00 GMT</lastBuildDate>
        <atom:link href="https://medium.com/feed/datocms" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[5 Reasons to Move Your Website from Wordpress to DatoCMS]]></title>
            <link>https://medium.com/datocms/5-reasons-to-move-your-website-from-wordpress-to-datocms-ab99f4904109?source=rss----e54f04e323da---4</link>
            <guid isPermaLink="false">https://medium.com/p/ab99f4904109</guid>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[content-management-system]]></category>
            <category><![CDATA[headless-cms]]></category>
            <category><![CDATA[wordpress]]></category>
            <dc:creator><![CDATA[Massimiliano Palloni]]></dc:creator>
            <pubDate>Tue, 23 Jul 2019 07:41:38 GMT</pubDate>
            <atom:updated>2019-07-23T07:51:57.918Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*V-WmIlB9v5o_iMgi8GBT2g.png" /></figure><p>Migrating a website from one CMS to another can seem painful and frustrating, but moving to the right CMS will improve your results and ability to grow online. There are <strong>various reasons to change Content Management System (CMS)</strong> for your online property. Here are the 5 best arguments to move your website to a headless CMS like DatoCMS.</p><h3>5 Reasons to Move Your Website from Wordpress to DatoCMS</h3><p>DatoCMS is one of the most prominent proprietary headless CMSs in the market. Compared to a traditional CMS, a headless solution doesn’t offer you a ready-to-use front-end.</p><p>In other words, it doesn’t provide a presentation layer for displaying your content to the end-user out of the gate. It’s about choosing between the convenience of a complete package or the <strong>unparalleled versatility of a headless CMS</strong>.</p><h4>Iron-clad Security without Maintenance</h4><p>It’s not true that all sites built on Wordpress are insecure. You can keep your platform safe by choosing the right hosting solution, installing only plugins from reliable sources and updating the platform as frequently as possible.</p><p>What is true, however, is that <strong>it takes work, time, and skills to attain these results</strong>. SaaS Headless CMS solutions <strong>take care of security and maintenance for you</strong> so you can focus on, well, managing and producing content.</p><p>DatoCMS serves content — images, text values — via an API to every platform of your choice without the need for you to manage a database like Wordpress. We do that part for you. No database means less unknown vulnerabilities and gateways that someone could exploit. All your dynamic content is safely stored and managed in your CMS, and you can even enforce two-factor authentication for sensitive content.</p><h4>It’s cheaper</h4><p>Yes, <strong>a paid SaaS subscription for DatoCMS is less expensive than a free Wordpress installation</strong>. How so? Well, premium Wordpress plugins are witnessing a price hike like never before. A reliable, competent hosting solution may even cost you thousands every year, even for smaller websites.</p><p>Do you know how much you would spend for a platform <a href="https://www.gatsbyjs.org/">built with a state-of-the-art site generator</a>, accompanied by a free and curated plugin library, and a <a href="https://www.netlify.com/pricing/">hyper-fast hosting solution</a>? <strong>Zero. Dollars.</strong></p><p>Need more? With a traditional stack, hosting and maintenance costs become prohibitive when your website attracts a considerable number of visits. With a headless CMS and a modern stack, the prices are so low it’s not even a fair comparison. <strong>Everything scales beautifully with an unparalleled price to performance ratio</strong>.</p><h4>It’s faster</h4><p>Ok, this is another point that requires a premise. There are sites built with Wordpress that show impressive performance, thanks to caching and aggressive image optimization techniques. Claiming that sites built using a headless CMS are always faster is marketing speak. However, a website built with DatoCMS, all things being equal, <strong>generally is faster than a traditional solution</strong>.</p><p>Headless CMSs tend to use a CDN out-of-the-box to serve data and images to users, offering response times lower than 20 ms. Moreover, <strong>a website built with a modern tech stack only has the code to run the front-end site and can more easily be optimized for speed</strong>.</p><h4>Focus on (real) content management</h4><p>The purpose of a CMS should be to manage structured content in a fast, transparent and effective way. Unfortunately, when a CMS also has the task of managing all the stack, there is a risk of favoring the final result for the end-user, losing sight of the real goal.</p><p>DatoCMS, thanks to the API-centered approach, allows you to manage your structured content and create transparent and effective relationships between them. You can reuse content on multiple devices and platforms, or import entire sections of one site into another in seconds. This speeds up production significantly, <strong>giving you a faster time-to-market</strong>.</p><h4>Flexibility above all</h4><p><strong>Traditional CMSs like Wordpress ask you to speak their language and be limited by their frameworks</strong>. DatoCMS is an API-first platform, which means it feeds content into any platform via a Content Delivery API.</p><p>Thanks to the power of GraphQL, <strong>every property can retrieve exactly the data it needs from the API, and nothing more</strong>. This way, developers can spend more time focusing on content creation and less on content management.</p><p><strong>They can build a front-end that makes sense for the project using their favorite framework and language</strong>. Being API-first also means that your CMS can communicate seamlessly with a wide range of services while remaining light in coding.</p><p>It would be foolish to say that a headless solution is for everyone; CMSs like DatoCMS still require developers at hand to turn your ideas into a final product. If you are comfortable with web development, though, don’t think twice!</p><p><em>Originally published at </em><a href="https://www.datocms.com/blog/5-reasons-to-move-your-website-from-wordpress-to-datocms"><em>https://www.datocms.com</em></a><em> on July 22, 2019.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ab99f4904109" width="1" height="1" alt=""><hr><p><a href="https://medium.com/datocms/5-reasons-to-move-your-website-from-wordpress-to-datocms-ab99f4904109">5 Reasons to Move Your Website from Wordpress to DatoCMS</a> was originally published in <a href="https://medium.com/datocms">DatoCMS</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to create a JAMstack site in minutes with Stackbit]]></title>
            <link>https://medium.com/datocms/how-to-create-a-jamstack-site-in-minutes-with-stackbit-c49951d4d982?source=rss----e54f04e323da---4</link>
            <guid isPermaLink="false">https://medium.com/p/c49951d4d982</guid>
            <category><![CDATA[jamstack]]></category>
            <category><![CDATA[stackbit]]></category>
            <category><![CDATA[web-development]]></category>
            <dc:creator><![CDATA[Massimiliano Palloni]]></dc:creator>
            <pubDate>Tue, 21 May 2019 07:28:58 GMT</pubDate>
            <atom:updated>2019-05-21T07:27:44.540Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Tt2pI0ecsr-TNiyzVMtEBw.png" /></figure><p>How long does it take to deploy a <strong>JAMstack site from scratch</strong>? For those used to work with Wordpress and other monolithic architectures, adapting to a completely different way of doing things could represent a time-consuming challenge.</p><p>I have good news though: this morning <strong>I published a JAMstack site in literally two minutes</strong> without writing a line of code or touching a single configuration file. No, I’m not using the term “literally” figuratively. I mean it. It took me two minutes and thirty-nine seconds to deploy a site from scratch.</p><p>Am I a wizard? No, quite the contrary! The lovely guys from <a href="https://www.stackbit.com/">Stackbit</a> and their new integration with DatoCMS deserve all credit for this. Stackbit allowed me to publish my blog in the time it takes to make a good coffee.</p><p>I just had to choose a theme, a static site generator and connect all my services while Stackbit did all the heavy lifting for me.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1vO1HMMqpWSIvY-ZG3ARPw.gif" /></figure><p>Stackbit is an excellent service even for those who are already familiar with the JAMstack architecture because it’s an easy and fast way to try new ideas in a matter of minutes.</p><h3>How to create your site in minutes with DatoCMS and Stackbit</h3><p>To get started, you must request an invitation for the <a href="https://www.stackbit.com/beta/">Stackbit beta</a> and make sure you have already an account on Netlify and Github.</p><p>When you have access to the <a href="https://app.stackbit.com/">Stackbit dashboard</a>, all you need to do is choose the name of your project and select one of the gorgeous themes ready to be used.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vDcFu0LLvHp9Vn3faeSEnw.png" /></figure><p>Then it’s time to decide which Site Generator to use; currently, Stackbit offers seamless support to <strong>Hugo</strong>, <strong>Jekyll</strong>, and <strong>Gatsby</strong>, but others will follow in the coming weeks.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*yx_nkAo5wjONP0vnZLUKMQ.png" /></figure><p>In the third step, you need to choose your favorite CMS — and we all know which one it is. <em>wink wink</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YdICvgVc_c9wgzGqXvh41A.png" /></figure><p>Now we just need to connect all the services and wait a few minutes; <strong>the site will be automatically created, pushed to Github and deployed on Netlify</strong>. After that, you can manage content from the DatoCMS Dashboard, set up your custom domain on Netlify, and customize the code pulled from Github.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*IKk3dL96LY-Y11lSFAa3XA.png" /></figure><p><a href="https://app.stackbit.com/wizard?theme=fresh&amp;cms=datocms">Start your new personal website with DatoCMS and Stackbit today!</a></p><h3>How to export your Medium blog to DatoCMS with Stackbit</h3><p><a href="https://medium.com/me/export">Exporting a blog from Medium is simple</a>, but sometimes it is challenging to offer your users an equally <strong>excellent reading experience</strong> when you switch to an open stack solution. For this reason, Stackbit offers you a tool to <a href="https://www.stackbit.com/medium/">import a blog from Medium</a> in a couple of minutes.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/830/1*aKfbImXhUBZG_r632bqohg.png" /></figure><p>Choose one of the Medium-compatible themes, select your favorite services, and deploy. That’s it. You will find all the contents you published on Medium in the DatoCMS dashboard at the end of the setup.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*j69nsDZRiFOpCG1MoY7b0g.png" /></figure><p>With a few tweaks, you will enjoy a fast, elegant, and usable version of your blog without writing a single line of code.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hMrFvNPF5dKsT_ubYRTAmg.png" /></figure><p>You can also <a href="https://app.stackbit.com/wizard?theme=fjord&amp;ssg=gatsby&amp;cms=datocms">try this theme</a> if you prefer to start your blog from scratch.</p><p>You can read more about the DatoCMS integration <a href="https://www.stackbit.com/blog/create-modern-sites-in-minutes-now-supporting-DatoCMS/">here</a>.</p><p><em>Originally published at </em><a href="https://www.datocms.com/blog/how-to-create-a-jamstack-site-in-minutes-with-stackbit"><em>https://www.datocms.com</em></a><em> on May 20, 2019.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c49951d4d982" width="1" height="1" alt=""><hr><p><a href="https://medium.com/datocms/how-to-create-a-jamstack-site-in-minutes-with-stackbit-c49951d4d982">How to create a JAMstack site in minutes with Stackbit</a> was originally published in <a href="https://medium.com/datocms">DatoCMS</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[4 SEO Jedi Tricks for your JAMstack Site]]></title>
            <link>https://medium.com/datocms/4-seo-jedi-tricks-for-your-jamstack-site-dd45fa2df1e3?source=rss----e54f04e323da---4</link>
            <guid isPermaLink="false">https://medium.com/p/dd45fa2df1e3</guid>
            <category><![CDATA[jamstack]]></category>
            <category><![CDATA[seo]]></category>
            <dc:creator><![CDATA[Massimiliano Palloni]]></dc:creator>
            <pubDate>Mon, 29 Apr 2019 12:40:44 GMT</pubDate>
            <atom:updated>2019-04-29T15:21:56.871Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*ScDsshB4Hxk6cWYZ" /><figcaption>Photo by <a href="https://unsplash.com/@kaleidico?utm_source=medium&amp;utm_medium=referral">Kaleidico</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>It is always challenging to explain to your non-technical colleagues what are the undoubted advantages of a JAMstack architecture compared to the old monolithic solutions. When it comes to SEO, however, the main advantage is obvious to anyone who knows enough about the subject: <strong>optimized static sites load so fast there is no competition with other traditional solutions</strong>. Moreover, there’s no more important factor for search engines than a website’s load times. We could end our blog post here, honestly: give your SEO team a super fast architecture, and they will be pleased as pie. There is more though: JAMstack offers a wide range of advantages to your team when it comes to optimizing and enhancing your content for a wide range of search engines. Here are four things to work on for a bullet-proof SEO!</p><h4>Work on structured data</h4><p>The <a href="https://en.wikipedia.org/wiki/Knowledge_Graph">knowledge graph cards</a>, <a href="https://developers.google.com/amp/">AMPs</a>, and <a href="https://ads.google.com/local-services-ads/">local ads</a> are voluntarily diverting users’ attention from organic results, thus reducing clicks on your website.</p><p>To tackle this problem, it is essential to work on structured data, making it easier for search engines to crawl, organize, and display your content. An excellent job on your structured data will give your search results a wide range of Rich Snippets, <strong>increasing your CTR by almost 30%</strong>. Schema markup also allows your content to appear in Knowledge Graph Cards and Rich Cards, two of the most popular search features of Google.</p><p>Static pages on a JAMstack architecture are already easier to understand for the crawlers because they love HTML static code, and adding JSON-LD markup to the source code it’s pretty straightforward. <strong>Most headless CMSs give you SEO tools to manage structured data from the get-go across all platforms</strong> (structured data is a deciding factor even for apps), but your editorial team and SEO specialists can manage schema markup on Google Tag Manager to make this process scalable across multiple pages. Just remember to use “History Changes” as a trigger instead of “Page Views” if you are using site generators like Gatsby or Gridsome because their sites behave like <a href="https://developers.google.com/analytics/devguides/collection/analyticsjs/single-page-applications">Single Page Web Apps</a>.</p><p>You can even write some basic scripts to inject structured data in your website dynamically; we added the code below to our blog, for example, to create structured data for every new post automatically:</p><pre>&lt;script&gt;<br> (function(){<br>  var data = {<br>   &quot;<a href="http://twitter.com/context">@context</a>&quot;: &quot;<a href="http://schema.org/">http://schema.org</a>&quot;,<br>   &quot;<a href="http://twitter.com/type">@type</a>&quot;: &quot;BlogPosting&quot;,<br>   &quot;mainEntityOfPage&quot;: {<br>    &quot;<a href="http://twitter.com/type">@type</a>&quot;: &quot;WebPage&quot;,<br>    &quot;<a href="http://twitter.com/id">@id</a>&quot;: {{Page URL}}<br>   },<br>   &quot;headline&quot;: {{SCHEMA - Article Headline}},<br>   &quot;image&quot;: {<br>    &quot;<a href="http://twitter.com/type">@type</a>&quot;: &quot;ImageObject&quot;,<br>    &quot;url&quot;: {{SCHEMA - Article Image}},<br>    &quot;height&quot;: 413,<br>    &quot;width&quot;: 1159<br>   },<br>   &quot;datePublished&quot;: {{SCHEMA - Article datePublished}},<br>   &quot;author&quot;: {<br>    &quot;<a href="http://twitter.com/type">@type</a>&quot;: &quot;Person&quot;,<br>    &quot;name&quot;: {{SCHEMA - Author Name}}<br>   },<br>   &quot;publisher&quot;: {<br>    &quot;<a href="http://twitter.com/type">@type</a>&quot;: &quot;Organization&quot;,<br>    &quot;name&quot;: &quot;DatoCMS&quot;,<br>    &quot;logo&quot; : {<br>     &quot;<a href="http://twitter.com/type">@type</a>&quot;: &quot;ImageObject&quot;,<br>     &quot;url&quot;: &quot;https:/datocms.com/datologo.jpg&quot;,<br>     &quot;height&quot;: 200,<br>     &quot;width&quot;: 200<br>     }<br>   },<br>   &quot;description&quot;: {{SCHEMA - Article Description}}<br>  }</pre><pre>var dateModified = {{SCHEMA - Article dateModified}};</pre><pre>if(dateModified){<br>   data.dateModified = dateModified;<br>  } else {<br>   data.dateModified = {{SCHEMA - Article datePublished}};<br>  }</pre><pre>var script = document.createElement(&#39;script&#39;);<br>  script.type = &quot;application/ld+json&quot;;<br>  script.innerHTML = JSON.stringify(data);<br>  document.getElementsByTagName(&#39;head&#39;)[0].appendChild(script); <br> })(document);<br>&lt;/script&gt;</pre><p>This is how it looks like live on <a href="https://search.google.com/structured-data/testing-tool">Google’s Testing Tool</a>:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*2t2T_I0p1vZCriiB" /></figure><p>You can do something similar for e-commerce, for example, shaving off hours upon hours of work on your SEO.</p><p>The <a href="https://schema.org/">schema.org</a> site helps to get a clearer idea of what you can do with your markup; the <strong>potentiality is limitless</strong>.</p><h4>Content Rich Pages</h4><p>One of the most central concepts in modern SEO is the importance of Content. “Content is King,” we always say, and we generally mean it. The problem is that in the race for visibility and pertinence, <strong>we have slowly but surely shortened the length of the content we produce</strong>. Although it is true that the attention span of an average user is at the lowest, recent studies show that longer pages produce more backlinks than short ones, also leading to a significant increase in average time spent on site. We have noticed, for example, that <strong>articles with more than 1,500 words have better results in Google’s ranking</strong>, thus leading to more organic visits over time.</p><p>The problem of static sites was until recently the lack for the writing team of a powerful and easy to use editor; today many headless CMSs offer intuitive tools to build visually compelling and text rich content in a matter of minutes.</p><p>DatoCMS makes it easy to build a tailored authoring experience for your editors and marketers thanks to its visual model builder and a super fast preview mode.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*YSv9W3urxQaSAn2WRlcGlA.gif" /></figure><h4>Keep it simple (and fast!)</h4><p>How we search for information on the internet has changed: according to Google <strong>1 research out of 5 go through a voice assistant</strong>. <a href="https://venturebeat.com/2017/12/11/deloittes-tech-predictions-for-2018-more-ai-digital-subscriptions-ar-and-live-events/">Deloitte</a> estimated over 250 million voice assistants were in our homes by the end of 2018. Voice-based technology is going to generate at least seven billion dollars in revenue this year. We are generally doing something else while searching with our voice, so our queries have a more natural and colloquial tone. Intercepting this kind of search pattern requires a significant change in keyword optimization strategies. <strong>Metadata may need long-tailed keywords consisting of multiple words</strong>, while texts that are too “literary” and overwritten will lose ranks on Google pretty fast.</p><p>Written content in 2019 should:</p><ul><li>be created with a specific research intent in mind, like a question (e.g., “Where can I buy museum tickets?” or “Where can I find the best prices?”);</li><li>be written in an informal tone that uses familiar and more natural words at least in the metadata that can be pronounced more efficiently;</li><li>employ highly specific keywords, even at the cost of making them very long.</li></ul><p>On the technical side, we need to remember that voice search is almost mobile only; if you want to see your pages ranked higher, your writing team needs a truly mobile-first website with a perfectly responsive front-end. Modern Static Sites are faster, more reliable and modular. A JAMstack architecture helps you strike a balance between ease of use and a platform-agnostic approach.</p><p>46% of users look to Facebook, Instagram, and YouTube when it comes to evaluating a purchase. <strong>As many as 70% of B2C companies have seen their revenue increase thanks to the much-reviled Facebook</strong>.</p><p>The way users consume content is the reason why Google and other search engines like Bing are increasingly rewarding content that shows the right level of engagement on multiple platforms. Like, retweets, social links, and shares are not just vanity points, but a litmus test of the desirability of your content.</p><p>Building and caring for your social presence helps not only to intercept your potential customers where they hang out the most but to bring quality traffic to the website.</p><p>Some bits of advice:</p><ul><li>Produce a balanced monthly editorial plan that contains a mix of useful, emotional and informative contents.</li><li>Monitor daily all your social accounts and make sure to promptly respond to user feedback in both private and public spaces.</li><li>Write easy to digest content with a clear message and a strong hook.</li><li>Make sure your content is ready to share, ensuring that your CMS can transparently manage Open Graph data.</li></ul><p>A headless CMS like DatoCMS helps you create compelling and social network-friendly content thanks to editable automatic meta tags for Twitter Cards and Facebook Open Graph.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*MH-7rf7gD1T2LbwYRhPMog.gif" /></figure><p><em>Originally published at </em><a href="https://www.datocms.com/blog/4-seo-magic-tricks-for-your-jamstack-site"><em>https://www.datocms.com</em></a><em> on April 29, 2019.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=dd45fa2df1e3" width="1" height="1" alt=""><hr><p><a href="https://medium.com/datocms/4-seo-jedi-tricks-for-your-jamstack-site-dd45fa2df1e3">4 SEO Jedi Tricks for your JAMstack Site</a> was originally published in <a href="https://medium.com/datocms">DatoCMS</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How a purpose-driven agency performs so well (with the right technology)]]></title>
            <link>https://medium.com/datocms/how-a-purpose-driven-agency-performs-so-well-with-the-right-technology-2f283026cc67?source=rss----e54f04e323da---4</link>
            <guid isPermaLink="false">https://medium.com/p/2f283026cc67</guid>
            <category><![CDATA[web-agency]]></category>
            <category><![CDATA[jamstack]]></category>
            <category><![CDATA[interview]]></category>
            <category><![CDATA[design]]></category>
            <dc:creator><![CDATA[Massimiliano Palloni]]></dc:creator>
            <pubDate>Wed, 27 Mar 2019 10:50:07 GMT</pubDate>
            <atom:updated>2019-03-27T22:51:55.812Z</atom:updated>
            <content:encoded><![CDATA[<p>“One of the fundamental conditions of happiness is to know that everything that one does has a meaning in eternity,” once said <strong>Titus Burckhardt</strong>, philosopher and supreme connoisseur of Islamic art, civilization, and culture. It is a quote that struck me as painfully real, even as a non-believer.</p><p>Self-fulfillment often seems to be entwined with the search for a higher meaning, a purpose that helps you leave the world better than you found it.</p><p>Curiously enough, Titus Burckhardt was born in Florence, like me, but was a Swiss citizen like <a href="https://www.linkedin.com/in/marca"><strong>Marc Ammann</strong></a>, with whom I believe he shares more than the passport color.</p><p>It is no coincidence that the word “purpose” was probably the most recurrent in my conversation with Marc, founder of <a href="https://mattersupply.co/"><strong>Matter Supply Co</strong></a>, a relatively new agency that <strong>lives and breathes purpose</strong> with an already impressive resume and a knack for JAMstack architectures.</p><h4>I read your <a href="https://mattersupply.co/us">bios</a>, and I really liked the way you all talked about your past experiences without overindulging in a long list of professional accomplishments.</h4><p>Yeah, we don’t like to talk about ourselves because our clients and good products come first. It’s a big item for us.</p><h4><strong>You and I also share the same passion for minimal techno, neurotic border collies and being called Max by others without reason. That said, would you like to introduce yourself to our fine readers?</strong></h4><p>Sure, I’m Marc, and I moved to the United States seven years ago to work at a creative agency called <a href="https://www.hugeinc.com/"><strong>Huge</strong></a> where I took on a technology director role. First I worked in New York on a few clients like <strong>Target</strong> and <strong>HBO Canada</strong> and then moved out to Portland with Huge to take over the Nike portfolio as a technology director and led a few interactive projects with Nike over four to five years, ranging from in-store/kiosk experiences, apps, websites, and companion sites.</p><p>After four and half years I thought it was time for a change and I asked my company to give me a separate role, so I ended up taking on a team in Colombia and got involved with our development team in Medellin. I started setting up best practices and a leadership-focused management training program, then Huge closed their Portland office, and I decided at that point to start my own company. I was like “Hey, I can do better than what I’ve done before moving to the US; I can build a better team, <strong>I can build a purpose and value driven agency</strong>,” so I asked <a href="https://www.linkedin.com/in/joshuareds/">Josh</a> — my co-founder and former colleague at Huge — to join me that same day. The same day I also got a call from one of the leaders in the Medellin office [<a href="https://www.linkedin.com/in/aguirrerozzo">Edgard Aguirre</a>] who asked me what I was intending on doing after Huge and I was like “wow, what a coincidence.” I said “I’m starting my own company” and he asked me if he could join right away!</p><p>That was the three of us who started this little agency two years ago. We grew from three people to 26 as of yesterday, and we’re working with a lot of fun clients, like <a href="https://impossiblefoods.com/"><strong>Impossible Foods</strong></a> which is one of our biggest ones.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Ulxv6HZkEbqpaOXzOq4yvg.png" /></figure><h4><strong>Wow, a big client indeed!</strong></h4><p>One that we’re also trying to move to DatoCMS, by the way…</p><h4><strong>Do you have other customers you love to work with?</strong></h4><p><a href="https://www.sweetgreen.com/"><strong>Sweetgreen</strong></a>, for example, it’s a restaurant chain specialized in sustainable and local dishes. They serve high-end salads at an affordable price.</p><p>We also had the chance to work with <a href="https://unitedwedream.org/"><strong>United We Dream</strong></a> as well, developing an app for DACA recipients, or “DREAMers” as they call them in the United States. DACA enables children of undocumented immigrants to remain in the country for two years and shield them from deportation.</p><p>We are lucky enough that <strong>all our clients have amazing mission statements</strong>, people who are actually trying to do the right thing.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hH1L2LPsEn6LPwNe6Hk0KQ.png" /><figcaption>Sweetgreen’s Android app</figcaption></figure><h4><strong>How important is it to work with clients who share similar values with you?</strong></h4><p>I think it’s essential, especially if you look at what the team wants to do. If you create an incredibly purpose-driven squad, you cannot stop or just undercut them when they work with the client. You can’t say you are a mission-driven and purpose-driven team when your clients are not. It just doesn’t work that way, and the passionate people you employ will walk away.</p><p>So far we looked for clients with a powerful mission statement because it’s easier to work with like-minded companies.</p><p>It also comes down to us believing in that mission; if leadership is cynical or doesn’t believe in the purpose of the client, it trickles down to the whole company with disastrous results. Luckily it hasn’t happened to us [smiles].</p><h4><strong>As an agency, who is your ideal client?</strong></h4><p>Do you mean the client itself or what we can do for them?</p><h4><strong>Both?</strong></h4><p>Ok, the ideal client would be somebody who wants to be successful at doing the right thing, somebody who cannot rest themselves. Companies like Apple and Google are fun clients, sure, but they’re already at the top of the pyramid, and while you can do a lot of exciting things for them, they need to be careful that they don’t become the “number two.”</p><p><strong>Working for the underdog is a lot more rewarding</strong> because you can usually push quite a bit more, you can approach things from an iterative perspective and take some risk.</p><p>That being said, I think we’d love to work with a client like Lego. Lego is like one of our “white whales.” I also would like to work with the New York Times or the Washington Post, because they do such fantastic journalism that I think it’s well worth supporting professionally. We’re small for now… but we’re getting there [smiles].</p><h4><strong>We saw one of your most recent works for </strong><a href="https://justdoit.nike.com/"><strong>Nike</strong></a><strong>, and we loved the way it enters boldly in the global conversation about empowerment, redemption, and change through sport and self-expression. Can you tell us something about your experience working on it?</strong></h4><p>There’s a kind of two tales. For one we were able to build this within a short time: this current site and the last were both made within two weeks of getting started with design. As a product, it goes relatively quick but the message behind it, what you see the team in Nike doing, it’s incredible. From the outside, it may seem very cynical, but when you work with the incredible mission-driven team over at Nike, <strong>you understand it’s not about the bottom-line</strong>, at all. You see, the shop is the last item on the list; it’s all about the fact that there are many women out there whose stories need to be heard and it’s well overdue for them to get the stage they deserve. It really resonated with us.</p><p>I have to be honest: after four and a half years on Nike at Huge I was burned out; I was like “Yeah, these are just ads for shoes and sneakers, whatever, they don’t believe in anything.”</p><p>Since we started working with them here, we were able to collaborate with some of the teams in Nike that are really trying to push these things, and I think <strong>Nike can really make a difference</strong>. They own up to that right now.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*AIMmHpnd9iTWsdm-.gif" /></figure><h4><strong>Why did you choose to use a JAMstack architecture for this project?</strong></h4><p>So we used Contentful before, in a previous experience, but Nike wasn’t too fond of it. We needed something more focused on the user experience, with user-friendliness in mind, and that works incredibly well and looks good.</p><h4><strong>Do you think it is important that a CMS is pleasant to look at?</strong></h4><p>It’s critical! If the CMS doesn’t look good, you can’t win your client over. <strong>The CMS also needs to feel nice, light, and easily accessible for the clients when they update their content</strong>.</p><p>Obviously, you need excellent scalability; for the Nike project we saw 200,000 visitors per day all of a sudden, so if you can’t scale to that you’re in big, big trouble.</p><p>The easiest way to scale is a static site because you can deploy it to something nice like Netlify, something that scales well, but then the CMS component came into that as well.</p><h4><strong>Why did you choose DatoCMS?</strong></h4><p>We were like “You know what, we’re gonna try something new, we’re gonna try the runner-up to the big Contentful.”</p><p>When I saw that you were backed by an agency I said to myself “well, these guys actually know what they need.” <strong>This is precisely what I want: a CMS that’s been built by an agency because they know what my clients need</strong>. We tried DatoCMS, and the team loved it; it felt good, it felt very nice, and our team at Nike has been super happy with it.</p><blockquote>This is precisely what I want: a CMS that’s been built by an agency because they know what my clients need.</blockquote><h4><strong>How’s the stack holding up?</strong></h4><p>I was talking with Netlify yesterday how everything has held up exceptionally well with multiple timed content deployments. <strong>I cannot thank you enough for </strong><a href="https://www.datocms.com/blog/scheduled-publishing-during-christmas"><strong>Scheduled Publishing</strong></a> because at Nike they publish their content at 6:00 in the morning and I do not want to get up so early anymore. With Time Publishing I know that when a new video goes live, all I need to do is look at Slack and see that the deployment has finished and then go back to bed.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/0*_C7P_oe7DwegRuHC.gif" /></figure><h4><strong>Was it challenging to sell your clients on the idea of JAMstack?</strong></h4><p>No no, <strong>they get it immediately</strong>. Sure, it’s a little bit harder to pick a solution that’s not Enterprise-focused, because it’s not like an SLA offering where you get that big contract, and you put it in front of your client.</p><p>Nike, fortunately, gives us a lot of free rein in terms of technology as long as we get the job done. Funny enough, <strong>the bigger the client, the less they care about what you use</strong> because if you mess it up, that is the last project you do with them.</p><blockquote>Funny enough, the bigger the client, the less they care about what you use because if you mess it up, that is the last project you do with them.</blockquote><h4><strong>What’s your favorite feature of DatoCMS? Mind you, “I can switch it off” doesn’t count!</strong></h4><p>I think <a href="https://www.datocms.com/features/"><strong>Modular Content</strong> is probably one of my favorite features</a>. Being able to put together a piece of content that the client can see on one page and think: “<strong>hey, this gets very close to Squarespace</strong>.” It’s what all clients want: to have something like Squarespace but somehow better, even if it’s an unfair comparison given its success. DatoCMS comes close to that feeling when you can put content together very quickly.</p><p><strong>Modular Content hands down has convinced Nike that DatoCMS was the best solution we could come up with</strong>.</p><p>The integration with <a href="http://gatsbyjs.org/">Gatsby</a> has also been great, for example, the Image integration via GraphQL; thank god it’s there! I also like <strong>the </strong><a href="https://www.imgix.com/"><strong>Imgix</strong></a><strong> integration that you provide transparently</strong> where we just have to send the Imgix parameters through, and we’re good. All that has been great, and we love it. The entire team loves it.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/964/0*EwLMwScBEBZRO4hQ.gif" /></figure><h4><strong>Why did you choose Gatsby for your project?</strong></h4><p>Because we’ve used Gatsby on Impossible Foods and a bunch of other sites for the static generation. We use a lot of React and Gatsby is perfect for building them and getting the stack under control. We think it is a really good product.</p><h4><strong>Is there an internal project you’re working on you can talk about?</strong></h4><p>We’re building a few things internally, and one is an animation framework with a bit of a holistic approach for our animations and transitions. We have always been a very interactive-focused agency and what is available now for React has forced us to take a step back in terms of providing the interactivity we need. There is a lot of internal drive to make this happen.</p><p>There are a few other things I probably get my wrist slapped if I talk about them, but I can say there’s a more significant initiative for us to <strong>create our own big GraphQL API</strong> that we can use to build everything we need to and deploy for our clients.</p><p>I think working with DatoCMS has inspired us to take a look at what services we need all the time that we should build for all of our teams/clients.</p><h4><strong>If a kid walked up to ask for your advice on starting an agency and you only had a few minutes to give them your best tip, what would it be?</strong></h4><p>Even if people make mistakes or fail, try to make sure you know what you can do to make the situation better next time and understand that <strong>your team matters more than the work it produces</strong>. As a leader of a creative team, it’s your job to create room for people to make mistakes and let them try again. Always give feedback on the task without attacking the person; it’s a piece of simple advice but really crucial.</p><p>Another thing is proactivity: <strong>you either create your own problems or you wait long enough for the problems to catch you</strong>, and I’d rather err on the side of creating my own problems and start things early.</p><p>Do I have another minute?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3FvinEiP1Knn1m9wB8GPVA.jpeg" /><figcaption>Part of the Matter Supply Team</figcaption></figure><h4><strong>Sure!</strong></h4><p>Understanding that <strong>there’s a difference between proficiency and creativity</strong>. That’s probably one of the more significant learnings, really. Creativity means you create room for people to fail and try again; proficiency means you’re making sure that people get better at what they do.</p><p>Those are two separate things, and you need to figure out where you stand on how you run your company. <strong>You can lead for both but you need to understand where you draw the line</strong>, and it needs to be clear and straightforward for people to understand.</p><h4><strong>Where’s your line?</strong></h4><p>I’d say about sixty percent creativity and forty percent proficiency. Matter Supply is a creative technology + product design practice, so it makes sense, but we also have another agency that’s more of a production studio called <strong>Outpost</strong>, and I’d say it’s eighty percent proficiency and twenty percent creativity.</p><p>At Outpost we get better by doing the same thing over, quality through iteration, really.</p><blockquote>Creativity means you create room for people to fail and try again; proficiency means you’re making sure that people get better at what they do.</blockquote><h4><strong>How would you introduce DatoCMS to the same kid as before?</strong></h4><p>I would call it a <strong>Swiss Army Knife</strong>. If you need a pragmatic CMS that allows you to work fast without standing in your way, providing all the tools you can possibly need to make a good experience happen, <strong>DatoCMS is there for you</strong>.</p><p>I think there’s a lot that could be added, but everything that you need is already there to build everything yourself: there’s enough duct tape, there are enough knives, there are enough zip ties to make everything work as you need it to on top of a seemingly rock-solid foundation.</p><p>Get inspired by Matter Supply’s work on its <a href="https://mattersupply.co/work">official website</a>.</p><p><em>Originally published at </em><a href="https://www.datocms.com/blog/purpose-driven-agency-interview-matter-supply"><em>www.datocms.com</em></a><em> on March 26, 2019.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2f283026cc67" width="1" height="1" alt=""><hr><p><a href="https://medium.com/datocms/how-a-purpose-driven-agency-performs-so-well-with-the-right-technology-2f283026cc67">How a purpose-driven agency performs so well (with the right technology)</a> was originally published in <a href="https://medium.com/datocms">DatoCMS</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Interview with Jeff Escalante: how HashiCorp gets the best out of DatoCMS]]></title>
            <link>https://medium.com/datocms/interview-with-jeff-escalante-how-hashicorp-gets-the-best-out-of-datocms-dcf29b95ba6e?source=rss----e54f04e323da---4</link>
            <guid isPermaLink="false">https://medium.com/p/dcf29b95ba6e</guid>
            <category><![CDATA[nextjs]]></category>
            <category><![CDATA[jamstack]]></category>
            <category><![CDATA[headless-cms]]></category>
            <category><![CDATA[hashicorp]]></category>
            <category><![CDATA[web-development]]></category>
            <dc:creator><![CDATA[Massimiliano Palloni]]></dc:creator>
            <pubDate>Thu, 07 Mar 2019 11:11:39 GMT</pubDate>
            <atom:updated>2019-03-07T11:09:04.107Z</atom:updated>
            <content:encoded><![CDATA[<p>Relationships shape us, make us collectively stronger and more able to achieve goals that we thought impossible. Curiously enough, the same applies to software. The relationship between DatoCMS and one of our repeat customers and frequent collaborators, <a href="https://jeffescalante.com/">Jeff Escalante</a>, has allowed our CMS to grow, improve and respond to the needs of a fast-growing company like HashiCorp.</p><p><a href="https://jeffescalante.com/">Jeff </a>has been a staunch believer in static development for years, and he’s made it a signature approach in his work in both of his last two roles.</p><p>We’ve been fortunate to partner with Jeff for quite a while, first at Carrot and now with the team at <a href="https://www.hashicorp.com/">HashiCorp</a>, so we asked him to sit down with us for an informal chat. Read below to find out what spell-slinging secrets we have managed to extract from him along the way.</p><h4>Let’s pretend we don’t know you, Jeff. What is HashiCorp and what do you work on?</h4><p><strong>HashiCorp is a cloud infrastructure automation company</strong> aimed at provisioning, securing, connecting, and running cloud infrastructure for complex applications. All of our products are open source, and we take great pride in this, and in our <a href="https://www.hashicorp.com/our-principles">cultural</a> and <a href="https://www.hashicorp.com/tao-of-hashicorp">working</a> principles.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4YUEfe-2zmCTtqhOyh3ICQ.png" /></figure><h4>Why did HashiCorp choose DatoCMS?</h4><p>Well, it’s a long story, actually! My previous job was at an agency called Carrot (now <a href="https://www.virtueworldwide.com/">Virtue</a>), we specialized in advanced static builds. We also had plenty of experience in managing multiple websites under single larger brands.</p><p>As an agency, every job was different from the last, and we needed tools that could be recycled for different projects, to keep our staff productive and foundations consistent. In choosing them, <strong>we had to find a careful balance between quality and flexibility</strong>. We needed our tools to be trustworthy but also able to cope with a wide variety of situations without falling apart.</p><h4>Choosing the right CMS for an agency does seem like a tricky proposition.</h4><p>Yes, it does. Some CMSs are very good, but their user experience is fairly confusing, especially as you get to more complex scenarios with a lot of linked relational records. Finding the right pricing scheme is also problematic: some solutions are geared exclusively towards enterprises, so it’s almost impossible to use a CMS for a smaller organization or product without taking very high risks. And others are aimed more at very small companies, so enterprises are reluctant to trust them. Having to navigate this divide was something that often put us in a really uncomfortable position with our clients.</p><h4>Which features were the most important for your agency?</h4><p>Agency clients are often demanding and if something can be asked for, it will. So we needed flexibility, sure, but we also needed <strong>really good control over validation</strong>. A lot of CMSs are not built to be put in the hands of non-technical clients for extended periods of time, so you’ll watch a site crumble as a result of clients slowly breaking all the rules, like uploading a 10 MB image or pasting three paragraphs of text in a headline. We took great pride in building high quality software that would last, so we couldn’t let this happen.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2Kd89HlBVfDhVmFz0MTfwA.png" /></figure><h4>Then you adopted DatoCMS…</h4><p>Yes, <strong>we ended up finding a really good balance in Dato</strong>. It has a lot of flexibility, a good pricing range that accommodates both large and small projects, a great user experience even with deeply linked records, and a very thorough API.</p><p>From that point on, most of the projects that came in at Carrot were built with DatoCMS. At one point, we pitched to HashiCorp to become a client — they wanted a static site and a headless CMS to manage multiple different properties, sharing assets, design and code through a wide range of products, which is right in the zone of projects we loved. We did end up partnering with them and after an exhaustive research and evaluation process, moved forward with Dato, which was exciting for us both.</p><p>A few months later, some structural changes within the company resulted in Carrot being absorbed into Virtue and the development department scaling down. Around this time, HashiCorp came in and offered me a position on their digital team, which I happily accepted as we had a great relationship and I had been doing exciting work on their web properties.</p><h4>Did you end up bringing DatoCMS with you?</h4><p>I sure did! During my time at Carrot, we rebuilt <a href="http://www.hashicorp.com/">hashicorp.com</a> from scratch, using Dato as the CMS. When I switched from working for HashiCorp through Carrot to working for them directly, the team and I continued to invest deeper into improving the site and its integration with Dato.</p><h4>How was the transition to DatoCMS for HashiCorp?</h4><p>The DatoCMS transition process is something that has always attracted us from the beginning, because <strong>its API is one of the most extensive</strong> among the many headless CMSs I have evaluated.</p><blockquote>The fact that it was so thorough made us a lot more confident in making the switch: I knew that anything that existed within the old CMS could be migrated over by writing a script.</blockquote><p>So while the migration was tough and took us a while, as any major system transition will, it was mostly because of issues we had with our previous CMS — everything about the integration with DatoCMS was quite smooth.</p><h4>What is your current static site generator of choice?</h4><p>We are currently using <a href="https://middlemanapp.com/">Middleman</a>, a really great piece of software in general and an excellent static generator. But as the company continues to grow, we have added more and more pages that we’re generating and more shared React components that comprise the majority of our sites’ markup. Working with an extensive React-based component system on top of a Ruby based static site generator is quite difficult. It has required us to implement several hacks to work around the transition between Ruby and Javascript, and the build time is very slow because of this. So at the moment, we are in the middle of a pretty extensive refactor and we need to move to a JavaScript-based static site generator in order to get a closer integration for these components.</p><p>At the moment, we are planning on building a more opinionated configuration layer on top of <a href="https://nextjs.org/">Next.js</a>, and taking it from there, and it has been a really big improvement in our proof of concept testing so far.</p><h4>Why Next.js?</h4><p>There are a few big reasons. First, since we have this global shared component system built with React, it makes sense for us to use an architecture that is based on Javascript and integrates well with React. We have a lot of sites with a lot of pages, so in order to keep performance strong, we prefer a server-rendered architecture with code splitting, which is exactly what Next gives us.</p><p>On top of that, you can generate a static site or run your own node server with exactly the same codebase. This feature is killer: it gives us the flexibility to start simple, and not worry about massive refactors or technology changes as projects begin and mature, also allowing us to maintain different services using the same foundation.</p><p>For example, our docs pages are likely to stay static for a while, but other sites we work on like our <a href="https://learn.hashicorp.com/">learning</a> and community portals will have user logins from the get-go and be better fit as dynamic sites. With Next, we can use the same architecture for both of these types of sites, which makes our developers much more productive.</p><h4>To gain a little flip switch and go from a static to a dynamic site without changing the architecture or changing the platform is really big.</h4><p>Yeah, that’s really the defining feature for us with Next.js.</p><h4>Are there any other interesting things you’re doing with the new architecture?</h4><p>Yeah actually, we just finished the prototypes of our data loading infrastructure, and we’re really taking advantage of <a href="https://www.datocms.com/docs/content-delivery-api">DatoCMS’s GraphQL API</a> for this. Previously, we would pull all of the data from DatoCMS then build the site using that, but as we added more and more relational content, this process got slower, to the point where just requesting a full copy of all our data would take a couple minutes. On top of that, we have a lot of sites that don’t use <strong>all</strong> the data we have in the CMS — they might just pull the data to render our shared footer, which appears on all sites. It was a big waste of time.</p><p>GraphQL really takes care of that concern for us, and <strong>lets us very quickly go to DatoCMS to pull just what we need for the site being built</strong>, while still taking advantage of Dato’s first-class relational records, which we utilize heavily for things like holding on to links between companies, products, talks, videos, blog posts, and everything else to make filtering and finding what you want easy for users, and surfacing related content easy for us.</p><p>Right now, each page sits in a folder with a couple files: a JS React component for the markup, a CSS file for the styles, a GraphQL file that contains the query for the data the page needs, and typing for TypeScript. This structure is wonderful — concerns are nicely separated but still easily found in the same place. When the page renders, we go to DatoCMS and get the data needed to render it.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/900/1*_poLDXtRR7RQO5DlQ3dhNg.png" /></figure><p>The TypeScript thing is also really great and takes advantage of how good a job DatoCMS has done with the GraphQL API. We have a script set up to call <a href="https://github.com/apollographql/apollo-tooling#apollo-clientcodegen-output">Apollo Codegen</a>, which looks at our components and Dato’s GraphQL schema, then it will automatically generate typings for our components and the data it uses. So we get the benefits of strict type checking without ever needing to write out any types because of these brilliant tools.</p><h4>There are a lot of people working on the site every day, how are you managing the risk of something going wrong?</h4><p>We are running HashiCorp’s sites through <a href="https://www.netlify.com/">Netlify</a> and it provides a nice layer of security, notifying us if a deploy fails for any reason. If somebody pushes content that our code can’t handle or we didn’t set up enough validations to catch, the build will fail, no error will go live, and we can fix the issue, add the necessary validations and patch it.</p><p>Dato’s integration with Netlify is great, <strong>it’s a little bit easier than any other CMS where you need to manually wire up the webhook</strong> , since you just click a button and it connects directly to Netlify.</p><p>And on top of this, of course we have a large suite of unit and integration tests, and we also use <a href="https://www.bugsnag.com/">BugSnag</a> to try to stay on top of any exceptions that occur in production.</p><h4>Speaking of webhooks, how are you using them?</h4><p>As I said before, the site is growing bigger every day and the compile time is starting to slow down. To cut it down we came up with an interim solution: we have a dynamic server with a good caching system that renders the content-heavy portions of the site, which for us are the blog and the resources page.</p><p>Within Dato, <strong>we use webhooks to hit that server when there’s a deployment so that it can refresh its cache and download the latest from Dato</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_deHxXHDjPT29o_CJcrxXQ.png" /></figure><h4>What do you think of our deployment environments?</h4><p>HashiCorp is moving towards having all of their sites and content consume data from a single DatoCMS instance to promote cross-linking of data and reduce user confusion switching contexts. When that happens <strong>we’ll be deploying ten or more sites off the same instance of Dato, setting each of our specific product sites as different environments.</strong> We already have ~4 deploying from our master instance, and we are constantly working on upgrading more of the company’s sites to take advantage of this.</p><p>Anyone with access can go to the build menu and create a deploy to the target project site so it will just deploy that site and that site only. Because of this we get quicker deployments, and a reduced risk of something being accidentally deployed to the wrong place. The environment thing is really big for us — we were all super excited when it came out, and immediately implemented it for several sites.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*HdULdV6OkBXWJ2LoJR0_cQ.png" /></figure><h3>What are you working on right now?</h3><p>A ton! In addition to our Next.js-based architecture refactor, we’ve been trying to come up with a system in which we can use a standard set of models to allow non technical people to create pages from scratch — “template pages”, as we named them. We are calling this the “section block system”, and will definitely do a more detailed writeup as we refine it more.</p><p><strong>This type of system is the “holy grail” of CMS-based websites</strong> — a system in which non-developers can create new pages that look great, perform well, and satisfy stakeholder needs. It’s something that many have attempted, but is incredibly difficult — there’s a fine line between too much flexibility, which can lead to poorly designed/engineered or off-brand pages being pushed through without approval, and too strict of user controls, which makes the system kind of useless — if it’s not flexible enough to get a wide range of messages across, people will come to the dev team to ask for custom pages instead of using the system.</p><h4>The problem ultimately lies with trusting your CMS users, right?</h4><p>That’s right, and unfortunately you can’t really trust your users to figure things out — you need to set intelligent constraints to keep them from doing anything wrong. Anyone who has worked with CMSs for a while knows that Murphy’s law applies here to the fullest: if there’s something a user can do in a CMS, they will do it. We have seen every range of attempted hack from putting 1000 words into a headline to changing a jpg file extension to “.svg” just to satisfy an image requirement. So validation is a big part of it.</p><p>We’re also trying to figure out how to create a system to balance layout orientations of the sections of a page, then within each layout zone have standard components that react well to things around them, and making it so that the only options you can choose are carefully built and tested, on-brand components, but that the components are flexible enough to allow a variety of different types of layouts and presentations.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*isSFp9IRrgROWbd8v_L8zg.jpeg" /></figure><h4>You should do some DatoCMS plugin in the meantime, you know, for science…</h4><p>Actually, we’re really excited about DatoCMS plugins too! This is a feature that is going to help us out a lot, because we won’t have to adapt our system to the way DatoCMS interface works no matter what. With plugins, we can just write our own micro-interface that works best for our specific system and basically embed it within Dato, which is awesome! <strong>It’s like having a custom built CMS, except DatoCMS takes care of all the hard parts</strong>.</p><p>We are also thinking about integrating pull in our React component library and doing live content renders within them… I mean, <strong>the sky is the limit with that kind of stuff</strong>!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*TVu4wxWs5ZdWQNZi-IoS9g.png" /></figure><h4>We know you’re an efficiency monster: what are you doing to cut response times?</h4><p>We’re thinking about a way to do partial cache updates. In order to do this, we would have to get back from DatoCMS both what we have updated in the most recent deploy and a full map of everything that has a relation to every item, so that we could validate accurately. Kind of like a dependency tree, except for data that has been changed in the CMS. With this, we could make really fast and efficient cache refreshes with Dato.</p><h4>Is it…?</h4><p>Yes, an additional feature request in the middle of the interview! <em>[laughs]</em></p><h4>Well, your ideas have always helped us improve DatoCMS. Some of the features we released, like <a href="https://medium.com/datocms/scheduled-publishing-the-perfect-way-to-manage-your-content-during-christmas-b544d46b0354">Scheduled publications</a> and <a href="https://www.datocms.com/blog/introducing-record-drafts/">Draft/Published records</a>, were requests we received from you.</h4><p>When we were doing our initial evaluation for HashiCorp between DatoCMS and other leading headless CMS providers, the <strong>importance of a good work relationship was something that came up as a major point</strong> , because I had worked with some other CMSs for years and they just didn’t listen to our feedback.</p><p>When you work with a company this closely, working on the CMS that powers your website, you need a partner that you have really good communication and a great relationship with, to make sure that we’re getting stuff done.</p><p>We are beyond excited about the close relationship we have built between DatoCMS and HashiCorp. It’s really amazing. More than once, <strong>we have asked “Hey, can we have this thing?” and next day we get back a response, “Oh yeah, here it is”. Unbelievable</strong>.</p><blockquote>It’s astounding that you’re able to listen to everybody’s feedback, not just ours, and act on it while still being such a small, bootstrapped company. Especially when there are giant competitors with hundreds of employees and million of dollars in the bank that just can’t put an ear to the ground and hear what their community is asking.</blockquote><h4>Aww, thank you!</h4><p>If you want to know more about Jeff and his work, drop him a line <a href="https://twitter.com/jescalan">on Twitter</a>. He’s always a friendly human being. And a competent, knowledgeable developer, so that’s a plus.</p><p>In case you want to know more about DatoCMS, <a href="https://dashboard.datocms.com/signup">try our demo</a>. It’s free and super cool, really.</p><p><em>Originally published at </em><a href="https://www.datocms.com/blog/how-hashicorp-gets-the-best-out-of-datocms"><em>www.datocms.com</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=dcf29b95ba6e" width="1" height="1" alt=""><hr><p><a href="https://medium.com/datocms/interview-with-jeff-escalante-how-hashicorp-gets-the-best-out-of-datocms-dcf29b95ba6e">Interview with Jeff Escalante: how HashiCorp gets the best out of DatoCMS</a> was originally published in <a href="https://medium.com/datocms">DatoCMS</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Scheduled publishing, the perfect way to manage your content during Christmas]]></title>
            <link>https://medium.com/datocms/scheduled-publishing-the-perfect-way-to-manage-your-content-during-christmas-b544d46b0354?source=rss----e54f04e323da---4</link>
            <guid isPermaLink="false">https://medium.com/p/b544d46b0354</guid>
            <category><![CDATA[scheduling]]></category>
            <category><![CDATA[wev-development]]></category>
            <category><![CDATA[publishing]]></category>
            <category><![CDATA[christmas]]></category>
            <category><![CDATA[deployment]]></category>
            <dc:creator><![CDATA[Francesco Falchi]]></dc:creator>
            <pubDate>Thu, 13 Dec 2018 17:31:00 GMT</pubDate>
            <atom:updated>2018-12-13T21:26:13.881Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Qb21Yrb2ZtiBClyuvKcG2g.jpeg" /></figure><p>Christmas is not here yet but DatoCMS has already a gift for you, Scheduled publishing.<br>It happens more often than not that you might want to publish one of your records but you aren’t available at the time you want to publish it. It’s probably going to happen during vacation time like Christmas.<br>Fear not because from now on you can set up you records publication even if you’re not there to press the “Build now” button.</p><h4>How to set up a Scheduled publishing</h4><p>We’re going to create two simple articles and schedule the publishing of the first one during Christmas and the second one for the new year.<br>To start we’ll create a “Festivity” model.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ZmUy2kHfHkuQF78049iyAQ.png" /><figcaption><em>Some of the fields you might need for your related to festivities model</em></figcaption></figure><p>Remember to enable the draft/published system in the additional setting of your model.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*IkfJ7CoXc6298lDtLwyUrQ.gif" /><figcaption><em>You need the draft/published system to be active to be able to use the Scheduled publishing</em></figcaption></figure><p>Now we can move on to create our records.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/954/1*61B3VTbcfAlcU-tElvsyHA.png" /><figcaption><em>Our New year festivity record</em></figcaption></figure><p>When we save it we have our New year post ready but nobody will be there to publish it at 12AM of the first of january.<br>We can set our scheduled publishing to be sure the post will be out.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*MYZecJp_A8aEJduIO1J-GQ.gif" /><figcaption><em>Setting up the publication date is really easy</em></figcaption></figure><p>You’ve probably noticed that the publication time is set to GMT(London) because that’s the time set on the Global project settings of our project, but our computer is actually in a different time zone.<br>Keep that in mind if you’re working remotely or in a different timezone than the the one set in the project.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/289/1*0km4wAWZk-Y_HHuyPkPr1g.png" /><figcaption><em>In our case we’re at GMT +1, we’ve set the publishing an hour earlier. If we were in London the notification about the Timezone would not show up</em></figcaption></figure><p>You can check the release time in your collection by selecting the “Scheduled publishing at” in your Tabular view.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/1*iASdTFbNVu7aFdy27hkTDA.gif" /></figure><h4><strong>Your environment is part of the process</strong></h4><p>If you’re using our <a href="https://www.datocms.com/docs/content-delivery-api/">CDA</a> client side (with React, Vue, Angular, you name it) or your DatoCMS project is server-side (using Rails, Node.js, Elixir, PHP or any other solution of your choice) and it’s using our Content Delivery API, the records will be available at the scheduled time.</p><p>Otherwise if you have a static site project, the last step is to enable Scheduled publishing in our environments so that they can deploy properly.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/1*55NsILPs586v5g4BfLZotA.gif" /><figcaption><em>Remember to select the right environment if you have more than one!</em></figcaption></figure><h4><strong>A request from the future</strong></h4><p>Many projects might need more than a single record to be released at the same time, for example if you have magazine that is going to release several article a specific day per month.</p><p>In the near future DatoCMS will expand Scheduled publishing capabilities to enable the release of several records at the same time.</p><h4><strong>Enjoy your vacations</strong></h4><p>Now you’re ready to enjoy Christmas and New year’s eve without the stress of pressing deadlines, go out there and break a leg!</p><p><em>Originally published at </em><a href="https://www.datocms.com/blog/scheduled-publishing-during-christmas/"><em>www.datocms.com</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b544d46b0354" width="1" height="1" alt=""><hr><p><a href="https://medium.com/datocms/scheduled-publishing-the-perfect-way-to-manage-your-content-during-christmas-b544d46b0354">Scheduled publishing, the perfect way to manage your content during Christmas</a> was originally published in <a href="https://medium.com/datocms">DatoCMS</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to create an inverse relationships plugin on DatoCMS]]></title>
            <link>https://medium.com/datocms/how-to-create-an-inverse-relationships-plugin-on-datocms-253e7370aedc?source=rss----e54f04e323da---4</link>
            <guid isPermaLink="false">https://medium.com/p/253e7370aedc</guid>
            <category><![CDATA[headless-cms]]></category>
            <category><![CDATA[plugins]]></category>
            <category><![CDATA[coding]]></category>
            <category><![CDATA[building]]></category>
            <category><![CDATA[web-development]]></category>
            <dc:creator><![CDATA[Irene Oppo]]></dc:creator>
            <pubDate>Thu, 22 Nov 2018 17:01:02 GMT</pubDate>
            <atom:updated>2018-11-22T17:01:02.675Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*L6yOwnLz3ny50bylkMFe_Q.png" /></figure><p>Just a couple of weeks ago we released the <a href="https://www.datocms.com/blog/build-the-perfect-cms-introducing-plugins/">Plugins SDK</a>, that enable the developers community to fully customize every project’s administrative area.</p><p>Let’s say we have a project that has, for example, an Author model and a Post model and each post is linked to an author by a single link field. In DatoCMS we can see which author created the post by navigating into the single post… but it is not possible to see which posts each author has written!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*KtwMDJjhyGsQfyThJN8fxw.png" /></figure><p>Being able to see inverse relationships it’s a <a href="https://github.com/datocms/feature-requests/issues/92">pretty common need</a>: thankfully we can build a plugin for that, let’s see how!</p><h3>Run the project generator</h3><p>To start straight away with the development and avoid writing boilerplate code, we’ve prepared a super-handy <a href="https://github.com/datocms/generator-datocms-plugin">Yeoman generator</a>.</p><p>Let’s create the folder that will contain the skeleton of our plugin and, once inside the folder, let’s run the generator:</p><pre>mkdir inverse-relationships<br>cd inverse-relationships<br>npx -p yo -p generator-datocms-plugin -c ‘yo datocms-plugin’</pre><p>Here’s a quick video of the tool in action:</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fplayer.vimeo.com%2Fvideo%2F301886498%3Fapp_id%3D122963&amp;dntp=1&amp;url=https%3A%2F%2Fvimeo.com%2F301886498&amp;image=https%3A%2F%2Fi.vimeocdn.com%2Fvideo%2F740536685_1280.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=vimeo" width="1920" height="1080" frameborder="0" scrolling="no"><a href="https://medium.com/media/090402dbf4a3233df5579f747614d224/href">https://medium.com/media/090402dbf4a3233df5579f747614d224/href</a></iframe><p>As you can see, a number of questions will be prompted. Some of them are quite obvious (ie. the plugin name), others require a little more understanding of what’s going on, so let’s see them in detail.</p><h3>Plugin type</h3><p>DatoCMS supports <a href="https://www.datocms.com/docs/plugins/introduction/#types-of-plugins">three types of plugin</a>: <em>field editors</em>, <em>field-addons</em> and <em>sidebar widgets</em>.</p><p>While the first two types of plugin operate on top of a particular field replacing/enhancing the default editor that DatoCMS provides, sidebar widget are rendered.. <em>duh</em>, on the sidebar of the record editor.</p><p>Since this plugin applies to an entire record instead of a single field, we’ll pick the <em>Sidebar widget</em> option.</p><h3>Field types the plugin is compatible with</h3><p>DatoCMS plugins need to be <a href="https://www.datocms.com/docs/plugins/install/#assigning-a-plugin-to-a-field">assigned to a field in one of your models</a> to come alive, so while creating new plugins you need to declare which kind of fields your plugin supports.</p><p>While it’s quite obvious that you need to assign <em>field editors</em> plugins and <em>field-addons</em> plugins to a field, it might be less clear why this also applies to <em>sidebar widgets</em>, right? Well, the reason is that the sidebar widget might want to use the field’s value to store some data (and yes, in case you’re wondering, the underlying field won’t be shown on the interface).</p><p>In any case, our sidebar widget plugin won’t read/store any data, so we can just choose any field type (ie. JSON) and move on to the next question.</p><h3>Configuration parameters</h3><p>Parameters allow the final user to customize the plugin, and you as the developer are in charge of deciding to which degree you want your plugin to be customizable.</p><p>Global parameters are set just once for the whole project. In this case we need to ask the final user the API token to use to query the DatoCMS API and get the actual inverse relationships.</p><p>Instance variables, on the other hand, allow the final user to insert different settings every time the plugin gets applied on a field.</p><p>Our plugin requires two instance variables: the first one will store the name of the model you want to connect to (ie. post), the other will store the field that hosts the inverse relation between the two (ie. author).</p><p>Parameters need to be expressed in JSON. The format is pretty straight-forward, but feel free to <a href="https://www.datocms.com/docs/plugins/creating-a-new-plugin/#configuration-parameters">take a look at our documentation</a> for all the nitty gritty details:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/5f3a64475e016ca43197b782ae623738/href">https://medium.com/media/5f3a64475e016ca43197b782ae623738/href</a></iframe><h3>Alright, I’m done configuring stuff!</h3><p>If everything went right, you should see in your DatoCMS project an already configured plugin similar to this one:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*DMGDzsYa72LiVwX8j6GC2w.png" /></figure><p>As you can see, in this page you can already insert the only global configuration parameter we have, the DatoCMS API token. Let’s do so and hit the Save button.</p><h3>Assign the plugin to a JSON field</h3><p>Now that the plugin is installed in the project, you need to apply it to a JSON field to see it working.</p><p>Navigate to the Author model (Settings &gt; Models &gt; Author) and add the JSON field that will host the plugin. You will notice that in the presentation tab you can select our plugin as the <em>Field editor</em> option and fill-in the instance configuration parameters:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/863/1*_xBO_3fusrVJFD0mkUz4cA.png" /></figure><h3>See the plugin working</h3><p>Technically speaking, plugins are small HTML5 applications that exist in a sandboxed &lt;iframe&gt; and interact with the main DatoCMS webapp</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*tIWY61kjnGAPTkyXpzyLfQ.png" /></figure><p>As you can see, our generator already setup the <a href="https://www.datocms.com/docs/plugins/entry-point/">Entry point</a> of our plugin so that it points to a tunnel connected to our local project. That is, using the raw localhost URL would give us some <em>mixed content </em>errors due to the fact that the local development server runs in HTTP while the main DatoCMS webapp runs in HTTPS.</p><p>Anyway, just start your local webpack development server with:</p><pre>yarn start</pre><p>Once the server starts, go to one of your authors.. and voilà! You should see a glorious “Hello, world!” awaiting for you!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mk2n3SkWjn7t_Jsfzj8XRQ.png" /></figure><h3>Write some code</h3><p>Alright, the setup part is finished, it is time to get to the coding! Let’s take a look at src/index.js file:</p><pre>import ‘./style.sass’;</pre><pre>window.DatoCmsPlugin.init((plugin) =&gt; {<br> plugin.startAutoResizer();</pre><pre>const container = document.createElement(‘div’);<br> container.classList.add(‘container’);<br> container.textContent = ‘Hello, world!’;</pre><pre>document.body.appendChild(container);<br>});</pre><p>The project already includes our <a href="https://www.datocms.com/docs/plugins/sdk-reference/">Plugin SDK</a>, which exposes the DatoCmsPlugin.init() method. Its callback will be called when the cross-window communication between our plugin and the DatoCMS main webapp is in place, so all the code needs to be executed inside of it. The plugin.startAutoResizer call will make sure the iframe will automatically resize whenever the content of the page changes.</p><p>Alright, let’s start adding a title to the widget:</p><pre>const container = document.createElement(‘div’);<br>container.classList.add(‘container’);</pre><pre>const title = document.createElement(‘h4’);<br>title.textContent = ‘Linked content’;</pre><pre>document.body.appendChild(container);<br>container.appendChild(title);</pre><p>Great, now we can add to our project the datocms-client package, so that we’ll be able to query the DatoCMS API to get the inverse relationships:</p><pre>yarn add datocms-client</pre><p>Once installed, we can require the package and instanciate the DatoCMS SiteClient using the datoCmsApitToken global parameter we configured earlier:</p><pre>import { SiteClient } from ‘datocms-client;</pre><pre>window.DatoCmsPlugin.init((plugin) =&gt; {<br> plugin.startAutoResizer();<br> <br> // …<br> <br> const client = new SiteClient(plugin.parameters.global.datoCmsApiToken);<br>});</pre><h4>Building up the query</h4><p>The next thing to do is building the right query to get what you need, in this case all the Post records that are linked to a specific author.</p><p>The plugin object holds a couple of properties that are essential here. The first one is plugin.itemTypes that returns all the project’s models. We can use it to get our Post model:</p><pre>const postItemType = Object.values(plugin.itemTypes).find(<br> itemType =&gt; itemType.attributes.api_key === plugin.parameters.instance.itemTypeApiKey<br>);</pre><p>The second is plugin.itemId , which is the ID of the current author record we’re seeing. Looks we’ve got everything to build the query now!</p><pre>const linkFieldApiKey = plugin.parameters.instance.fieldApiKey;</pre><pre>const query = {<br> ‘filter[type]’: postItemType.id,<br> [`filter[fields][${linkFieldApiKey}][is][]`]: plugin.itemId,<br> ‘page[limit]’: 10,<br> version: ‘current’,<br>};</pre><pre>client.items.all(query)</pre><p>This returns all the blog posts that have the current record as its author. For each one of them we can create a link element and then append it to the iframe:</p><pre>dato.items.all(query).then((items) =&gt; {<br> items.forEach((item) =&gt; {<br> const link = document.createElement(‘a’);<br> link.textContent = “title placeholder”;<br> const url = `#`;<br> link.href = url;<br> link.target = ‘_top’;<br> link.classList.add(‘link’);<br> container.appendChild(link);<br> });<br>})<br>.catch((error) =&gt; {<br> console.log(error);<br>});</pre><p>We now need to find out which is the title field for the Post model:</p><pre>const titleFieldId = postItemType.relationships.title_field.data.id;<br>const titleField = plugin.fields[titleFieldId];</pre><p>Now we can build the url and show the appropriate title. Of course our item could be localized, so in this case we should get the title in the main locale:</p><pre>if (titleField.attributes.localized) {<br> const mainLocale = plugin.site.attributes.locales[0];<br> link.textContent = item[titleField.attributes.api_key][mainLocale];<br>} else {<br> link.textContent = item[titleField.attributes.api_key];<br>}</pre><pre>const url = `/editor/item_types/${postItemType.id}/items/${item.id}/edit`;</pre><p>Finally you should be able to see something like this:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/429/1*6hXJE4NzW2vvylUXNWNAaQ.png" /><figcaption>Add your favourite CSS styling and there you have your first custom plugin!</figcaption></figure><h4>Share your plugin to the world</h4><p>It is now time to share your work with the community!</p><p>Open your package.json and README.md and make sure all the info is correct following <a href="https://www.datocms.com/docs/plugins/publishing/">our documentation</a>.</p><p>Consider adding a nice cover picture and a preview GIF image so that when the plugin will be displayed <a href="https://www.datocms.com/plugins/">our plugin catalog</a> it will be easier to decide that this is the plugin we want.</p><p>When everything is ready, run npm publish, and you’re good to go! The plugin will be added to the catalog in 10 minutes.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mAyKnSoD8znQErfxdNKQmw.png" /></figure><p>You can install the final plugin <a href="https://www.datocms.com/plugins/i/datocms-plugin-inverse-relationships/">from our catalog</a> or take a look at the complete code in this <a href="https://github.com/datocms/plugins/tree/master/inverse-relationships">Github repo</a>.</p><p><em>Originally published at </em><a href="https://www.datocms.com/blog/how-to-create-an-inverse-relations-plugin/"><em>www.datocms.com</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=253e7370aedc" width="1" height="1" alt=""><hr><p><a href="https://medium.com/datocms/how-to-create-an-inverse-relationships-plugin-on-datocms-253e7370aedc">How to create an inverse relationships plugin on DatoCMS</a> was originally published in <a href="https://medium.com/datocms">DatoCMS</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Build the perfect CMS: introducing DatoCMS Plugins]]></title>
            <link>https://medium.com/datocms/build-the-perfect-cms-introducing-datocms-plugins-fe7dac218a6b?source=rss----e54f04e323da---4</link>
            <guid isPermaLink="false">https://medium.com/p/fe7dac218a6b</guid>
            <category><![CDATA[jamstack]]></category>
            <category><![CDATA[frontend]]></category>
            <category><![CDATA[cms]]></category>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[npm]]></category>
            <dc:creator><![CDATA[Stefano Verna]]></dc:creator>
            <pubDate>Tue, 30 Oct 2018 17:30:25 GMT</pubDate>
            <atom:updated>2018-10-30T17:27:31.156Z</atom:updated>
            <content:encoded><![CDATA[<p>Possibly the single most-anticipated feature for DatoCMS ever, is finally here: <a href="https://www.datocms.com/plugins/">DatoCMS plugins</a>.</p><p>While DatoCMS offers a great number of fields with different appearance configurations, it’s obvious we cannot cover every possible scenario. Plugins aim to provide an amazing experience for DatoCMS editors, by letting developers replace the default fields that DatoCMS provides with third-party HTML5 applications, so the editing experience of every DatoCMS project can be fully customised.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*cp8sGYaiTa1WESNeXxwR6Q.png" /></figure><h3>What you can do with plugins?</h3><p>Glad you asked! Basically anything you could think of inside of a form.</p><p>Technically speaking plugins are small HTML5 applications that exist in a sandboxed &lt;iframe&gt; and interact with the main DatoCMS web-app through the Plugins SDK. They can be implemented with basic HTML and JavaScript, or using more advanced client-side frameworks such as React, Angular or Vue.</p><p>Using our SDK, plugins are able to show/hide record’s fields based on some condition:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/900/1*Yk80ejb-4VOmzSVBsQQZUw.gif" /></figure><p>Or just make editing experience more intuitive, like using a star rating widget instead of a plain textual input:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/900/1*-lKAzKIthP2ZW6Z4Tk7glw.gif" /></figure><h3>How to install them</h3><p>Just head over our <a href="https://www.datocms.com/plugins/">Plugins</a> section and click the install button: you will be able to specify in which one of your projects you want the plugin to be installed.</p><p>Once installed, a plugin can be assigned to one (or many) fields. In the Presentation tab of your field settings, choose the plugin as the field editor, and configure its settings.</p><h3>Help us build an ecosystem!</h3><p>We already released an handful of plugins, and we’ll keep on shipping new ones, but the real magic starts if you, our users, will decide to help us build a flourishing ecosystem.</p><p>We made it extremely easy to create new plugins. They are just NPM packages, so if you’ve ever released a package, then you’re already pretty far along. We’ve also made available lots of resources to start hacking around right away:</p><ul><li><a href="https://www.datocms.com/docs/plugins/creating-a-new-plugin/">A step-by-step guide to develop new plugins</a></li><li><a href="https://www.datocms.com/docs/plugins/sdk-reference/">The Plugins SDK reference</a></li><li><a href="https://github.com/datocms/plugins/">The source-code of all of our plugins</a></li></ul><p>On Slack we’ve just created a new <a href="https://datocms.slack.com/messages/CDN83VAQG/">#plugins</a> channel, so please don’t hesitate asking for help!</p><p><em>Originally published at </em><a href="https://www.datocms.com/blog/build-the-perfect-cms-introducing-plugins/"><em>www.datocms.com</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=fe7dac218a6b" width="1" height="1" alt=""><hr><p><a href="https://medium.com/datocms/build-the-perfect-cms-introducing-datocms-plugins-fe7dac218a6b">Build the perfect CMS: introducing DatoCMS Plugins</a> was originally published in <a href="https://medium.com/datocms">DatoCMS</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to make the most out of DatoCMS roles]]></title>
            <link>https://medium.com/datocms/how-to-make-the-most-out-of-datocms-roles-5ef048fa6e58?source=rss----e54f04e323da---4</link>
            <guid isPermaLink="false">https://medium.com/p/5ef048fa6e58</guid>
            <category><![CDATA[headless-cms]]></category>
            <category><![CDATA[publishing]]></category>
            <category><![CDATA[platform]]></category>
            <category><![CDATA[organization]]></category>
            <category><![CDATA[web-development]]></category>
            <dc:creator><![CDATA[Francesco Falchi]]></dc:creator>
            <pubDate>Fri, 05 Oct 2018 16:31:02 GMT</pubDate>
            <atom:updated>2018-10-05T16:31:02.650Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ZXok1sFY_hFw55sgdE-YLA.png" /></figure><p>One of DatoCMS strenghts is how you can give extremely granular permissions to every user you invite to a project. Just a week ago we released a much requested new feature to our roles system called <a href="https://www.datocms.com/changelog/creator-based-permissions-added-to-roles/">creator-based permissions</a>, which allow a whole new set of complex permission rules.</p><p>To explain what this new feature does and, more in general, how you can make the most out of DatoCMS roles, we’re going to run through a real-world example where setting proper permissions is vital for the project itself.</p><h4>When will I need to use roles?</h4><p>The most obvious example would be an editorial platform that creates a constant flow of new content, like an online newspaper.</p><p>The first instance of a role that you will run into when working with DatoCMS is of course yourself as the <em>Admin</em>.</p><p>An admin:</p><ul><li>can perform any action on any record contained of the project,</li><li>can publish the website on any environment (e.g. staging, production),</li><li>can invite new users to the project, and</li><li>has complete access to the project’s settings.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*JKgQOlxGvmxYu2fEgmQoGQ.gif" /><figcaption>The admin role with the default rules and additional settings</figcaption></figure><p>This is the role that the project creator inherits automatically and in a small project, if you’re managing it by yourself, you won’t need to create more roles.</p><p>But we’re creating a platform for an online newspaper that will have many people involved with different responsibilities, so let’s see what our next steps are going to be.</p><h4>Adding models</h4><p>Your client tells you that they need to create articles for the three main categories that they run daily: news, economics and sports.</p><p>First thing you’ll do is to setup the project’s schema, creating a model for each one of these kind of articles and adding some the fields for these models:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/691/1*t01Gt51wfixsqmtuO8Mb_w.png" /><figcaption>The model for the sport articles with some examples of the fields your client requested</figcaption></figure><p>Now that you have the basic structure for you project, you need to add roles for the people that will work on your platform.</p><h4>The chief editor</h4><p>The first role that you’re going to create is the <em>Chief editor</em>, which:</p><ul><li>must be able to edit/review any article,</li><li>has the final say to publish them in production, and</li><li>must be able to add new article writers.</li></ul><p>Translating this to your DatoCMS project means:</p><ul><li>being able to perform any action on every record created by anyone on the platform</li><li>publish the website in every environment available</li><li>invite new users.</li></ul><p>It’s quite similar to the <em>Admin</em> role. What differs is the fact that he can’t access or make changes to any of the projects settings, thus preventing him from inadvertently make some damage.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*BAHD6LiEAJirk-rx5m1geA.png" /><figcaption>The only additional option that you need to activate for the chief editor</figcaption></figure><h4>The freelance writers</h4><p>Now we need to manage freelance writers. We want them to be free to create new content for the newspaper section of their competence (e.g. sports) and preview it in the staging website, but not publishing the article on production. Only the <em>chief editors</em> can do that. We also do not want them to make changes to articles written by other writers.</p><p>This is the perfect example to illustrate the new <a href="https://www.datocms.com/changelog/creator-based-permissions-added-to-roles/">creator-based permissions</a> feature just added to our roles system.</p><p>To translate this requirement into DatoCMS language, we need to create a new role, the <em>Sports freelance writer</em>, that can perform every action only on the records of the <em>Sports article</em> model and, most importantly, created by the user itself. We also allow this role to publish only on the <em>Staging</em> environment.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/744/1*mvDAS_yai39jrLUNp5OAvg.gif" /><figcaption>The rules you want to select for this particular role</figcaption></figure><p>We can create similar roles for the news and economics sections of the newspaper.</p><h4>The art director</h4><p>Another important figure for a newspaper might be someone that makes sure articles look great. We’ll call it the <em>Art director</em>. An art director must be able to review the quality of the images used inside any article and the way the text is presented.</p><p>In DatoCMS we’ll set this role so that it is allowed to read and update every record available (regardless the model) but we’re not interested to make this role able to create any new record.</p><p>The art director, just like our freelance writers, will need to see what the article is going to look like, so we’ll set the publishing rule to staging again.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5oAFi0CAP1ck_H-JlSvQQg.png" /><figcaption>The update only is perfect for this role</figcaption></figure><h4>The proofreader</h4><p>The last role you need for your newspaper is the <em>Proof-reader</em>. Let’s say the chief editor approved an article and published it, but a typo is still there. It’s a proof-reader responsibility to find errors, correct them and publish the changes, even in production.</p><p>In DatoCMS:</p><ul><li>there’s no need for this role to create new records (just like the art-director) but it will need to update any record available;</li><li>the proof-reader will also need to publish on every environment, so we’ll set no limitations for the publishing rule;</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/739/1*XagzQwI0jyaHRlcI7JUj3g.png" /><figcaption>Proofreader is the first example of a role where you need more than one rule</figcaption></figure><h4>Any role you might need</h4><p>As you’ve seen, DatoCMS permissions system is very flexible and can be adapted for any kind of project you might need. In just a few minutes we created a complex editorial workflow, suitable for most mid-sized online newspapers.</p><p>The new creator-based permissions allows even more specific and useful permissions, letting the admin (or in this case, the chief editor) to easily create new roles that will work on a specific part of the project.</p><p>Please, try out our roles in one of your projects or demos, and let us know how it went!</p><p><em>Originally published at </em><a href="https://www.datocms.com/blog/how-to-make-the-most-out-of-datocms-roles/"><em>www.datocms.com</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5ef048fa6e58" width="1" height="1" alt=""><hr><p><a href="https://medium.com/datocms/how-to-make-the-most-out-of-datocms-roles-5ef048fa6e58">How to make the most out of DatoCMS roles</a> was originally published in <a href="https://medium.com/datocms">DatoCMS</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Tabular view + filters]]></title>
            <link>https://medium.com/datocms/tabular-view-filters-a0193be2dd8a?source=rss----e54f04e323da---4</link>
            <guid isPermaLink="false">https://medium.com/p/a0193be2dd8a</guid>
            <category><![CDATA[features]]></category>
            <category><![CDATA[visualization]]></category>
            <category><![CDATA[organization]]></category>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[headless-cms]]></category>
            <dc:creator><![CDATA[Francesco Falchi]]></dc:creator>
            <pubDate>Thu, 27 Sep 2018 16:31:01 GMT</pubDate>
            <atom:updated>2018-10-05T15:08:59.828Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*93fps4bUxQKBE8Ak9r5PZQ.png" /></figure><p>Every project starts simple, with few models and not so many records to take into consideration. But either by necessity or simply by adding more content through time, having a grasp of every piece of content created should be easy to access and in a fast way.</p><p>To reach this accessibility goal, DatoCMS has two important features that work perfectly together, the tabular view and the filters.</p><h4>Why Tabular view?</h4><p>Tabular view is the perfect solution for complex projects.</p><p>If you want to make a project for an e-commerce, you’ll have a model for a product with many different fields.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hX1aLufqxavPS4NViRHkOw.png" /><figcaption>A product could have even more fields than this</figcaption></figure><p>As your project grows and more records are added to your product model, it becomes hard to keep track of every single record when you have to edit them.<br>The Compact view seems to be unfit to manage this kind of complexity, you can’t sort your products and it’s very hard to search for them.</p><p>Now let’s see instead how the Tabular view shows a collection of many records.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*RHHbX_mK0wrxbu9DT4OiLA.png" /><figcaption>With different columns it’s much way easier to discern your records</figcaption></figure><p>Tabular view allows editors to configure(add, remove, reorder and resize), columns related to the field will inherit its name making them highly customizable too. <br>Each editor can manage its preferences, adding or moving columns according to its needs, then merge different filters to create a powerful search experience through many records. <br>With Tabular view you’ll be able to put some logic in the visualization of your list of records.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/212/1*Z7UTIqB-jNOzYL_jDyrLTg.png" /><figcaption>The columns selection with default values and customized fields</figcaption></figure><h4>How to use it</h4><p>By default the visualization for your models is now set on tabular view, let’s see exactly where it is located in your model settings. <br>In <a href="https://dashboard.datocms.com/projects">your DatoCMS dashboard</a> choose a project and then go to its settings and select “Models”, under “STRUCTURE” in the left sidebar, and then click on the “SETTINGS” of the model you want to edit.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*WfQtayuJz8WNBc11rRUd_g.png" /><figcaption>The settings for the model are next to its name on the right</figcaption></figure><p>Once you clicked this will open the settings modal, select the “Additional settings” tab.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/635/1*9ZnZ8wvqwtYg_Hbfw5859g.png" /><figcaption>This is where you can set your records visualization mode to tabular view</figcaption></figure><p>With Tabular view DatoCMS allows you to select what columns you want to see and then arrange them as you like.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*8vIClOAvAjsfrPVD4MpU3w.gif" /><figcaption>Select and remove the columns and then move them the way you like</figcaption></figure><h4>Tabular view + Filters, a match made in heaven</h4><p>So it’s a given that tabular view for your model is awesome but it would be an empty shell without a proper way to search for your content. <br>Enter the new filters, with them you can search any of the values of the columns and if you don’t remember the name of a record you can narrow it down to time.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*r7bb-GjOBSPaf9Iw4gXiUg.gif" /><figcaption>you can use more than one filter for a detailed search</figcaption></figure><h4>Evolving</h4><p>Tabular views and filters are a couple of features designed to improve content management for anyone using DatoCMS.</p><p>DatoCMS has many other new features incoming and it’s constantly evolving thanks to the suggestions and feedbacks of who’s using it.</p><p>Moving forward is the only way for DatoCMS.</p><p><em>Originally published at </em><a href="https://www.datocms.com/blog/tabular-view-and-filters/"><em>www.datocms.com</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a0193be2dd8a" width="1" height="1" alt=""><hr><p><a href="https://medium.com/datocms/tabular-view-filters-a0193be2dd8a">Tabular view + filters</a> was originally published in <a href="https://medium.com/datocms">DatoCMS</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>