When it’s your job to promote and nurture the brands of your clients, developing and promoting your own brand can often be an even tougher job. As people, we tend to define ourselves and those around us by what we do.  It’s only natural, but when you begin to define your brand around what you do rather than who you are, you will only end up selling yourself short.

Read the rest of this entry »

Well, it’s been one very busy summer here, at MetaSpring! Unfortunately, we were forced to go on a bit of a blogging hiatus in order to keep up with everything, but we’re back now and we’re doing better than ever! These last few months have given us the opportunity to re-examine our goals as a company and re-assess the tools and methodologies that we employ – resulting in some very exciting changes for MetaSpring.

Read the rest of this entry »

What is Nofollow, Dofollow?

Nofollow is an attribute that can be added to a hyperlink preventing Google from passing link credit to that site rel=”nofollow”. Link credit is one of the major factors Google considers when determining how authoritative your site is. You will these tags on to blog comments, and on sites like Wikipedia. It was created to fight dirty spammers, spam bots, and anyone trying to get a free link without adding any value to the site.

Dofollow is the practice of removing the nofollow tag from your links. In certain circles it is becoming the “in thing” to spread the link love.

Example badge from U Comment I Follow wordpress plugin

Pros

Share the Link Love

If a webmaster posts a legitimate comment, then does it really hurt to share the link love? Everyone wants to build their link popularity, but if it can be done by helping to contribute to other’s thoughts and ideas then it seems natural.

Reward people for taking the time to write quality comments

You don’t need to accept every comment. One that is not legit usually screams spam.

Discount Canadian Pharmacy Says:
“Your post is good. I know many peoples who also have this problem”

It isn’t hard to filter out the blatant spam. If you get hundreds of comments to your blog, then you might want to consider the Link Love Plugin, which allows you to specify the number of comments required before the visitor gets a link credit.

If you are interested in dofollow plugins Andy Beard has The Ultimate List Here. He has become a dofollow evangelist, with a great amount of information about the good, the bad, and the ugly of the dofollow movement

Encourage cross linking across sites

Allowing link credit naturally encourages cross linking amongst similar sites. You say legitimate comments should come from the heart right? As an SEO, much of my time is spent link building as opposed to leisure blog reading. If I can provide a meaningful comment to a blog and gain a backlink as a result, I will read and contribute everywhere that I can.

Note: You have to actually READ the article, and write a comment that isn’t limited to “Nice”, or “Cool…”. You still have to read articles and posts that interest you, so you can provide a meaningful contribution.

Cons

May cause comments to be less genuine

If you advertise your dofollow blog, chances are you are going to get more spam. This is just a natural result of sticking your bleeding finger into an ocean of sharks. You may start to get comments from people who just breeze over the article, and post a comment. This amigos, is called manual comment spam.

Not to say that these comments aren’t genuine, but you just have to be a little more careful while accepting comments.

Too many external links

If you have a lot of comments for a particular post, you might end up with hundreds of external links. This has been known to dilute the sites page rank, and cause it to loose favor with Google.

Vandelay experienced a direct decrease in traffic after removing the nofollow link. Read the post here.

Bad Neighborhood

You might have people who write genuine comments, but link to a bad neighborhood… EG link farms, spam sites etc. If your site passes link credit, then you might get penalized.

Conclusion

I am all for giving back to contributing readers, but it requires a careful watch. Removing the nofollow attribute might be something to consider if you have time to ensure the commenting doesn’t get out of hand. Plugins like the Link Love plugin, allow you to give something back, while still maintaining the integrity of both your posts and your posts page rank.

Over the last few years, micro-blogging has spread to the masses and everyone from Barack Obama to the New York Times to Amazon has joined in the fun. Essentially (and according to my dear friend, Wikipedia),

Micro-blogging is a form of blogging that allows users to write brief text updates (usually less than 200 characters) and publish them, either to be viewed by anyone or by a restricted group which can be chosen by the user. These messages can be submitted by a variety of means, including text messaging, instant messaging, email, MP3 or the web.

Some of the most popular independent micro-blogging services are Twitter, Jaiku, Tumblr, and Pownce. But even existing platforms like Facebook and MySpace have begun building in various types of micro-blogging functionality.

Read the rest of this entry »

Rails Migrations provide an easy way to make versioned revisions to your database structure over a period of time. When used properly they can make it easy to make modifications to your existing database programmatically as you need to make changes. This is extremely helpful for large up-and-running projects, but what about projects that are still in development? I don't know about you but for me, after working on large project for awhile there can be a ridiculous number migrations sitting around. It's also quite possible that a good portion of your earlier migrations have been nullified by other migrations later on. When you start throwing data into your migrations this can quickly become a tangled patchwork web of evil.

While migrations are extremely helpful for making modifications on production systems, we have found that having a pile of migration revisions really doesn't serve much purpose during the development cycle. This is especially true if you are not needing to work with live data and you have access to a good code repository like SVN. So during the development cycle for most of our Rails related projects we maintain one large initialization migration, an installation shell script, and a refresh shell script. The large migration handles the standard migration goodness, any type of data import, and other dynamic data installation initialization procedures. The installation script is run once to deploy the application on a new system; it typically sets up the database, runs the initialization migration, and handles whatever other settings you need for deployment. The refresh script simply refreshes the database and reruns the initialization migration; this is used when the migration is updated.

Below is a very simple example of how we put this idea to use:

Database Initialization Migration - 001_initialize_database.rb

require 'active_record/fixtures'
 
class InitializaDatabase < ActiveRecord::Migration
  def self.up
 
    # Initialize fixture array
    # This array is used to load a list of fixtures that will be loaded into the database at the end of the installation process
    fixture_array = []
 
    # It's important to use the :force option if you are not going to drop tables in your down method
    # this forces tables to be overwritten if they are already present
    create_table :customer, :force => true do |t|
      t.column :name, :string
    end
 
    # Add to fixture array
    fixture_array << :client
 
    # CREATE REMAINING TABLES
 
    # Load fixture data
    Fixtures.create_fixtures('db/fixtures', fixture_array)
  end
 
  def self.down
  end
end

Installation SQL Script - install.sql

CREATE DATABASE database_name_dev;
CREATE DATABASE database_name_pro;
CREATE DATABASE database_name_test;
GRANT ALL privileges ON database_name_dev.* TO 'user'@'localhost' IDENTIFIED BY 'password';
GRANT ALL privileges ON database_name_pro.* TO 'user'@'localhost';
GRANT ALL privileges ON database_name_test.* TO 'user'@'localhost';

Installation Shell Script - install.sh

#!/bin/bash
 
mysql -u root --password=password -e "source install.sql"
rake db:migrate

Refresh Shell Script - refresh.sh

#!/bin/bash
 
rake db:migrate VERSION=0
rake db:migrate

Then to install on a system we simply run install.sh from the command line.

> ./install.sh

If a change is made to the schema we run refresh.sh from the command line.

> ./refresh.sh

Since refreshing the database wipes the database clean and reloads each time, its really only useful until you have reached a final stage of deployment. Hopefully by that time though you will have a relatively stable db structure and won't need to be adding a butt-load of migrations.

It's really a relatively simple concept, but I can't tell you how much time we have saved in deployment using this methodology. We'd love to hear your ideas and deployment strategies.