<?xml version="1.0" encoding="utf-8"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
<title type="text">Satellite</title>
<generator uri="https://github.com/mojombo/jekyll">Jekyll</generator>
<link rel="self" type="application/atom+xml" href="/feed.xml" />
<link rel="alternate" type="text/html" href="" />
<updated>2013-08-16T19:11:53+10:00</updated>
<id>/</id>
<author>
  <name>Japh</name>
  <uri>/</uri>
  <email>japh@satellitedev.com</email>
</author>


<entry>
  <title type="html"><![CDATA[Developing WordPress Plugins]]></title>
  <link rel="alternate" type="text/html" href="/articles/developing-wordpress-plugins" />
  <id>/articles/developing-wordpress-plugins</id>
  <updated>2013-08-16T00:00:00-00:00</updated>
  <published>2013-08-16T00:00:00+10:00</published>
  
  <author>
    <name>Japh</name>
    <uri></uri>
    <email>japh@satellitedev.com</email>
  </author>
  <content type="html">&lt;p&gt;When you need to extend the functionality of your WordPress site, you build a plugin (or you get us to build one for you!)&lt;/p&gt;

&lt;p&gt;Some people will tell you that you could put the functionality into your theme instead. They might even tell you that having too many plugins will slow down your site.&lt;/p&gt;

&lt;p&gt;Those people are misinformed. So, let’s stop the cycle of misinformation right here:&lt;/p&gt;

&lt;ol&gt;
  &lt;li&gt;
    &lt;p&gt;You can have hundreds of plugins installed on your WordPress site without negative side effects. The proviso is, they need to be well-coded and play nicely together.&lt;/p&gt;

    &lt;p&gt;This is where they get the bad reputation for causing slowness from: often they aren’t well coded, people install plugins with overlapping functionality (causing conflicts), and often they have more functionality than is actually needed.&lt;/p&gt;

    &lt;p&gt;There’s also no difference in performance by having this code in your theme instead of in a plugin. The code from ten troublesome plugins will be just as troublesome if you copy and paste it into your theme instead.&lt;/p&gt;
  &lt;/li&gt;
  &lt;li&gt;
    &lt;p&gt;Keeping things separated and modular is a good thing. Seeing as there’s no detrimental affect on performance by having code in plugins, why not embrace the organisational benefits?&lt;/p&gt;

    &lt;p&gt;If you need to turn specific functionality off temporarily, you can easily do so.&lt;/p&gt;

    &lt;p&gt;If you’re experiencing a problem and need to troubleshoot what’s causing it, it’s much easier to identify where it’s coming from.&lt;/p&gt;

    &lt;p&gt;If you need some extra work done to customise it, it’s much simpler for a developer to get familiar with, and then modify, a plugin than a monstrous theme full of a variety of functionalities that may, or may not, be linked.&lt;/p&gt;
  &lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;I’m sure the myth of “plugins are bad!” will continue on, but hopefully, you and I can now explain to others that it &lt;em&gt;is&lt;/em&gt; a myth.&lt;/p&gt;

  &lt;p&gt;&lt;a href=&quot;/articles/developing-wordpress-plugins&quot;&gt;Developing WordPress Plugins&lt;/a&gt; was originally published by Japh at &lt;a href=&quot;&quot;&gt;Satellite&lt;/a&gt; on August 16, 2013.&lt;/p&gt;</content>
</entry>


<entry>
  <title type="html"><![CDATA[[Updated] Selling Services on Microlancer]]></title>
  <link rel="alternate" type="text/html" href="/articles/selling-services-on-microlancer" />
  <id>/articles/selling-services-on-microlancer</id>
  <updated>2013-07-27T00:00:00-00:00</updated>
  <published>2013-07-27T00:00:00+10:00</published>
  
  <author>
    <name>Japh</name>
    <uri></uri>
    <email>japh@satellitedev.com</email>
  </author>
  <content type="html">&lt;p&gt;If you’ve not heard of &lt;a href=&quot;http://microlancer.com&quot;&gt;Microlancer&lt;/a&gt;, it’s a relatively new marketplace for digital professionals to sell their services. They’re still in “beta”, as they gradually add more services.&lt;/p&gt;

