Zemanta Automatic Recommended Links & Posts Feature Live For All Users
Wanted: One Support Superstar

Typepad Release Notes: New Theme and Beta Feature

Today's release is all about a new theme and bringing back our Beta team. We'll have an email out to all of you beta team members in a bit, but we didn't want to hold back on sharing the news with everyone until then. Before we get more into the Beta feature, let's discuss the theme.

Raising the Bar

The latest theme is Highbar, which features the sidebar content pulled up to the top of the browser window, even with the banner and blog title.

Highbar
Blue + Cherry Gray + Orange Purple +  Pink Green + Teal

With four color variations to choose from, you're sure to find one that fits your blog's style. You can make it even more suited to your blog by customizing it with Custom CSS if you're an Unlimited subscriber or higher.

Beta Feature

Now available for Beta users, who are also Unlimited subscribers or higher, is a Head module! Found at Design > Head, there is now a customizable field that is similar to how the Custom CSS feature works. Any content you add into the Head section will be inserted into your blog's HTML, but, and get this(!), it is placed directly within the <HEAD> and </HEAD> tags.

How the Head is used
Adding content to the Head at Design > Head

Custom Head content in the source code
Custom Head content showing in the HTML source of a blog

The Head section is a feature that's been asked about for a while, and we're ready to deliver! What's more, we're ready for the Beta team to test the feature with everything you've got. Throw your custom meta tags, jQuery scripts, and more at it. Report anything you think is a bug with how the feature works.

To avoid any issues, make sure to use the Head module with a test blog until you're confident that what you're adding works. Now, if you go and break your test blog because you added something that doesn't belong in the Head section (check out the sidebar tips on the Head page to find out what those items are), then your first step should be to review your code and any instructions you're following. If, after that, you're not sure why the code broke, your second step is to open a ticket and direct us to the blog in question, followed by detailed information on what your attempting. We'll be happy to take a look and provide assistance.

If this sounds awesome and you're NOT a Beta user, then go to Account > Summary and opt into the Beta team. We look forward to hearing from you.

comments powered by Disqus