WordPress migration timeline

Beta period:

  1. Finish fixing photos
  2. Change colour of links and the search box
  3. Generally finish tweaking template
  4. Add Google Analytics tracking to WP blog
  5. Find a photo upload plugin akin to the Upload Photo tool in Blogger

Release:

  1. Shift Blogger blog to www.sindark.com/blogger
  2. Redirect from www.sindark.com to www.sindark.com/wp/
  3. Update any technorati style services as needed
  4. Discontinue updates to Blogger blog
  5. Fix internal links within WP blog

Optional:

  1. Fix internal links within Blogger blog

If done properly, this will only really cause turmoil for the search engines, which should be able to sort it out in a few months, regardless. Relatively non-technical people who have seen the new WP site detect little difference, as it is. Is there anything else I am missing here?

Author: Milan

In the spring of 2005, I graduated from the University of British Columbia with a degree in International Relations and a general focus in the area of environmental politics. In the fall of 2005, I began reading for an M.Phil in IR at Wadham College, Oxford. Outside school, I am very interested in photography, writing, and the outdoors. I am writing this blog to keep in touch with friends and family around the world, provide a more personal view of graduate student life in Oxford, and pass on some lessons I've learned here.

13 thoughts on “WordPress migration timeline”

  1. Why not keep your existing post and archive pages in place, where Google knows to find them, replacing your index page with one from WordPress. Then, replace the link in the banner for the Blogger blog with one for the WP frontpage.

  2. You also need a snazzier banner – something more in keeping with the “Web 2.0” styling of the WP blog.

  3. It doesn’t do that in IE6.

    I should remember to change the lines that border the page from distracting dashes to cleaner solid lines, though.

  4. Some progress has been made. I think I have fixed all the improperly formatted photos. I have also dealt with the bug that was leaving open strong tags strewn about. The only way I could do that (loading every entry on one huge page) was very bandwidth intensive.

    I have also categorized all 300+ posts included here in the new blog. Posts that didn’t have titles before now do.

    A bit of format tweaking and I will be ready to shift to the release stage.

  5. I’ve changed the colour of hyperlinks within the template, as well as the colour of the search box. I am starting to get a feel for all the CSS. Unlike the Blogger page, which only had one CSS stylesheet, this blog uses more than ten.

    Once I have a new banner up, I think I will swap this over so it occupies the root of sindark.com

  6. Still not done:

    # Add Google Analytics tracking to WP blog
    # Find a photo upload plugin akin to the Upload Photo tool in Blogger

    #Fix internal links within WP blog

    #Fix internal links within Blogger blog

  7. Mozilla, although supportive, is still a ways from ACID2 compliance. Web developers are therefore faced with a difficult decision: do they develop their content to the standards, or to the browsers that will render it? As web developers (or the manager of web developers), what decisions did you made on your projects?

    (Source)

  8. Another bit of housekeeping:

    1) Remove my old ‘links’ page from my Oxford webspace. Shift it to sindark.com
    2) Remove my really old ‘links’ page from Shaw webspace. Delete it
    3) Likewise, remove academic CV and other duplicate content from both other spaces.

Leave a Reply

Your email address will not be published. Required fields are marked *