&lt;p&gt;Currently they sell predominantly design services, and they &lt;a href=&quot;http://wp.tutsplus.com/articles/news/the-best-place-for-wordpress-devs-to-get-design-work-done/&quot;&gt;recently announced&lt;/a&gt; that they’re soon going to be adding code services!&lt;/p&gt;

&lt;p&gt;We plan to be selling some of our services via Microlancer in the near future, specifically WordPress-based services such as plugin development and theme customisation.&lt;/p&gt;

&lt;p&gt;Keep an eye out for updates  :)&lt;/p&gt;

&lt;p&gt;[ Update ] : Code services are now live on Microlancer! You can hit us up for jobs via &lt;a href=&quot;https://www.microlancer.com/users/Japh&quot;&gt;Japh’s profile&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;We currently offer the following services through Microlancer:&lt;/p&gt;

&lt;ul&gt;
  &lt;li&gt;&lt;a href=&quot;https://www.microlancer.com/explore/wordpress-customization/2935-wordpress-theme-customization&quot;&gt;WordPress Theme Customization&lt;/a&gt;&lt;/li&gt;
  &lt;li&gt;&lt;a href=&quot;https://www.microlancer.com/explore/wordpress-plug-ins/2939-custom-wordpress-plugin-development&quot;&gt;Custom WordPress Plugin Development&lt;/a&gt;&lt;/li&gt;
  &lt;li&gt;&lt;a href=&quot;https://www.microlancer.com/explore/wordpress-plug-ins/3104-wordpress-plugin-customization&quot;&gt;WordPress Plugin Customization&lt;/a&gt;&lt;/li&gt;
  &lt;li&gt;[Coming Soon] Convert Your WordPress Theme Into a Jekyll Theme&lt;/li&gt;
&lt;/ul&gt;


  &lt;p&gt;&lt;a href=&quot;/articles/selling-services-on-microlancer&quot;&gt;[Updated] Selling Services on Microlancer&lt;/a&gt; was originally published by Japh at &lt;a href=&quot;&quot;&gt;Satellite&lt;/a&gt; on July 27, 2013.&lt;/p&gt;</content>
</entry>


<entry>
  <title type="html"><![CDATA[New Satellite Website]]></title>
  <link rel="alternate" type="text/html" href="/articles/new-satellite-website" />
  <id>/articles/new-satellite-website</id>
  <updated>2013-07-22T00:00:00-00:00</updated>
  <published>2013-07-22T00:00:00+10:00</published>
  
  <author>
    <name>Japh</name>
    <uri></uri>
    <email>japh@satellitedev.com</email>
  </author>
  <content type="html">&lt;p&gt;The Satellite website has had a refresh! The previous design was from 2009, so it had its day, and we’ve now moved to a new one.&lt;/p&gt;

&lt;p&gt;This new design is also a move from the flat HTML site we had before to a CMS. Nope, not WordPress, but Jekyll. Jekyll is Ruby software that generates a flat HTML site from dynamic files.&lt;/p&gt;

&lt;p&gt;Jekyll sites are something we’ll now be offering to clients also, which is pretty exciting!&lt;/p&gt;

&lt;p&gt;We’re looking to get some products of our own released this year, so it’s shaping up to be a pretty fun year here at Satellite.&lt;/p&gt;

&lt;p&gt;We’d also like to contribute more to open source software, and we’ve managed to do a little of that as part of this redesign. The redesign is actually a theme for Jekyll by Michael Rose, which we’ve customised. In the process, we also fixed an error, which we sent back to Michael and has been integrated into the original theme. It’s nice to give back.&lt;/p&gt;

&lt;p&gt;If you’re considering getting some custom WordPress work done, even a complete site, or interested in Jekyll, feel free to get in touch!&lt;/p&gt;

  &lt;p&gt;&lt;a href=&quot;/articles/new-satellite-website&quot;&gt;New Satellite Website&lt;/a&gt; was originally published by Japh at &lt;a href=&quot;&quot;&gt;Satellite&lt;/a&gt; on July 22, 2013.&lt;/p&gt;</content>
</entry>

</feed>