Skip to main content

Completing The Migration - Converting To A Layouts Template

New Blogger - what I will call here "New Blogger 2006" - has been with us now for one year, give or take a few months. This time last year, I had just previously written about the impending migration to Blogger Beta (aka "New Blogger 2006"). Now, we are completing the migration.

I say "completing the migration" because there are, currently, folks seeking guidance on how to complete the migration of their blogs.

All blogs are now under New Blogger - that's not the issue - Old Blogger was laid to rest some months ago. Not all blogs are using Layouts templates, however. Some blogs, which are published using FTP to external servers, will always be using Classic templates. Yet there are some blogs which can be migrated to Layouts, that haven't.

Anybody who has been posting, or helping, in any of the Blogger Help Group forums has seen this query.
I just finished entering a post into my blog. I previewed it - and it looked fine. Then I published it. And now, my blog looks like crap. What happened to my blog?


Well, what happened is that you didn't test your post enough. The Post Preview wizard simply doesn't provide a valid test, for every blog.

And my guess is that the template migration process doesn't provide a valid test, for every template, either. There will be template features, on any blog with any complexity, that will have to be tested in a live browser. Preferably, two, or more, live browsers.

Expecting that, after migration, there will likely be template features, in any Classic blog of any complexity or size, that won't be migrated automatically, I'll ask a rhetorical question.
When would you prefer to be testing your new Layouts template?
  1. Now, while your blog is online and operating (as a Classic)?
  2. Or later, after migration, while your blog is down (with missing features to be patched in) (And with complaints from your readers)?


I'll bet you'll answer
#1

in a heartbeat.

Why stress yourself? Having added various features to both Classic and Layouts templates, I'd bet that any Classic template, that originally took more than an hour or two to setup, probably wouldn't migrate as is, with all features intact. I'd waste an evening, to reduce stress and make a more successful migration happen. Start this process before you execute the migration.
  1. Be aware of Layouts template migration issues. Learn from other folks mistakes.
  2. Be aware of Layouts templates design deficiencies and limitations. Learn from others disappointments.
  3. Setup a test blog.
  4. Copy the current template, and the posts with comments, from your current Classic blog.
  5. Migrate the test blog, to a Layouts template.
  6. Customise the test blog, adding template features, as necessary.
  7. Test the test blog, with the Layouts template, in multiple browsers.
  8. When you have the test blog all working, so it looks like you want your blog to look, then migrate the production Classic blog to a Layouts template.
  9. Finally, copy the fully tested Layouts template, from the test blog, to your newly migrated production Layouts blog.


The bottom line? Some planning, and extra (and redundant) effort, will make for a less stressful migration. Less stress will make for less mistakes. Less mistakes will make for a better experience by your readers. And your readers are The Bottom Line, aren't they?

If you consider this to be excessive thinking, consider my hypothetical experiences in Which Migration Experience Would You Prefer?

>> Top

Comments

Popular posts from this blog

Custom Domain Migration - Managing The Traffic

Your blog depends upon traffic for its success.

Anything that affects the traffic to your blog, such as any change in the URL, affects the success of your blog. Publishing the blog to a custom domain, like renaming the blog, will affect traffic to your blog. The effects of the change will vary from blog to blog, because of the different traffic to every different blog.Followers. People who find your blog because of recommendations by other people.Search engines. Robotic processes which methodically surf your blog, and provide dynamic indexing to people who search for information.Subscribers. People who read your content from their newsfeed reader, such as the dashboard Reading List.Viewers. People who read your content from their browser.No two blogs are the same - and no two blogs will have the same combinations of traffic sources.

Stats Components Are Significant, In Their Own Context

One popular Stats related accessory, which displays pageview information to the public, is the "Popular Posts" gadget.

Popular Posts identifies from 1 to 10 of the most popular posts in the blog, by comparing Stats pageview counts. Optional parts of the display of each post are a snippet of text, and an ever popular thumbnail photo.

Like many Stats features, blog owners have found imaginative uses for "Popular Posts" - and overlook the limitations of the gadget. Both the dynamic nature of Stats, and the timing of the various pageview count recalculations, create confusion, when Popular Posts is examined.