<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Chad Person on Medium]]></title>
        <description><![CDATA[Stories by Chad Person on Medium]]></description>
        <link>https://medium.com/@objectivedesign?source=rss-31af9b52d638------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/2*T4eGmf-ovWRQwVCaLGZsXg.png</url>
            <title>Stories by Chad Person on Medium</title>
            <link>https://medium.com/@objectivedesign?source=rss-31af9b52d638------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 12:19:33 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@objectivedesign/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Keep it Static Stupid — Simple Sites Make Happy Clients]]></title>
            <link>https://medium.com/no-buffer/keep-it-static-stupid-simple-sites-make-happy-clients-960d49ccfdb4?source=rss-31af9b52d638------2</link>
            <guid isPermaLink="false">https://medium.com/p/960d49ccfdb4</guid>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[static-site]]></category>
            <category><![CDATA[cms]]></category>
            <dc:creator><![CDATA[Chad Person]]></dc:creator>
            <pubDate>Sun, 21 Feb 2016 00:04:19 GMT</pubDate>
            <atom:updated>2019-03-22T11:59:38.728Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4PUBxSlxCB6OZoxQ8J5f3Q.jpeg" /><figcaption>Static is beautiful.</figcaption></figure><h4>How to build faster, leaner, and safer websites without a database.</h4><p>The internet is broken. We arrived here mostly as a matter of habit — a pattern that needs to change.</p><h4>Your workflow is the problem</h4><p>A few years back (15?) developers and designers were introduced to an amazing, paradigm-shifting technology called a CMS (content management system). You know many of them by name (WordPress, Drupal, Joomla, etc.), and today they house a significant share of the web’s content.</p><p>Why did the CMS take over? Before them most pages were written very simply — with a text editor. Content had to be manually updated on every page, and developers needed to keep track of every change to make sure that repeated elements were updated throughout a site.</p><p>A CMS was a convenient new way to build a website. Install it on your server, and you gain access to a number of turnkey features — typically wrapped in an interface to make users, content, and settings easier to maintain. Layouts and frequently replicated elements (like nav bars) are easily repeatable, and simple site changes can often be made by fairly non-technical users. Additionally, many site designers and developers leverage the CMS to hand off a site to a client or content creator who wants to perform simple updates or handle routine maintenance — for better or worse.</p><p>In order to provide all these features, most content management systems leverage a database. That database stores content, user information, site configuration, and presentation data. Every time a visitor arrives on the page, the database is queried and content is retrieved/assembled for display. Every time.</p><p>Today, using these systems to power even the most basic sites has become common practice. Why? Because building simple sites on top of database-driven architecture feels more convenient than just delivering simple HTML content. As a result, our web has become bloated with lethargic, vulnerable content that costs us time and money.</p><h4>The case for simple websites</h4><p>It’s ironic that while mobile devices have ushered in flat design and streamlined content, over-complicated dynamic architecture is powering some of the most basic content online.</p><p>Imagine your website as a newspaper. Publishing a site on a database-driven CMS like Wordpress is the equivalent of printing a newspaper on the fly, every time a reader wants to access any part of your paper. This inherently inefficient system results in slower page loads and lost eyeballs.</p><p>These same visitors have been bitten by wide spread security breaches that seem to crop up with increasing frequency. Needless complexity and poorly maintained software expose vulnerabilities that can lead to a site going offline, being inundated with malware, or worse — a data breach. By some measures — as many as <a href="https://www.smashingmagazine.com/2015/11/modern-static-website-generators-next-big-thing/">70% of WordPress installs are vulnerable</a> to known exploits, such as last May when a <a href="http://www.engadget.com/2015/05/07/wordpress-xss-bug/">bug affected millions of WordPress sites</a>. In the previous year as many as <a href="https://nakedsecurity.sophos.com/2014/10/30/millions-of-drupal-websites-at-risk-from-failure-to-patch/">12 million Drupal site were compromised</a>. Each new complexity in the system and/or time-saving plugin becomes a potential point of failure.</p><p>Likewise, developers pay the price when handing off routine updates and regular maintenance to a client. I’ve personally received the unfortunate after hours call from a client who discovered her site was compromised and infected with embarrassing content. It could have been avoided. But, since her site hadn’t been changed/updated in ~18 months the software had fallen behind, making it susceptible to attack.</p><h4>HOUNDSTOOTH IS A BETTER CMS FOR STATIC CONTENT</h4><p>As with so many things, simple is ultimately better.</p><p>For many use cases (brochure sites, service providers, portfolios, event pages, landing pages), static sites are quite obviously the right tool for the job. In fact, any site where visitor interactions are guided (accessing existing content, submitting content through a fixed form, and not interacting with other visitors in real time) can be deployed as a static site. All of these interactions can be handled without a database.</p><p>But, no one wants to lose all the convenience features of a CMS. The good news is, there are better options to provide the same benefits with less hassle.</p><p>Today’s browsers can execute many of the same functions that used to require dynamic code running on a server. Comments, social integration, data storage, live chat, payments, and search can be easily added to a static site.</p><p>Modern tools like <a href="https://houndstooth.work/">Houndstooth</a> allow you to manage websites that are faster, leaner, and as flexible as a traditional database-driven CMS.</p><ul><li>Static sites managed with Houndstooth load faster (because we’ve rendered the site in advance), and eliminate the risk of a database breach (because there is no database).</li><li>Site developers use tools they are comfortable with (git, local development, Jekyll).</li><li>Content is managed in a customized interface for non-technical users to update/create content.</li><li>Edits are made in the browser, and your site is rebuilt automatically on save using tools like <a href="https://razorsite.co/">RazorSite</a> or Netlify.</li><li>Your site files are hosted on Github for safety and infinite redundancy.</li><li><a href="https://houndstooth.work/">Houndstooth</a> is open source, and we are looking for contributors.</li></ul><h4>STATIC IS A BEAUTIFUL FUTURE</h4><p>Is static the right solution for your next site? For simple sites, landing pages, and many web apps, the answer is a resounding yes. The ecosystem of tools surrounding static sites is rich and growing. Combining these with a client-ready CMS like Houndstooth match the capabilities that have made dynamic websites convenient in the past.</p><p>An increasing number of agencies and freelancers are deploying static sites for small business clients and major brands. Static architecture was the solution that fixed <a href="https://developmentseed.org/blog/new-healthcare-gov-is-open-and-cms-free/">Healthcare.gov</a> following its very high profile performance failures at launch. And, an increasing number of design-driven enterprise companies are using static sites to power their primary properties (<a href="https://blog.mailchimp.com/building-the-new-mailchimp/">MailChimp</a>, Nest, Google).</p><h4>WORKING WITH HOUNDSTOOTH</h4><p>If you wan to explore <a href="https://houndstooth.work/">Houndstooth</a> for your next project I recommend you visit the main project site, and check out the source on <a href="https://github.com/bowtie-co/houndstooth-ui">Github</a>.</p><p>If you would like to work with our agency on your next project, contact <a href="https://bowtie.co/">Bowtie.co</a> to start the conversation.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=960d49ccfdb4" width="1" height="1" alt=""><hr><p><a href="https://medium.com/no-buffer/keep-it-static-stupid-simple-sites-make-happy-clients-960d49ccfdb4">Keep it Static Stupid — Simple Sites Make Happy Clients</a> was originally published in <a href="https://medium.com/no-buffer">Objective Art + Design</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[BowTie is happier with Zapier]]></title>
            <link>https://medium.com/@objectivedesign/bowtie-is-happier-with-zapier-2d5556c8c237?source=rss-31af9b52d638------2</link>
            <guid isPermaLink="false">https://medium.com/p/2d5556c8c237</guid>
            <category><![CDATA[api]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[product-development]]></category>
            <dc:creator><![CDATA[Chad Person]]></dc:creator>
            <pubDate>Thu, 23 Jul 2015 16:43:51 GMT</pubDate>
            <atom:updated>2015-07-23T16:43:51.235Z</atom:updated>
            <content:encoded><![CDATA[<h4>Test drive our invite-only Zapier integration and we’ll buy your lunch!</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/300/1*6uNM4c4V_oxEt6oTABslrA.png" /><figcaption>You can now use BowTie with Zapier</figcaption></figure><p>We just shipped a brand new integration to <a href="http://seedworthy.createsend1.com/t/d-l-jylkulk-l-i/">Zapier</a>. Now you can connect your BowTie project to hundreds of other services and automate common tasks without writing a line of code.</p><p>BUT… we need your help:</p><p>We need 10 people to fire up new ‘<a href="http://seedworthy.createsend1.com/t/d-l-jylkulk-l-d/">Zaps</a>’ in order to make our integration public. It only takes a few minutes, and if you send us a screen grab of your zap, we’ll credit your BowTie account with $10!</p><p>If you haven’t used Zapier, it’s an automation platform that lets you connect api services together with the simplicity of if this, then that statements.</p><p>Want to send a BowTie user to MailChimp or another email provider? Done. Would you like to get a Slack notice when someone upgrades? Done. There are literally thousands of options.</p><h3><a href="https://zapier.com/developer/invite/24423/05c8fdf1319a7917a90fdc3d63c8e519/"><strong>Try It Now</strong></a></h3><p>Need help? I wrote a <a href="https://bowtie.io/blog/using-bowtie-with-zapier.html">How to post</a> you can read on the BowTie blog.</p><p>PS — If you haven’t created a BowTie account, you can still join our private beta with the code ‘<a href="https://bowtie.io/owners/sign_up">EARLYBIRD</a>’. Thanks for your support, and please share this email with anyone who may be interested.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2d5556c8c237" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Announcing Springboard Hackathon]]></title>
            <link>https://medium.com/@objectivedesign/announcing-springboard-hackathon-df0bcd823d8e?source=rss-31af9b52d638------2</link>
            <guid isPermaLink="false">https://medium.com/p/df0bcd823d8e</guid>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[development]]></category>
            <category><![CDATA[hackathons]]></category>
            <dc:creator><![CDATA[Chad Person]]></dc:creator>
            <pubDate>Fri, 16 Jan 2015 16:13:37 GMT</pubDate>
            <atom:updated>2015-03-02T05:11:48.617Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*R5pKxLMhHJPLpe-ODoONhw.jpeg" /></figure><h2>Announcing Springboard</h2><h4>Ship to win tools, space, exposure and toys on Jan 31st!</h4><p>Ready to ship your side project? Toss it on ⋈ <a href="https://bowtie.io/">BowTie</a> for a chance to present at SXSWi, win hosting, co-working space, legal help and other amazing prizes. <a href="https://springboard.bowtied.io/">Springboard 201</a>5 is open for registration.</p><p>This isn’t a hackathon, its a shipathon. The format is simple — launch your app on ⋈ BowTie, validate for 2 weeks, bring it back for Demo Day and win awesome prizes to help you keep moving.</p><h4>Format:</h4><p>Teams of 1–3 developers/designers/entrepreneurs will dive in on January 31st for an intro to <a href="https://bowtie.io/">BowTie.io</a> and hackathon at FatPipeABQ in Albuquerque, NM. (You do not need to be present, we can beam you in from the tubes).</p><p>On Feb. 13th we reconvene for a Demo Day and party. Judges will award a Grand Prize, Runner Up, and Audience Choice project.</p><p>Prizes:</p><p>Shipping is winning! But, here are some other prizes to help keep you leap:</p><p><strong>Grand Prize</strong></p><ul><li>1 year of hosting for your project on ⋈ BowTie, with premium support.</li><li>Legal setup + trademark service for your startup from <a href="http://lernerventurelaw.com/">Lerner Venture Law</a></li><li>6 months free at <a href="http://fatpipeabq.com/">Fatpipe ABQ</a> — including fiber internet.</li><li>Stage time for your project at <a href="http://startupoasis.up.co/">Startup Oasis</a> during <a href="http://sxsw.com/interactive">SXSWi</a> on March 17th.</li></ul><p><strong>Runner Up</strong></p><ul><li>6 months of hosting for your project on ⋈ BowTie, with premium support.</li><li>Legal setup + trademark service for your startup from <a href="http://lernerventurelaw.com/">Lerner Venture Law</a></li><li>BowTie.io Team Hooded Sweatshirts</li></ul><p><strong>Audience Choice</strong></p><ul><li>6 months of hosting for your project on ⋈ BowTie, premium support included.</li><li><a href="https://www.oculus.com/dk2/">Occulus Rift Dev Kit </a>2</li><li>BowTie.io Team Hooded Sweatshirts</li></ul><p>…and don’t forget we’ll have tons of swag from our sponsors!</p><h4>Registration:</h4><p>We are accepting 30 teams. As of this posting, 20 slots remain.<br>Registration closes Jan. 30th, or when we reach our cap. Sign up!</p><blockquote><a href="https://springboard.bowtied.io/"><strong>REGISTER FOR</strong></a><strong> SPRINGBOARD</strong></blockquote><p><em>⋈ BowTie assumes no ownership of your project. We just want to help you get out the door.</em></p><p>For more information, please <a href="https://springboard.bowtied.io/">View the Springboard Event site</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=df0bcd823d8e" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>