Working on WordPress projects can be a hassle. Especially if there’s more than one developer. There are a lot of files and chances are huge that you’ll be working on the same files quite often. This slows down development tremendously, not to mention the annoyance it causes.
You can fix the ‘working on the same file’ and ‘working on the live server’ issues quite adequately by using version control. I prefer Git, because of it’s distributed character. WordPress has another issue however, when trying to run the same site on different machines. Among the data it stores are urls, absolute urls.. This means that if you’d load a database dump from a live WordPress site into your local install, nothing will work correctly.
WordPress Project Creator [github] is a tool I created to streamline working on WordPress projects with multiple people. It does a couple of things:
- Download WordPress
- Create a new Git repo out of your wp-content folder or clone an existing wp-content folder into the WordPress folder
- Easily import database dumps by alterering absolute urls
- Create wp-config.php file
- Create .htaccess file
Adding new developers to your project is as easy as allowing them access to the Git repo and running wpprojectcreator. If you clone an existing project, the only things you’ll have to do is run the python script, import the dump using setup.php and you’re ready to work on the website as if it were live.
I released it on GitHub so everyone can give it a go. Or everyone.. at least everyone running OSX, Linux or 32bit Windows. Git on 64bit Windows can’t be installed in such a way that it’s accessible from the command line, which is required by wpprojectcreator. Be sure to read the README .
Check out WordPress Project Creator on GitHub.
I’ve had this article on my computer for three months now, but never got around to finishing it. Finally found some time to put it up.
It’s interesting to see that the standard process of thinking of something new, trying to figure out how to make money from it, creating it and then releasing it to the public seems to have changed. A business model does not necessarily come first anymore. A new process could be described similar to this: have an idea, create a very basic implementation and provide an extensive platform for people to use what you’ve created, hand it over to the community, now find a way to make money or hope for a takeover by some enterprise (Google). This makes new technology much more accessible than it’s ever been. A lot of effort is put into making it easy for other people to use and mashup what’s been created.
Detect and use
Needless to say a skill that’s becoming increasingly useful, is the ability to detect these services and find ways to implement them in your own concepts. YouTube, Twitter and Flickr have all been fully embraced by the community, which means the movies, images and messages they store show up on all kinds of applications. Some with a lot easier business model than the services they’ve incorporated. Twitter clients for instance, have a price tag or use adds to turn a profit, while Twitter is still struggling to find a way to make money.
Reasons to use public API’s
Does that mean Twitter is in trouble? Probably not, what they have is data and a lot of people who use that data. Apparently that’s worth multi million dollar investments. Money they need to provide a reliable system and store data the client applications are generating. Which is awesome, because you don’t have to worry about that anymore. It means you could create fairly extensive applications with a minimal amount of effort, as the services provide you with a solid backend.
Maybe the biggest benefit is popularity and content. It’s easier to use an existing user base than to create your own. Let’s say you want to create a website about the Olympic Games. You want visitors to contribute text, photos and videos. This would require quite a lot of work to create from scratch. Incorporating Twitter, Flickr and YouTube would reduce that dramatically. More importantly however, it would generate a lot more content, as it allows your audience to use the tools they’re already accustomed to.
What you have to take in consideration though, is that you’re not in direct control of the content you’re provided with. This may seem daunting at first and it makes the use of services unsuitable for some applications. It takes a new way of moderating the content you’re provided with. Both YouTube and Flickr allow you to only search through video’s and images that are marked safe. Other than that, it’s always a good idea to think about how you can stay in control of your own application.
Start your own projects
The list of services that are available right now seems endless. Some are more successful than others, obviously. Like I said, popularity is a good measure to determine if a service is worth checking out. To get you started, Programmable Web keeps an incredible list of public API’s. I’ve been spending a lot of time with the Google Apps API’s lately, which are pretty awesome and really allow for some cool applications. Especially if you look further than mashing up some of the individual components. For instance, it’s very easy to use Google Spreadsheet as a cloud database. How neat is that :)? Anyway, have fun!
Hey, do you have a Twitter account? Have you ever noticed those messages in which people tell you where they are? Pretty annoying, eh. Well, they’re actually also potentially pretty dangerous. I’m about to tell you why.
Don’t get me wrong, I love the whole location-aware thing. The information is very interesting and can be used to create some pretty awesome applications. However, the way in which people are stimulated to participate in sharing this information, is less awesome. Services like Foresquare allow you to fulfill some primeval urge to colonize the planet. A part of that is letting everyone know you own that specific spot. You get to tell where you are and if you’re there first, it’s yours. O, and of course there’s badges..
The danger is publicly telling people where you are. This is because it leaves one place you’re definitely not… home. So here we are; on one end we’re leaving lights on when we’re going on a holiday, and on the other we’re telling everybody on the internet we’re not home. It gets even worse if you have “friends” who want to colonize your house. That means they have to enter your address, to tell everyone where they are. Your address.. on the internet.. Now you know what to do when people reach for their phone as soon as they enter your home. That’s right, slap them across the face.
To raise some awareness on this issue and emphasize how easy it is to retrieve this information let me introduce: pleaserobme.com. Have fun and please don’t hook up Foursquare to your Twitter account, okay?
A few weeks ago Barry Borsboom and I had a funny idea for a twitter mash-up. We would basically measure your Twitter popularity in the form of a giant penis. Better know as the e-Penis. In order to see if we really created something to talk about, Seth Godin would call this the sneeze-factor, we registered an url: www.epenis.nl and we uploaded our e-Penis app with a few ‘share-this’ buttons. The first button to post it on Twitter, and the second one to Digg it. Would people share this site with their friends? How fast would it spread? All question a marketer would like to know when creating a viral marketing campaign right?
In our first day we managed to reach about 100 of our own friends on Twitter. But to really call it successful, we needed to reach some people on Twitter with a huge amount of followers. We used our own ‘Post on Twitter’ button a number of times on all sorts of people. And after a few tries @michielveenstra (2500 followers), picked up on our message and reposted our website on his own twitter stream on a friday. Overnight we reached 1500 hits. But as it turned out our biggest traffic came from a porn-blog! Apperently a webmaster from this well know porn-blog picked up our site after seeing it at @michealveenstra. In the weekend we managed to get around 8,000 hits, but on monday morning it really took off. Hordes of time wasting desk workers measured their body part. From that point on it really became a trend on Twitter. Our ‘Post on Twitter’ button was used a few times every few minutes now. Because people often measured the popularity off some well known people, they eventually couldn’t help but brag about (cough @stephenfry, 336.599 followers) ;). This caused Great Great Brittian to swarm our website and spread it even more. At this point North and South-America just woke up.
By the way, we were still hosting the website on my server, at my parents’ home. Utilizing almost all of the “massive” 1Mbit bandwith. Thank god my little brother didn’t complain. The reason this was even possible is that epenis.nl has no server-side scripts. It’s all jQuery, HTML, CSS and (small) images. We actually reduced the size of the website by half, by grabbing jquery.js from google.com.
At monday around 4 pm, CET, we finally managed to get the word Penis into the Twitter trending topics. A huge success, because now people twittered about why the word penis was in this list. Generating even more traffic to our site when they found out we were causing it.
Some people saw a connection between Spring Break, which probaly helped accepting the fact the word penis was a part of the list. Twitter however didn’t agree with that. After a few hours we saw some messages from people who were complaining about their twits disappearing, not much later penis wasn’t trending anymore. Did Twitter screw with us here? We can’t be sure. But the damage had already been done, we had spread to the American continent. A couple of big American Twitter users like @MrsKutcher, that’s Demi Moore (257,150 followers) posted about later in the evening, that really generated lots of traffic and added a large amount of females to our users, who seemed to have smaller e-peni. Which actually contributed to the credibility of the website.
The length of the penis most people we’re getting seemed to match what they expected. Which is funny, because we didn’t use a really complicated algorithm. Average people would get averige sizes (between 10 - 20 cm). While very popular twitterers, like celebrities, are showing extremely large numbers.
The next morning we had almost 40k in hits. We called our viral a success, we expected it to die out rather soon. But we were wrong! To our suprise it kept on going. Around 14:00 there was a huge spike in our traffic. As it appeared, @Guykawaski (92,399 followers) was giving a keynote during SES New York about ‘Twitter As A Tool For Social Media’. Lots of people posted live messages during his talk…
’@Searchcowboys: Guykawasaki shows epenis.nl and says it’s more powerfull then twittercounter :) #sesny’
And some stuff that made us laugh:
’@PaulIAm: Darwin just backed the car up to his grave, connected a hose to the tailpipe and took a deep breath…http://www.epenis.nl/’
’@Retecool: There’s lots of stuff out there that figures out your Twitter ranking, value, mojo, etc. But let’s cut the crap it’s all about who’s has the big swinging dick, right?’
’@Vatikan: Scheiße, @satan ‘s ePenis ist länger als meiner http://www.epenis.nl/’
At this moment we’re trying to figure out what the hell we’re are going to do with it. To conclude, here is a list of the things we learned:
- Use Sneezers, find Twitter users with respect and high amounts of followers. (Seth Godin’s Purple Cow)
- Post your viral at the right time. We had Spring Break, the SESNY Keynote by Guykawasaki and the usual monday morning boredom going for us.
- Maximize sharability. Our ‘Post on Twitter” button was used extremely well.
- Make it simple. There are no lists, links, pages. It does only one thing verry well. (KISS: Keep it Simple Stupid)
- Sex Sells