<?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[Fiat Insight - Medium]]></title>
        <description><![CDATA[Building products with purpose. Since 2010. - Medium]]></description>
        <link>https://medium.com/fiatinsight?source=rss----a01bacb00b29---4</link>
        <image>
            <url>https://cdn-images-1.medium.com/proxy/1*TGH72Nnw24QL3iV9IOm4VA.png</url>
            <title>Fiat Insight - Medium</title>
            <link>https://medium.com/fiatinsight?source=rss----a01bacb00b29---4</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 11:06:30 GMT</lastBuildDate>
        <atom:link href="https://medium.com/feed/fiatinsight" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[How to ensure reliable email sending from your WordPress website]]></title>
            <link>https://medium.com/fiatinsight/how-to-ensure-reliable-email-sending-from-your-wordpress-website-12a20487c323?source=rss----a01bacb00b29---4</link>
            <guid isPermaLink="false">https://medium.com/p/12a20487c323</guid>
            <category><![CDATA[email]]></category>
            <category><![CDATA[wordpress]]></category>
            <category><![CDATA[business-strategy]]></category>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[small-business]]></category>
            <dc:creator><![CDATA[Ben Zumdahl]]></dc:creator>
            <pubDate>Sat, 26 Jan 2019 02:41:35 GMT</pubDate>
            <atom:updated>2019-01-26T02:41:35.788Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2Oo1Din32plTMdI8GypK4Q.jpeg" /></figure><p>You may not have given it much thought, but your website can send emails just like you do. Well, not <em>just</em> like you do. But when actions occur on your website — when a form is submitted or a password reset is requested — an email notification can be sent.</p><p>WordPress is built to tap into the basic email setup of most web hosts so that sending emails works without too much tinkering. However, problems often arise that prevent emails from sending properly. And you may not notice when you don’t receive that first contact form submission. Or the second or third one…</p><h4>Use a transactional email service</h4><p>So how can you ensure that emails get where they are supposed to go? Instead of relying on your web host’s server to send your email, use a <em>transactional email </em>provider. For years now, we’ve partnered with one such provider — <a href="https://postmarkapp.com/">Postmark</a> —with great success.</p><p>There are three reasons you should consider using a transactional email service:</p><ol><li><strong>Transparency</strong>: Not sure if all the emails your website sends are getting through? Wouldn’t it be nice to know? With Postmark integrated you can see a full log of emails sent along with a status to confirm if each was received or encountered an error.</li><li><strong>Branding</strong>: Emails sent through your web host won’t appear as coming from you. They may have an obscure email address and are often flagged as spam because of their generic nature. Using Postmark, emails can be sent from your actual email address, e.g.: name@myorginization.com.</li><li><strong>Quantity</strong>: Many web hosts place a limit on the number of emails your website can send per hour or day. There is no such limit using a transactional service. So there’s no worry if you suddenly have a lot of contact form submissions, payment notifications, or petition signatories.</li></ol><p>We provide Postmark for email to all of our clients with support plans, and it’s proved invaluable for its reliability (always works!) and clarity (“Yes, you did get that password reset email on…”).</p><p>Downside? We haven’t found one yet. Postmark <a href="https://wordpress.org/plugins/postmark-approved-wordpress-plugin/">maintains a plugin</a> that makes getting set up easy, and they offer a free plan of up to 100 emails per month.</p><p><em>Questions about your email reliability or capabilities? Speak up today at </em><a href="https://fiatinsight.com/contact"><em>https://fiatinsight.com/contact</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=12a20487c323" width="1" height="1" alt=""><hr><p><a href="https://medium.com/fiatinsight/how-to-ensure-reliable-email-sending-from-your-wordpress-website-12a20487c323">How to ensure reliable email sending from your WordPress website</a> was originally published in <a href="https://medium.com/fiatinsight">Fiat Insight</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 change a filename in Rails Active Storage]]></title>
            <link>https://medium.com/fiatinsight/how-to-change-a-filename-in-rails-active-storage-f3e4f26f427e?source=rss----a01bacb00b29---4</link>
            <guid isPermaLink="false">https://medium.com/p/f3e4f26f427e</guid>
            <category><![CDATA[rails-5]]></category>
            <category><![CDATA[active-storage]]></category>
            <category><![CDATA[how-to]]></category>
            <category><![CDATA[ruby-on-rails]]></category>
            <category><![CDATA[guides-and-tutorials]]></category>
            <dc:creator><![CDATA[Ben Zumdahl]]></dc:creator>
            <pubDate>Sat, 27 Oct 2018 22:19:36 GMT</pubDate>
            <atom:updated>2018-10-27T22:19:35.684Z</atom:updated>
            <content:encoded><![CDATA[<h4>Ensure that downloaded files have the name you want</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*j5QLyzpTErmZjgk32teLCA.jpeg" /></figure><p>If you’ve tried it, you know that <a href="https://edgeguides.rubyonrails.org/active_storage_overview.html">Active Storage</a> provides a flexible and feature-rich Rails file management solution. Under the hood, the blobs and attachments can seem confusing at first, but it’s actually remarkably simple to set up and use.</p><p>I recently ran into a challenge, though, when trying to change the name of the files that I was uploading. The goal was to standardize and set the filename format so that no matter what a file might have been named when I uploaded it, it would be overwritten. Then, when a user would download the file later, it would have the standardized name.</p><p>I couldn’t find mention of exactly how to accomplish this, but it turns out updating the blob filename is all that’s required:</p><pre>self.active_storage_object.blob.update(filename: &quot;desired_filename.#{self.active_storage_object.filename.extension}&quot;)</pre><p>In my case, I used an after_create callback to wrap this because I was using one form to both create the object (a <em>product</em>) and upload and attach a file (a <em>video</em>) to it. Here’s that in a gist:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/1ba78174ceafddf2aa14bef45ef56df7/href">https://medium.com/media/1ba78174ceafddf2aa14bef45ef56df7/href</a></iframe><p>Don’t forget, it’s also critical to retain the extension as above when saving over the filename!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f3e4f26f427e" width="1" height="1" alt=""><hr><p><a href="https://medium.com/fiatinsight/how-to-change-a-filename-in-rails-active-storage-f3e4f26f427e">How to change a filename in Rails Active Storage</a> was originally published in <a href="https://medium.com/fiatinsight">Fiat Insight</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Using Duo MFA with Devise for Rails]]></title>
            <link>https://medium.com/fiatinsight/using-duo-mfa-with-devise-for-rails-6daddc2b46f3?source=rss----a01bacb00b29---4</link>
            <guid isPermaLink="false">https://medium.com/p/6daddc2b46f3</guid>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[ruby-on-rails]]></category>
            <category><![CDATA[mobile]]></category>
            <category><![CDATA[security]]></category>
            <category><![CDATA[web-development]]></category>
            <dc:creator><![CDATA[Andrew Haines]]></dc:creator>
            <pubDate>Mon, 22 Oct 2018 21:06:14 GMT</pubDate>
            <atom:updated>2018-10-22T21:06:13.626Z</atom:updated>
            <content:encoded><![CDATA[<h4>Roll your own two-factor authentication solution</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*EfW1ONufca7JMdQPtxtYUw.png" /></figure><p><a href="https://duo.com/">Duo</a> is a really nifty, easy-to-use service. And <a href="https://github.com/plataformatec/devise">Devise</a> is the undisputed heavyweight Rails authentication engine. So, I figured it’d be easy to find out how to make them work together.</p><p>Turns out, I was wrong. (It’s almost 2019, for crying out loud!)</p><p>Here, I’ll try and help fix that.</p><h4>Credit where it’s due</h4><p>Actually, <a href="https://medium.com/@tjoye20/ruby-on-rails-setting-up-duo-two-factor-authentication-with-devise-b6a9c1a025e0">this post</a> by TJ Oyeniyi <em>did </em>end up proving very useful, but it’s behind a paywall, and you can’t copy/paste the code. So I figured presenting some similar information for free, with my own spin, and in an easier-to-copy format, would be worthwhile. (But still, maybe thank <a href="https://medium.com/@tjoye20">him</a> if you can.)</p><h4>Okay, setting up…</h4><p>First things first. Install the <a href="https://github.com/duosecurity/duo_ruby">Duo gem</a>: gem install duo_web. Or put it in your Gemfile: gem &#39;duo_web&#39;. Then set some environment variables, either in your .env file or as Heroku config vars or whatever.</p><pre>DUO_INT_KEY=your_identity_key_from_duo                       DUO_SECRET_KEY=your_secret_key_from_duo                       DUO_APP_KEY=your_secret_string # Generate with SecureRandom.gen_random(40)<br>DUO_HOST=api-123abc.duosecurity.com</pre><h4>Controllers</h4><p>To handle the actions, create a RegistrationsController that inherits from your Devise::RegistrationsController and add the following:</p><pre>class RegistrationsController &lt; Devise::RegistrationsController<br>  skip_before_action :require_no_authentication, only: [:verify_duo]<br>  skip_before_action :verify_authenticity_token<br><br>  def connect_with_duo<br>    @sig_request = Duo.sign_request(ENV[&quot;DUO_INT_KEY&quot;], ENV[&quot;DUO_SECRET_KEY&quot;], ENV[&quot;DUO_APP_KEY&quot;], current_user.email)<br>  end<br><br>  def verify_duo<br>    @authenticated_user = Duo.verify_response(ENV[&quot;DUO_INT_KEY&quot;], ENV[&quot;DUO_SECRET_KEY&quot;], ENV[&quot;DUO_APP_KEY&quot;], params[&#39;sig_response&#39;])<br>    if @authenticated_user<br>      session[:duo_authentication] = true<br>      redirect_to some_path_you_want<br>    else<br>      redirect_to some_other_path_you_want<br>    end<br>  end<br>end</pre><p>In your ApplicationController you can check to see if the session[:duo_authentication] variable is set.</p><pre>def confirm_duo_authentication<br>  if !session[:duo_authentication]<br>    redirect_to connect_with_duo_path<br>  end<br>end</pre><p>You can invoke this method from any individual controller. Or you can require it for all controllers by putting the following at the top of your ApplicationController:</p><pre>before_action :confirm_duo_authentication</pre><h4>Routing</h4><p>Assuming you’ve already got Devise routes up and running, just include a few more lines to the relevant controller actions, above.</p><pre>devise_scope :user do<br>  post &#39;registrations/verify_duo&#39;, to: &#39;registrations#verify_duo&#39;, as: :verify_duo<br>  get &#39;registrations/connect_with_duo&#39;, to: &#39;registrations#connect_with_duo&#39;, as: :connect_with_duo<br><br>  authenticated do<br>    root :to =&gt; &quot;registrations#connect_with_duo&quot;<br>  end<br>end</pre><h4>Views</h4><p>The last thing you’ll have to do is allow a user to actually <em>use</em> the Duo setup. For that you’ll need a view corresponding to your controller action; in this case, at views/registrations/connect_with_duo.html.erb. You can pipe in the Duo magic using JavaScript, and display it via an iframe:</p><pre>&lt;script src=&quot;https://api.duosecurity.com/frame/hosted/Duo-Web-v2.js&quot; type=&quot;text/javascript&quot;&gt;&lt;/script&gt;</pre><pre>&lt;iframe id=&quot;connect_with_duo&quot; data-host=&quot;&lt;%= ENV[&quot;DUO_HOST&quot;] %&gt;&quot; data-sig-request=&quot;&lt;%= @sig_request %&gt;&quot; data-post-action=&quot;/registrations/verify_duo&quot;&gt;&lt;/iframe&gt;</pre><p>You’ll need to stylize your iframe to work with your app (setting min-width and min-height most importantly).</p><h4>Flexible implementation</h4><p>You can easily determine where and when the Duo connection setup takes effect. If you’re working with users in an existing app and want them to configure Duo for the first time, that’s possible, too. Playing with the ApplicationController, after_sign_in_path_for(), and the routes are all that’s required.</p><p>This setup also works with <a href="https://duo.com/docs/dag">Duo Access Gateway</a>, which makes it easy to tap into existing directory credentials for things like Microsoft Active Directory or Google Apps with SAML.</p><h4>The whole thing</h4><p>Here’s a gist of the whole thing. Enjoy!</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/b60eb2b87009b59bf5021ef6df60c027/href">https://medium.com/media/b60eb2b87009b59bf5021ef6df60c027/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6daddc2b46f3" width="1" height="1" alt=""><hr><p><a href="https://medium.com/fiatinsight/using-duo-mfa-with-devise-for-rails-6daddc2b46f3">Using Duo MFA with Devise for Rails</a> was originally published in <a href="https://medium.com/fiatinsight">Fiat Insight</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[WordPress is changing]]></title>
            <link>https://medium.com/fiatinsight/wordpress-is-changing-e14fd470f044?source=rss----a01bacb00b29---4</link>
            <guid isPermaLink="false">https://medium.com/p/e14fd470f044</guid>
            <category><![CDATA[plugins]]></category>
            <category><![CDATA[wordpress]]></category>
            <category><![CDATA[guides-and-tutorials]]></category>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[gutenberg]]></category>
            <dc:creator><![CDATA[Ben Zumdahl]]></dc:creator>
            <pubDate>Wed, 10 Oct 2018 17:34:44 GMT</pubDate>
            <atom:updated>2018-10-10T17:34:43.808Z</atom:updated>
            <content:encoded><![CDATA[<h4>What to know and how to prepare for the Gutenberg editor overhaul</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/1*nVJmdBPomPBM2Pb41GULbg.jpeg" /></figure><p>We actively manage hosting for hundreds of WordPress websites, so we take changes to the WordPress ecosystem seriously. The coming release of <a href="https://wordpress.org/gutenberg/">Gutenberg</a> is the biggest in recent memory. Some even fear it’ll be more like Gutenpocalypse or Gutengeddon.</p><p>We take a more measured approach. In preparation for the big release, we’re informing our clients about the change, its possible impact, and a recommendation for how to proceed.</p><h4>So, what should I do?</h4><p>Here are a few things to keep in mind, and a course of action, concerning WordPress, Gutenberg, and your website:</p><p><strong>What’s happening</strong>? WordPress is releasing a new editing interface codenamed <a href="https://wordpress.org/gutenberg/">Gutenberg</a>. In practice, this will mean that editing a page on your website is less like editing a Word document and more like stacking blocks of different types of content (pictures, text, quotes, etc).</p><p><strong>Why is this happening</strong>? This change is prompted by a desire to enable more flexibility and control over the layout and arrangement of page content.</p><p><strong>When will this occur?</strong> This change will <em>automatically occur when your website updates to WordPress 5.0</em>, which is scheduled for release on November 19, 2018.</p><p><strong>Is this bad</strong>? No, the changes should bear fruit in the future. However, <em>immediate compatibility</em> with your website is unknown and your ability to properly edit content may be <em>negatively impacted</em> (i.e., things may break).</p><p><strong>What can be done?</strong> You can preemptively install a plugin made just for this purpose. Installing the <a href="https://wordpress.org/plugins/classic-editor/">Classic Editor</a> plugin will ensure that your content editing experience is unchanged even while preserving your ability to continue receiving automatic updates to WordPress.</p><p><strong>What do you recommend?</strong> We think Gutenberg is a bold effort to prevent complacency and keep WordPress on a path of market dominance well into the foreseeable future. That said, unless you’re fond of squashing bugs, we suggest installing <a href="https://wordpress.org/plugins/classic-editor/">the plugin</a> now and trying the new editor later, after any (very likely) kinks are worked out.</p><p><em>Not sure you’re ready for </em>Gutenpocalypse? <em>Let us know how we can work with you, today: </em><a href="https://fiatinsight.com/contact"><em>https://fiatinsight.com/contact</em></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e14fd470f044" width="1" height="1" alt=""><hr><p><a href="https://medium.com/fiatinsight/wordpress-is-changing-e14fd470f044">WordPress is changing</a> was originally published in <a href="https://medium.com/fiatinsight">Fiat Insight</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Simplest Way to add Two-Factor Authentication to WordPress]]></title>
            <link>https://medium.com/fiatinsight/the-simplest-way-to-add-two-factor-authentication-to-wordpress-77d8a08121cc?source=rss----a01bacb00b29---4</link>
            <guid isPermaLink="false">https://medium.com/p/77d8a08121cc</guid>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[two-factor-authentication]]></category>
            <category><![CDATA[wordpress]]></category>
            <category><![CDATA[plugins]]></category>
            <category><![CDATA[security]]></category>
            <dc:creator><![CDATA[Ben Zumdahl]]></dc:creator>
            <pubDate>Tue, 09 Oct 2018 17:30:02 GMT</pubDate>
            <atom:updated>2018-10-09T17:30:02.381Z</atom:updated>
            <content:encoded><![CDATA[<h3>The simplest way to add two-factor authentication (2FA) to WordPress</h3><h4>No more excuses: secure that WordPress login today</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/806/1*R5WO0cT2K5lL_T83YVhWdg.png" /><figcaption>(screenshot from Duo setup video)</figcaption></figure><p>On a recent project, a client requested that we enable two-factor authentication (2FA) for a WordPress website (a very good idea). We’d used <a href="https://duo.com/">Duo</a>, a best-in-class security provider, on custom-built Rails applications before, but never with WordPress. We opted to try it here and I’m glad we did: it turns out setup was effortless and it’s easy to use.</p><h4>Why Duo?</h4><ol><li>It can be used free with up to 10 users</li><li>There is a well-maintained plugin that makes set up quick and easy</li><li>You can require two-factor for all users or only specific user roles</li><li>Users can easily self-enroll (i.e., no burdensome set up)</li></ol><h4>How does it work?</h4><p>After configuration, users go to the same WordPress login page as before. After entering the username and password a new prompt appears, which walks the user through authenticating a second way: either via a text message or the Duo app (or even a voice call).</p><h4>Want to get started?</h4><ol><li><a href="https://signup.duo.com/">Sign up for a free Duo account</a></li><li><a href="https://wordpress.org/plugins/duo-wordpress/">Install the WordPress plugin</a></li><li><a href="https://duo.com/docs/wordpress">Watch the brief setup video</a></li></ol><p>It took me less than 15 minutes to get signed up, configured, and logged into the WordPress website using Duo’s two-factor authentication. Given the benefits, cost (<em>free</em>), and ease of use, I anticipate we’ll be similarly enhancing many client WordPress sites in the near future.</p><p><em>Need a partner to help you secure your WordPress website? Let us know how we can work with you, today: </em><a href="https://fiatinsight.com/contact"><em>https://fiatinsight.com/contact</em></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=77d8a08121cc" width="1" height="1" alt=""><hr><p><a href="https://medium.com/fiatinsight/the-simplest-way-to-add-two-factor-authentication-to-wordpress-77d8a08121cc">The Simplest Way to add Two-Factor Authentication to WordPress</a> was originally published in <a href="https://medium.com/fiatinsight">Fiat Insight</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Hire for complements, not compliments]]></title>
            <link>https://medium.com/fiatinsight/hire-for-complements-not-compliments-f0f959f1bd46?source=rss----a01bacb00b29---4</link>
            <guid isPermaLink="false">https://medium.com/p/f0f959f1bd46</guid>
            <category><![CDATA[business]]></category>
            <category><![CDATA[small-business]]></category>
            <category><![CDATA[psychology]]></category>
            <category><![CDATA[management]]></category>
            <category><![CDATA[productivity]]></category>
            <dc:creator><![CDATA[David Sly]]></dc:creator>
            <pubDate>Wed, 30 May 2018 15:58:25 GMT</pubDate>
            <atom:updated>2018-05-30T15:58:25.514Z</atom:updated>
            <content:encoded><![CDATA[<h4>Doubling down on your weaknesses is bad business</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*uRP7iQA33Hd1k_euoNCANw.jpeg" /></figure><p>You hear people talk about a “stuck at the airport” rule for hiring. The idea is that when you have a difficult choice between two candidates (employees, vendors, clients, etc.), choose the one that you would rather be stuck at the airport with, because…well, you might someday be.</p><p>Making a choice because you think you’d get along with one person over another is a nice heuristic for choosing between mostly similar candidates. Getting along with people you work with is not something to take lightly. However, it’s tempting to stretch this rule beyond its limits — to use it not as a tie breaker, but as a reason for moving ahead in the first place. Worse yet, it can lead to a mindset where “getting along” by reducing friction is the primary goal over bringing real value to a business. Estimating how well you’ll get along with someone isn’t easily measured, and typically is only based on how agreeable the person has been in your encounters so far. This can be a trap.</p><p>Getting along with coworkers, subordinates, or vendors is generally good. But it’s a skill, and really shouldn’t depend on how agreeable someone is. When we choose people solely — or primarily — based on sharing the same opinions, viewpoints, work ethics, etc., it’s a dangerous definition of a “good fit.” Real value occurs when ideas are challenged. Not for the sake of being difficult, but because someone sees a problem differently and rounds out rough edges, or sharpens others. Fostering this type of environment, and intentionally surrounding yourself with people that are different than you, helps to ensure that you won’t get stuck in an avoidable, harmful mindset or business rut.</p><p>Whether you’re a business owner or managing a team, the goal for hiring should always be to hire into a need you have. Most of the time, the most glaring need you have is in an area in which you’re naturally deficient. Therefore, the person you most need usually possesses a complementary skill to something you are not good at. If you hire someone whose temperament, demeanor, and work style closely resembles your own, it’s very likely you share many of the same strengths and conversely the same weaknesses.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f0f959f1bd46" width="1" height="1" alt=""><hr><p><a href="https://medium.com/fiatinsight/hire-for-complements-not-compliments-f0f959f1bd46">Hire for complements, not compliments</a> was originally published in <a href="https://medium.com/fiatinsight">Fiat Insight</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Use images, yes. But be selective.]]></title>
            <link>https://medium.com/fiatinsight/use-images-yes-but-be-selective-2bead4db7f49?source=rss----a01bacb00b29---4</link>
            <guid isPermaLink="false">https://medium.com/p/2bead4db7f49</guid>
            <category><![CDATA[childrens-books]]></category>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[picture-books]]></category>
            <category><![CDATA[web-design]]></category>
            <category><![CDATA[photojournalism]]></category>
            <dc:creator><![CDATA[Ben Zumdahl]]></dc:creator>
            <pubDate>Thu, 03 May 2018 16:37:18 GMT</pubDate>
            <atom:updated>2018-05-03T16:37:17.759Z</atom:updated>
            <content:encoded><![CDATA[<h4>I went on my first field trip as a parent this week, and I walked away thinking about the power of pictures.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*CZBTZF3tLlt-6xfT6aF8Dw.jpeg" /></figure><p>Helping with a class field trip was definitely one of those milestone moments in life. I opted to play it safe by chaperoning a visit to the local library, as opposed to signing up for an all-day bus trip to a theme park. I was rewarded with a lively presentation by children’s book author <a href="http://salinayoon.com/HOME.html">Salina Yoon</a>. She accomplished the rare feat of entertaining and educating a group of both kindergartners and adults.</p><p>Salina moved to the United States as a child and, not knowing English, faced the challenges thereof. She couldn’t read the books at school or the library. But what she could — and did — do was to <em>read the pictures</em>. As she explained it, reading the pictures is more than a quick glance at each picture; it’s examining a book’s illustrations with the aim of getting inside the story, uncovering a character’s motivations, picking up nuance that doesn’t come through in the text. Reading the pictures as a child hooked her on books even when she couldn’t read the words, and it led her to become the author — and illustrator — of well over 100 books.</p><p>As one who creates online this concept resonated with me. Today’s web is driven by imagery. It’s the norm to feature a full-width image as the initial and primary element on a homepage, with a few words and perhaps a button laid nicely overtop of it. Lists on websites are now often replaced with cards or boxes, each featuring a small picture.</p><p>This heavy reliance on images to tell the story isn’t bad. People are visual creatures and we appreciate what the image offers to our senses. In practice, however, the actual photos selected on websites are loosely related to the topic at hand. Instead they are all-too-often confusing (<em>what does this have to do with anything?</em>) or overused (<em>I’ve seen this stock photo before…</em>) or irrelevant (<em>was there an image there? I didn’t notice</em>).</p><p>Image selection matters. As Salina noted, sometimes the pictures say more than the words. As a visitor to your website the pictures you include speak to me on many levels. They set a tone (dark or light, playful or serious, professional or casual). They show me faces (smiling or laughing) or places. I notice the quality of the photos (this looks stretched), and I get a sense for how much effort you put into your image selection.</p><p>A website is the first place many people meet your organization. Like a child reading the pictures in a book, people are reading the pictures on your website. What do they say?</p><p><em>Need help selecting the right pictures? Let us know how we can work with you, today: </em><a href="https://fiatinsight.com/contact"><em>https://fiatinsight.com/contact</em></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2bead4db7f49" width="1" height="1" alt=""><hr><p><a href="https://medium.com/fiatinsight/use-images-yes-but-be-selective-2bead4db7f49">Use images, yes. But be selective.</a> was originally published in <a href="https://medium.com/fiatinsight">Fiat Insight</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Simple user signups with Rails]]></title>
            <link>https://medium.com/fiatinsight/simple-user-signups-with-rails-fa6fbd18f337?source=rss----a01bacb00b29---4</link>
            <guid isPermaLink="false">https://medium.com/p/fa6fbd18f337</guid>
            <category><![CDATA[design]]></category>
            <category><![CDATA[productivity]]></category>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[ruby-on-rails]]></category>
            <dc:creator><![CDATA[Andrew Haines]]></dc:creator>
            <pubDate>Mon, 30 Apr 2018 22:39:12 GMT</pubDate>
            <atom:updated>2018-04-30T22:39:12.132Z</atom:updated>
            <content:encoded><![CDATA[<h4>Basic design patterns to help ease the pain</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-B5mZcpvyrOQyHKNn68s5w.jpeg" /></figure><p>Most of our Rails apps include some type of authentication account for end users. That’s easy enough to do, especially with a gem like <a href="https://github.com/plataformatec/devise">Devise</a>. Since Rails provides so much room to maneuver, however, we try hard to maintain a simple design matrix for envisioning on-boarding, and for automating much of the logic we lean on for deeper app functionality. It’s not rocket science, but it can make running and maintaining your app, and the new user experience, much easier.</p><h4>Separate signup concerns</h4><p>The first thing to remember is that signups don’t have to do <em>all</em> the work. We favor separating user authentication from payment accounts whenever possible. That keeps concerns separated and models and controllers cleaner. We typically use the User class to handle all the signup logic, and something like an associated PaymentProfile or Customer (maybe even via an Account or Organization) to do other things. That’s a lot easier to maintain, especially when you start mixing in third-party services like the <a href="https://stripe.com/docs/api">Stripe API</a> to do other, fancy payment things.</p><h4>Forget passwords</h4><p>No matter, even simple signups can quickly get complicated. One way to reduce overhead is to minimize the amount of information required to create a login. Requiring only a couple of fields for signup — like an email, and maybe a name — and automating password creation helps with this.</p><p>You can use a before_validation callback to create a password, then deliver it to the user via <a href="https://postmarkapp.com/">Postmark</a>.</p><pre>before_validation :assign_password, on: :create<br>after_create :send_welcome_email</pre><pre>def assign_password<br>  if !self.password<br>    o = [(‘a’..’z’), (‘A’..’Z’), (‘0’..’9&#39;)].map { |i| i.to_a }.flatten<br>    new_password = (0…10).map { o[rand(o.length)] }.join<br>    self.password = new_password<br>    self.password_confirmation = new_password<br>  end<br>end</pre><pre>def send_welcome_email<br>  client = Postmark::ApiClient.new(&quot;#{Rails.application.secrets.POSTMARK_API_KEY}&quot;)<br>  client.deliver_with_template(<br>  {:from=&gt;&quot;from@yourdomaincom&quot;,<br>   :to=&gt;self.email,<br>   :template_id=&gt;12345,<br>   :template_model=&gt;<br>   {&quot;name&quot;=&gt;self.first_name,<br>    &quot;action_url&quot;=&gt;&quot;https://yourdomain.com/auth/secret/new?email=#{self.email}&quot;,<br>    &quot;login_url&quot;=&gt;&quot;https://yourdomain.com/auth/login&quot;,<br>    &quot;email&quot;=&gt;self.email,<br>    &quot;password&quot;=&gt;self.password,<br>    &quot;support_email&quot;=&gt;&quot;support@yourdomain.com&quot;}}<br>  )<br>end</pre><p>Of course, this is a baseline. You can do a lot more for security with expiring passwords, tokens, etc. In this case, the user would be given an option to set a new password immediately from a link in the welcome email, tapping into the default Devise routing.</p><h4>Tokenize everything</h4><p>Creating a token for a record is a low-cost idea that affords a lot of downstream flexibility. You can pass tokens around to identify things more securely, both within your app and outside of it.</p><p>Tokenize your new User by calling include Tokenable on the model and writing a concern:</p><pre>module Tokenable<br>  extend ActiveSupport::Concern</pre><pre>  included do<br>    after_create :create_token<br>  end</pre><pre>  def create_token<br>    o = [(&#39;a&#39;..&#39;z&#39;), (&#39;A&#39;..&#39;Z&#39;), (&#39;0&#39;..&#39;9&#39;)].map { |i| i.to_a }.flatten<br>    token = (0...50).map { o[rand(o.length)] }.join<br>    self.update_attributes(token: token)<br>  end<br>end</pre><p>That’ll fire every time a new user is created. Now you can more securely tie things to a user in other methods and classes throughout your app with User.find_by(token: params[:user_token]).</p><h4>Extend signups to MailChimp</h4><p>Another highly-desired workflow is subscribing new users to a MailChimp list. You can do that instantly with a callback on the same User class using the <a href="https://github.com/amro/gibbon">Gibbon</a> gem.</p><pre>after_commit :sign_up_on_mailchimp, on: :create</pre><pre>def sign_up_on_mailchimp<br>  begin<br>    gibbon = Gibbon::Request.new(api_key: &quot;#{Rails.application.secrets.MAILCHIMP_API_KEY}&quot;)<br>    gibbon.lists(&quot;abcde12345&quot;).members.create(body: {email_address: &quot;#{self.email}&quot;, status: &quot;subscribed&quot;, merge_fields: {FNAME: &quot;#{self.first_name}&quot;, LNAME: &quot;#{self.last_name}&quot;}})<br>  rescue Gibbon::MailChimpError =&gt; e<br>    puts &quot;Houston, we have a problem: #{e.message} - #{e.raw_body}&quot;<br>  end<br>end</pre><h4>Put things into background jobs</h4><p>Any of these functions can be pushed to a background job, instead. We prefer using <a href="https://github.com/mperham/sidekiq">Sidekiq</a> and <a href="http://edgeguides.rubyonrails.org/active_job_basics.html">Active Job</a>. Jobs make models slimmer by compressing larger functions into fewer lines of code. They can also make finding and working on functions a little easier, especially if you carry this design pattern forward to other parts of your app. And, of course, they improve user-side performance by removing the wait time required to process a bunch of requests.</p><p>Instead of the MailChimp callback, above, you could instead write:</p><pre>after_commit -&gt; { Subscription::CreateMailchimpSubscriptionJob.set(wait: 10.seconds).perform_later(self) }, on: :create</pre><p>This could refer to a job at app/jobs/subscription/create_mailchimp_subscription_job.rb:</p><pre>class Subscription::CreateMailchimpSubscriptionJob &lt; ApplicationJob<br>  queue_as :default</pre><pre>  def perform(new_user)<br>    # Functional code here...<br>  end<br>end</pre><p><em>Need a partner to help you build a streamlined, fast, and secure subscription app? Let us know how we can work with you, today: </em><a href="https://fiatinsight.com/contact"><em>https://fiatinsight.com/contact</em></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=fa6fbd18f337" width="1" height="1" alt=""><hr><p><a href="https://medium.com/fiatinsight/simple-user-signups-with-rails-fa6fbd18f337">Simple user signups with Rails</a> was originally published in <a href="https://medium.com/fiatinsight">Fiat Insight</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Using the MailChimp API to check a WordPress user’s subscription status]]></title>
            <link>https://medium.com/fiatinsight/using-the-mailchimp-api-to-check-a-wordpress-users-subscription-status-4db55649c648?source=rss----a01bacb00b29---4</link>
            <guid isPermaLink="false">https://medium.com/p/4db55649c648</guid>
            <category><![CDATA[php]]></category>
            <category><![CDATA[mailchimp]]></category>
            <category><![CDATA[wordpress]]></category>
            <category><![CDATA[email-marketing]]></category>
            <category><![CDATA[api]]></category>
            <dc:creator><![CDATA[Ben Zumdahl]]></dc:creator>
            <pubDate>Fri, 06 Apr 2018 16:35:24 GMT</pubDate>
            <atom:updated>2018-04-06T16:35:23.999Z</atom:updated>
            <content:encoded><![CDATA[<h4>Is this user on my MailChimp list?</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*tstG1PbD53EP2Whdv46aMQ.jpeg" /></figure><p>Many of our clients with WordPress websites use MailChimp for email marketing. Its barrier to entry is nonexistent (free!), the interface is top notch, and website integrations abound: MailChimp has an <a href="https://wordpress.org/plugins/mailchimp/">official plugin</a>, form providers like <a href="https://www.gravityforms.com/add-ons/mailchimp/">Gravity Forms offer add-ons</a>, and third party plugins <a href="https://wordpress.org/plugins/search/mailchimp/">are numerous</a>.</p><p>But here’s a scenario these integrations don’t address: <em>I want to know if the user who logs into my website is on my MailChimp list</em>. Based on this information (is this user a subscriber: yes or no) we can provide better prompts to the user and a better on-site experience. At a minimum, we can stop prompting the user to sign up — because we know she’s already signed up. Instead, we can prompt her toward another type of engagement.</p><p><strong>So, how to accomplish this? </strong>We turn to MailChimp’s API.</p><p>Version 3.0 of MailChimp’s API is <a href="http://developer.mailchimp.com/documentation/mailchimp/guides/get-started-with-mailchimp-api-3/">well documented</a> but it doesn’t provide any quick start examples for specific coding languages. This keeps it out of reach for developers not yet comfortable delving into and unpacking new APIs. Below is one way to use the API to tackle the basic task of <em>checking a specific user’s email address to see if it is on a particular MailChimp list</em>.</p><p>Here’s the code — scroll down for a few tips on using it:</p><pre>function get_subscriber_mailchimp_status($user_login, $user) {</pre><pre>$api_key = &#39;mailchimp_api_key&#39;;<br>$list_id = &#39;mailchimp_list_id&#39;;<br>$us = &#39;mailchimp_us&#39;; // eg, &#39;us5&#39; or &#39;us7&#39;</pre><pre>$args = array(<br>    &#39;headers&#39;     =&gt; array(<br>      &#39;Authorization&#39; =&gt; &#39;Basic &#39; . base64_encode( &#39;user:&#39; . $api_key ),<br>      &#39;Access-Control-Allow-Origin&#39; =&gt; &#39;*&#39;,<br>    ),<br>  );</pre><pre>$email_address = $user-&gt;user_email;<br>$email_formatted = md5(strtolower($email_address));</pre><pre>$response = wp_remote_get( &#39;<a href="https://us7.api.mailchimp.com/3.0/lists/&#39;">https://&#39;. $us  .&#39;api.mailchimp.com/3.0/lists/&#39;</a>. $list_id .&#39;/members/&#39; . $email_formatted, $args );</pre><pre>$body = json_decode( wp_remote_retrieve_body( $response ) );</pre><pre>$mailchimp_status = $body-&gt;status;</pre><pre>if($mailchimp_status == &#39;subscribed&#39;):<br>    update_user_meta( $user-&gt;ID, &#39;user_mc_subscriber_status&#39;, &#39;yes&#39; );<br>  else:<br>    update_user_meta( $user-&gt;ID, &#39;user_mc_subscriber_status&#39;, &#39;no&#39; );<br>  endif;</pre><pre>}</pre><pre>add_action(&#39;wp_login&#39;, &#39;get_subscriber_mailchimp_status&#39;, 10, 2);</pre><p>There are three variables you need to set to make this work:</p><ol><li>$api_key: Create and add a MailChimp API key</li><li>$list_id: Get the ID of the MailChimp list you want to use</li><li>$us: When you log into MailChimp, the URL looks something like this: <a href="https://us9.admin.mailchimp.com/">https://us9.admin.mailchimp.com</a>. The number in ‘us9’ varies by account; just grab the three digits and use them as this variable.</li></ol><p>This function is set to run when a user logs into your website (see the last line of code above). You could hinge it on another action, but as is, each time a user logs in, his MailChimp subscriber status is checked. If the result confirms that he is a subscriber, then a custom meta field named ‘user_mc_subscriber_status’ is updated with the value of ‘yes’. If not, it is updated with a value of ‘no’.</p><p><strong>Now what?</strong></p><p>Now that you’re storing this yes/no value on the user record you can check that value and do something based on it. Here’s how to check it:</p><pre>if(get_user_meta(get_current_user_id(), &#39;user_mc_subscriber_status&#39;, &#39;true&#39;) == &#39;yes&#39;):</pre><pre>// do something for subscribers</pre><pre>else:</pre><pre>// do something for non-subscribers</pre><pre>endif;</pre><p>You can use this if-else check throughout the website to provide differentiated content for MailChimp subscribers and non-subscribers!</p><p><em>Want to take the next step and do even more with MailChimp on your WordPress website? Let us help you build a solution that’s just right for your needs: </em><a href="https://fiatinsight.com/contact"><em>https://fiatinsight.com/contact</em></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4db55649c648" width="1" height="1" alt=""><hr><p><a href="https://medium.com/fiatinsight/using-the-mailchimp-api-to-check-a-wordpress-users-subscription-status-4db55649c648">Using the MailChimp API to check a WordPress user’s subscription status</a> was originally published in <a href="https://medium.com/fiatinsight">Fiat Insight</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[One secret to social media marketing success]]></title>
            <link>https://medium.com/fiatinsight/one-secret-to-social-media-marketing-success-f2c69da3c84c?source=rss----a01bacb00b29---4</link>
            <guid isPermaLink="false">https://medium.com/p/f2c69da3c84c</guid>
            <category><![CDATA[productivity]]></category>
            <category><![CDATA[business]]></category>
            <category><![CDATA[social-media]]></category>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[marketing]]></category>
            <dc:creator><![CDATA[Andrew Haines]]></dc:creator>
            <pubDate>Mon, 15 Jan 2018 18:43:29 GMT</pubDate>
            <atom:updated>2018-01-15T18:43:28.439Z</atom:updated>
            <content:encoded><![CDATA[<h4>Show up with lots of money, or probably just don’t try</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*MiF2pEh0d_YOPmGoKSQejg.jpeg" /></figure><p>Okay, here it is, the one secret to social media marketing success. Ready?</p><blockquote>Show up with <strong>lots</strong> of money. And if you don’t have lots of money? Then <strong>probably</strong> just don’t try.</blockquote><h4>That’s a bummer</h4><p>Yes, it’s a bummer, but it’s mostly true. Sometimes it’s not; sometimes a little bit of money works to create a profit by social marketing. But that’s an outlier, and well within the acceptable margin of error. And in those cases, something else is filling in the gaps, anyway — sweat equity, viral promotion, or an insanely good idea, none of which are very predictable or cheap.</p><p>We don’t do social media marketing at Fiat Insight because we believe it’s a bad place for most of our clients to spend their money.</p><h4>That seems biased</h4><p>It’s not biased, really. If doing social media marketing turned $1 from a client into $2, we’d do it all day long so they’d have more money to spend on our other services. Experience says that basically never happens, though. And it’s not like Facebook is bad at placing content — they’re exceptionally good, in fact. It’s just that the best numbers really look more like turning $100k into $200k. The first $1k in isn’t profitable; the next $5k scratches the surface, and so on. Most people just don’t have that kind of budget.</p><h4>Why so negative?</h4><p>With rare exceptions, marketing is a ground game of trial and error, and fixing errors. Spending a little money is harmless, but you’ll quickly uncover things that don’t work — potential customers don’t convert, or your inventory listing isn’t correct, or something’s not working to capture payments, or whatever. So you make the fix (that costs time and money), then spend a little more on marketing. More trials, more errors, more fixing errors. If all goes well, after a few progressively larger cycles, you’re turning real revenue. But you’re still out the investments you’ve made to date, and you have to be able and willing to wait to recoup them.</p><p>That’s why doubling $100k is much more realistic than doubling $1, or even $1k. It’s easy to forget about the ancillary costs associated with marketing that aren’t “marketing” <em>per se</em>. And those rack up quickly. Given successful trial and error testing and a worthwhile product, eventually you won’t run a deficit. But the breakeven point is going to be a lot higher than the marginal value of the thing you’re trying to sell (think widgets or services). <em>Or</em>, the thing you’re trying to sell is at such a high value that the trial and error cycle is slowed to a crawl (think real estate).</p><h4>So what do to?</h4><p>If you’ve got a lot of money to spend, just do what everyone says to do. No argument from me. Facebook promotion works because Facebook wouldn’t make tons of money if it didn’t. The rich get richer: Brand promotion, including “organic” reach, is more expensive than ever, and will continue to be.</p><p>If you don’t have lots to spend, be decisive to minimize the errors and adjustments you’ll eventually need to make once you start marketing,<em> or even if you never plan to market</em>. Come up with a way to make your product simpler, or to reduce the different versions a customer can buy. Invest in strong branding, content, and customer support documentation <em>before</em> you need it. Work through your site with conversion optimization in mind to decide what paths make sense, which ones don’t, and how you’ll best funnel traffic. Install some competent metrics tracking— and someone to analyze them — so you know you’re working with real data.</p><h4>Little data, little problems</h4><p>Think about it this way. If you got 100 users to your site right now, what would you do with them? What are your current conversion rates? What’s the value of your product that you can sell to that converted user base? Are you being responsible with the potential customers you have? Or are you abusing or neglecting them? (Bonus question: How much have you <em>already had to pay</em> to get those users?)</p><p>Now, imagine you’ll have to pay to get another 100 users to your site. (Realistically, let’s say, the cost per user would be somewhere above $2 each, maybe a lot higher.) Your conversion rate would ideally be similar to the first 100, but might actually be a lot worse until your ad design is perfectly thought-up and placed. At the (relatively) increased sales values, would your marketing — the raw costs, ad design, analytics, development, strategy, customer support, etc. — pay for itself? Would it be anywhere close? What’s the real revenue value of a single paid customer? And how many of those do you need to break even? What’s the timeline? Are there better ways for you to get to profitability more quickly and easily?</p><h4>Big data, big problems</h4><p>Jumping too far ahead obscures the simple calculations that make social media marketing a bad choice for most. On the surface, the secret to success is about how much money you have, need, and are willing to spend. A little deeper, it’s a secret of <a href="https://medium.com/fiatinsight/being-organized-makes-you-better-dce8f99a0c71">breaking the cycle</a> of running down bad decisions just because they’ve been decided.</p><p>Willingness to complete the things you start is a sign of dedication. But carefully deciding what things you <em>should</em> start, and <a href="https://medium.com/fiatinsight/projects-are-planning-75b0a69e89fe">preparing for them deliberately</a>, is a sign of maturity and practical wisdom.</p><p><em>Fiat Insight won’t do your social media marketing, but we will build you a great platform that makes it easier for you to be responsible with your leads and sell your products. Let’s talk! </em><a href="https://fiatinsight.com/contact"><em>https://fiatinsight.com/contact</em></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f2c69da3c84c" width="1" height="1" alt=""><hr><p><a href="https://medium.com/fiatinsight/one-secret-to-social-media-marketing-success-f2c69da3c84c">One secret to social media marketing success</a> was originally published in <a href="https://medium.com/fiatinsight">Fiat Insight</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>