<?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 Rob Jones on Medium]]></title>
        <description><![CDATA[Stories by Rob Jones on Medium]]></description>
        <link>https://medium.com/@robjones_14838?source=rss-dca61e266928------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*r9DpXZbvRErC0X9A3Ud7uA.jpeg</url>
            <title>Stories by Rob Jones on Medium</title>
            <link>https://medium.com/@robjones_14838?source=rss-dca61e266928------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 07:09:45 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@robjones_14838/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[A simple workflow for Wordpress developers]]></title>
            <link>https://medium.com/@robjones_14838/a-simple-workflow-for-wordpress-developers-71b0ae7eddd?source=rss-dca61e266928------2</link>
            <guid isPermaLink="false">https://medium.com/p/71b0ae7eddd</guid>
            <category><![CDATA[sass]]></category>
            <category><![CDATA[git]]></category>
            <category><![CDATA[developer-tools]]></category>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[wordpress]]></category>
            <dc:creator><![CDATA[Rob Jones]]></dc:creator>
            <pubDate>Wed, 07 Feb 2018 14:58:24 GMT</pubDate>
            <atom:updated>2018-02-09T21:15:22.444Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/640/1*9CRSQxuPKn-U3EH_-oPCAQ.jpeg" /></figure><p>Every developer has their own workflow that they swear by, it’s usually something that’s constantly evolving.</p><p>Here’s mine, feel free to shout at me in the comments.</p><p>Tools used:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/723/1*6KAgVde5C0GSq4SicBocvQ.png" /><figcaption>Local by Flywheel, Atom and Codekit</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/728/1*4x6coLmt9GigF5WYMSfzuQ.png" /><figcaption>Bitbucket, Sourcetree and BackupBuddy</figcaption></figure><h3>Setting up the local environment</h3><p>There’s a lot of developers out there that still use <a href="https://www.mamp.info/en/">MAMP</a>, up until recently I was one of those developers. There’s nothing inherently wrong with it but there are some inefficiencies.</p><p>Having to manually create a database just seemed unnecessary not to mention mind numbing! That’s when I decided it was time to move.</p><p>This led me to <a href="https://local.getflywheel.com/">Local by Flywheel</a>. Cue a mind-blown gif…</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/640/1*Dp6WKBTOn04Q8YEJE6QIkw.gif" /></figure><p>One click installs and imports, local live links, blueprints, ability to switch between PHP versions… yes, it’s good, it’s very good.</p><p>Now you’ve got your environment setup, onto the coding part.</p><h3>Your code is beautiful on the outside</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/480/1*_TxUHOvlCuSCapSkadjVzQ.gif" /></figure><p>It’s good practice to code as neatly as possible but sometimes you need a helping hand. I use <a href="https://atom.io/">Atom</a> as my editor of choice as it has very little distractions and just generally looks nice to use. There’s also a tonne of plugins for it, like removing trailing whitespace to neaten things. But that’s just one, the list really is endless so it’s all down to your personal preference.</p><p>The second piece of software I use is <a href="https://codekitapp.com/">Codekit</a>. I really can’t say enough about this as it’s a huge time saver. Especially with SASS…</p><h3>S(aving my)ASS</h3><p>SASS, what would we do without it. Not only will it save you time whilst coding (ahhh, glorious variables) but using Codekit means you won’t have to touch any command lines to compile it.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/498/1*TdGDr4CKbRbr47kQInLgZw.gif" /></figure><p>The compile and browser refresh on save features of Codekit will instantly make you more efficient… imagine the time saved when you multiply that by the life span of the project!</p><h3>Wait, what about GIT?</h3><p>So you’ve got your code sorted but no workflow would be complete without GIT. I hope this goes without saying that all changes are being pushed to <a href="https://github.com/">Github</a> or <a href="https://bitbucket.org/">Bitbucket</a> at sensible times. <a href="https://www.sourcetreeapp.com/">Sourcetree</a> is another good tool to use without touching the command line.</p><p>I won’t go into a huge amount of detail (that’s a whole article!) but as developers, we’ve all tried to push our changes before the other developer so we don’t have to deal with any merge issues! (Yes, I’m that person!)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/480/1*f8MNDpoVFEytncn1N5qDdw.gif" /></figure><p>Anyways, back to the environments.</p><h3>Moving to the staging environment</h3><p>Ah the staging environment or better known as URL hell. This has been a long standing issue for many developers, moving Wordpress quickly and easily.</p><p>I’ve tried many ways to move Wordpress, some have even suggested using various command line tools. NO! Just, no! I hate the command line… there I said it.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/480/1*cXOaGXjXHvudOks7yE-NQA.gif" /></figure><p>THE easiest way is to use a tool that has never failed for me… <a href="https://ithemes.com/purchase/backupbuddy/">BackupBuddy</a>.</p><p>Once you’ve setup your database on your staging environment, it’s just a case of SFTP’ing the file up. Yes I said SFTP. Hipster developers might want to leave now.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/480/1*wA-LSpVhxRSzO2g2KUtApA.gif" /></figure><p>I know it’s not the cool way to transfer files but it’s the easiest that’s for sure.</p><h3>Tying the environments together</h3><p>One of the great features in BackupBuddy is the ability to push/pull between the environments using remote destinations.</p><p>There’s only one rule, always work on the local environment. If the website is live then always pull from there first, then you can make your local changes. You can then push to the various environments depending on the stage you’re at.</p><p>You’ll definitely need to make use of pushing/pulling once you’re stuck in an endless loop of changes from the client (<a href="https://bugherd.com/">Bugherd</a> is great for tracking bugs).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/380/1*XP7QdQN2GH6B5qGcLES0fQ.gif" /></figure><h3>Setting up the live environment</h3><p>You’ve made it to the “yes, please put the website live” stage!</p><p>Again, make use of BackupBuddy and just go through the same process you did to setup the staging site. Hopefully this is the easy part!</p><p>The site is now live… you can calmly leave the office.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/410/1*Gt0mA_eO4-BzozVKGW9g_A.gif" /></figure><h3>Listen up team of developers!</h3><p>There’s admittedly one hole in this workflow, working in a team of developers. Now I love Local by Flywheel but MAMP wins when it comes to working in a team.</p><p>At the moment, Flywheel doesn’t allow the team to all run from one database (but it maybe something they look at in the future). If you’re a solo developer then stick with Flywheel, if you’re in a team then (sadly) use MAMP.</p><p>But, just in case you need a team setup then this will work well using MAMP:</p><p>We used three computers, each had MAMP running and each started off with the same version of the site installed (use BackupBuddy to quickly deploy the site on all computers).</p><p>You need to be all running on the same version of the database as merging a one will give you all kinds of nightmares. So all developers need to point at one database on one of the computers by changing the wp-config.php in each of their own setups to:</p><p>define( ‘DB_HOST’, ‘192.168.1.75:3306’ );<br>(That’s the IP of one computer followed by the port)</p><p>That will ensure you’re all reading the same database and therefore all changes are mirrored across the computers without any database merge complications.</p><p>To sync files that’s where GIT comes in, use Sourcetree to push/pull changes to/from Bitbucket.</p><p>That will keep both the database and files in sync for all developers. This process can be used for an unlimited amount of developers to all work on the same website at the same time with minimum fuss.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/476/1*Oord8iTQ3kTRZhiw_0o7_Q.gif" /></figure><h3>Nothing is set in stone</h3><p>This whole setup is fairly modular so elements can be switched in and out depending on your preference but the important thing to note is that it’s ever evolving. For me personally my focus is on efficiency, I want to develop as quickly as possible without getting bogged down in the process.</p><p>Developers have a tendency to use the latest cool software without actually asking “does this make my process quicker and easier?”. There’s no right or wrong way to do it, it’s what works best for you.</p><p>Feel free to shout at me in the comments below, I’d love to hear alternate workflows or improvements.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=71b0ae7eddd" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>