Feature
Post

Category
Code

CSS: Fun With Floating in the Grid

Sometimes for bigger design projects that will need to be pretty flexible, I tend to use several CSS classes to make it easy to maintain from a design and layout perspective in the long run. If you’re a fan of grid-like design, this is most certainly things for you to consider.

Flexible Floating

To make it easier to position elements in a design, from actual content areas (like columns and sidebars), to images and boxes, I employ a set of CSS classes that can be mixed together easily enough.

The core of these classes are:

.left { float:left; }
.right { float:right; }
.frame { border: 1px solid #aaa; padding: 5px; }

This means that any element I’ve given the left class will float to the left. If I add the frame class, it will get a grey 1 pixel border, with some padding between the content and the actual border, to make it look better.

Now, to make sure that images get the necessary spacing to the left or right when being floated, I also add these additional classes:

img.left { margin: 0 15px 15px 0; }
img.right { margin: 0 0 15px 15px; }

This will make sure that images floated to the left will get a 15 pixel spacing to the wrapping text to the right, and below. The same goes for images floated right, but to the left and below of course.

So how would this work?

<img src="myimage.jpg" alt="My image" class="right" />

This image will float right, with a suitable spacing to the wrapping text. Well, let’s add a border to it to make it look better:

<img src="myimage.jpg" alt="My image" class="right frame" />

imagefloatdemo.gifI just add frame to the class attribute to make this happen, not hard at all. In fact, I have in the explanatory image to the right just here.

The really nifty thing, however, is that I can use the classes left and right anywhere, which can be convenient.

If you’re a WordPress theme developer then you might want to add the classes alignright and alignleft to your CSS declarations. These are the default classes used by WordPress’ image uploader/inserter, so it might be a good idea to support them.

Practical Layout Uses

Nothing fancy so far, right? Well, as I said, by doing it this way, I can easily arrange my layout as well. Let’s say I have this 970 pixel wide design, following the grid with three columns of 310 pixels each. You might recognize the concept, it’s the new Devlounge design. What I do is that I define the column, like this:

.column { width: 310px; }

No float or anything. I can also add a wide column, spanning over two columns (310×2=620 pixels), and add the spacing I have between each column in the design, being 20 pixels, bringing it to a total of 640 pixels.

.widecolumn { width: 640px; }

So let’s have a wide (double) column to the left, and a single column to the right. Simple:

<div class="widecolumn left">My wide column's content</div>
<div class="column right">My right column's content</div>

For clarity’s sake, here’s an overview of the Devlounge layout, with the columns marked:

It can be convenient to keep the float attributes free of the actual content containers. As you remember, the classes left and right are global stuff that I can pull out whenever I want.

The whole current Devlounge design is built like this, using columns and separate classes as much as I could. I could optimize it a lot more (and I am, whenever I have time), but this suited this build.

Do you use this technique, and if not, why not? Share your thoughts in the comments!

Feature
Post

Category
Code

Getting Gravatars on your Single Posts in WordPress

Gravatars are global recognizable avatars, being avatars hosted at Gravatar.com, a service run by Automattic, creators of WordPress and WordPress.com, these days. Since version 2.5 of WordPress there’s built in support for Gravatars, using a template tag to display the appropriate avatar, or a placeholder. The default WordPress theme, being Kubrick renamed as default, uses it in comments, which is the common usage of gravatars.

However, with the recent redesign of Devlounge, I decided to use gravatars rather than theme-bound avatars for displaying the author’s pretty face. You can’t just pull the gravatar code from comments.php to do that, you need to work a bit with the template tag.

First, to display a gravatar you need to register an e-mail with the Gravatar.com service. There, you connect an avatar with the e-mail address. The key is the e-mail address, that’s important to remember.

Displaying the Gravatar

The code used here on Devlounge, for the avatar on the top of the single post pages, is the following:

<?php echo get_avatar( get_the_author_id(), 40 ); ?>

So what does it mean? The get_avatar() is the WordPress call the Gravatar functionality. As you can see, I’m using the template tag get_the_author_id() to fetch the singe post’s author ID, which will tell get_avatar() what e-mail to use to look for. I could use other template tags to fetch the correct e-mail, but I went with the ID one.

40 is the width and height of the avatar in pixels. 16, 32, 48 or 64 are more common uses, but 40 pixels fits the design for me.

If you wanted to, you could add a path to the default avatar URL, so that not the default one from Gravatar.com is displayed for people not having registered an avatar. In this case, I’m going with the default one because people are used to it, and when they see that a gravatar can be used, they might be more inclined to get one.

For comparison, in the comments the gravatar code looks like this:

<?php echo get_avatar( $comment, $size = '32' ); ?>

Here $comment calls the comment in question’s author e-mail is used to fetch the appropriate avatar, and that one will be 32×32 pixels in size. As above, I could have added a path to a default avatar.

Feature
Post

Category
Headline

Headline: The New Devlounge

Introducing the New Devlounge

Feature
Post

Category
Publishing

Welcome to the New Devlounge

Welcome to the new version of Devlounge. I have revamped the design to make things easier for the people involved in running this site. The previous version, being a nice piece of work for sure (I doubt Splashpress would’ve bought it otherwise!), had been around for a while, and it’s always good to redefine oneself every now and then.

So here we are, with a new version of Devlounge, for all the right reasons, I hope.

More importantly, it was necessary for us to redesign so that Devlounge would fit better in the Splashpress network (which isn’t fully integrated yet), as well as find its new voice. You have probably noticed that we have experimented a bit with various types of content during the past month or so, and spoken directly to some of you to make sure that we’re reading things right. It’s always hard to butt in as the poor bloke in charge of a recently acquired site, especially when you haven’t bought it yourself.

So here we are, with a new version of Devlounge, for all the right reasons, I hope.

So What’s New?

Besides a visual overhaul, still pretty true to the Devlounge look and feel I’d say, the big news is the way the content is categorized. In the backend, a lot of old things and choices still lingered, which is fairly common for sites in constant evolution actually. The key is to focus it so that you can have actual use of things like categories, tags and so on. It’s only natural that things are piling up, so this week will involve me re-categorizing a lot of content to fit our main categories. These have been described earlier, in the sneak peak post, but here they are again:

  • Code focusing on PHP, CSS, XHTML and similar, tutorials and snippets
  • Design on trends, web 2.0, inspiration, critique and praise
  • Opinion being commentary on the web from the staff, will probably delay this one for focusing reasons
  • Publishing blog platforms, forum systems, open source applications as well as paid ones, things you need to publish a website, basically
  • Strategy for launch and relaunch, monetization and SEO, things to help you succeed
  • Webapps is about online tools, necessities, desktop replacements, cool apps, things like that

The reason is of course to make it easier for the readers to find what they’re looking for. I have chosen to put the menu to the right, in favor of the descriptive type, otherwise I’m a fan of horizontal menus.

So category listings with relevant content will be coming along during the week, as will a dedicated archive page, an author archives at that.

The front page is new as well. It’s not the version I showed in a concept mockup way back, but a more straight forward one, displaying the latest articles straight up, but having space for more visual pushes at the top. I expect to tweak this a bit, to find the way to manage it and use it. It’ll be one of those elements where you have to find your way.

What About the Content, People?!

Yes, I’m getting to that. The whole purpose with a redesign is to elevate the content, and I’ve had the feeling that we needed to do that all along. There’s a lot of cool features planned, including my promised ones on bbPress, and I’ve got some promising writers on the way in as well. The idea is to up the publishing schedule, and offer a solid mix of articles and posts in the topics described above.

The whole purpose with a redesign is to elevate the content

I’m also hoping to be able to look through and update the WordPress themes offered here on Devlounge, with better support. Still working on how to solve that.

And yes, the previous Devlounge design will be released for free! Just don’t expect it right away, there’s probably a lot of hacking and customization to do to get it download-worthy. After all, it was made for Devlounge, and not general use.

We’ll offer more downloadable content as well, as we get back into our groove. Expect cool stuff coming out of the article series planned for this Summer… Tease, tease indeed!

This Week Might Be Rocky

Finally, I’d like to warn you all that this week might be rocky, as I take the time to manage the content as well as clean up a few things. I wanted to get this version out in the open, for feedback (the comments are wide open for you!) and reflection. The idea is to make Devlounge great, and that will take some effort for sure.

Expect a follow-up post on the progress late this week, or (probably) early the next.

Feature
Post

Category
Publishing

Spam Protection Solutions for WordPress and Movable Type

Spam is the bane of blogs, ugly links trying to nest its way into your blog comments section to trick your readers to buy their products, download spyware, or just build links. We don’t want it, none of us do, and luckily there are ways to stop it.

Solutions in the Blog Platform

You can do it manually, which will work perfectly fine to start with. Just moderate every comment, no problem right? Wrong. That will take time, and the more readers and Google juice your blog gets, the more spam will hit you. It is just not humanly possible to manage spam on a larger blog, it will get out of hand really quick.

Enter the anti-spam measures taken by the blogging platforms. In WordPress you can set up a blacklist and stop all comments with more than two links, for instance, which will help out a bit. Similar solutions are available for Movable Type. Problem is, spammers are sometimes very bright, which means that they alter their spam comments to trick you, so you’ll end up with a bunch of spam comments getting by your line of defence.

Enter the Spam Fighting Plugins

The real way to tackle blog spam is using plugins.

AkismetAkismet is something of an industry leader, developed by Automattic and shipped with WordPress. The plugin is free for personal use, but there are problogger licenses. Akismet started as a WordPress plugin, but nowadays it is available for other platforms as well, including Movable Type, various forum software, and more.

DefensioDefensio is a fairly new anti-spam solution similar to Akismet. It is available for both WordPress and Movable Type, as well as other platforms, which is a good thing. The plugin is free for personal use, but commercial adopters will have to pay.

TypePad AntiSpamTypePad AntiSpam is Six Apart’s brand new anti-spam plugin built on the TypePad platform’s spam protection. It’s in beta and totally free at the moment, and available for both Movable Type and WordPress, with more platforms coming soon. The plugin got a very good testimonial from TechCrunch’s Michael Arrington, who puts it in the same level of effectiveness as Akismet, which is a great start. TypePad AntiSpam is a plugin that learns from what you mark as spam, which means that you need to work a bit to get the plugin to be really effective. It will be very interesting to follow this one.

Other options are of course available, mostly for WordPress. Spam Karma 2 used to be a lifesaver for me, until Akismet got really effective, and I’ve had clients being happy with Bad Behaviour. I’d also like to flag for Mollom, an anti-spam plugin for Drupal that is available for WordPress and apparently is looking go the same way as Akismet and TypePad AntiSpam, with wider platform support.

My Weapons of Choice in the Spam War

I used to have a combination of Akismet and Spam Karma 2 on my WordPress blogs, which means most of my sites, and it’s been working really well. However, the last 6 months or so I’ve settled for Akismet, and actually haven’t had the need to utilize any other anti-spam plugin. Defensio is yet to impress me, although I wouldn’t rule it out. I am waiting for more users to report on how it is working for them, should it get a lot of positive press I’ll probably give it a serious go on one of the larger public sites.

Six Apart’s TypePad AntiSpam plugin is the most interesting one, however, and I’ll be using it on an upcoming project to see how it turns out.

How do you battle comment spam on your blog, and how is the war coming along? Share your experiences in the comments.

Feature
Post

Category
Design

The Devlounge Redesign: Sneak Peak #1

It’s been a bit quiet on the Devlounge redesign front for some time now. Juggling a lot of project can do that to a man. However, things are rolling again, so expect a relaunch soon enough. No, I won’t make an estimate yet, those always break anyway, right? Maybe I shouldn’t have said that…

I will, however, give a sneak peak as to what you can expect from Devlounge once the redesign is rolled out. I’m talking about the new categorization of our content.

Brand New Categories

Screenshot from next DevloungeToday’s categories doesn’t really work well with how Devlounge have evolved. I’m sure the plan behind the current layout is both cunning and brilliant, but things change over time, no matter how well you plan them. A good and logical categorization of content for such an editorial site as Devlounge is crucial. I repeat: it’s crucial!

That’s why these will be our new main categories, replacing the old ones.

  • Code focusing on PHP, CSS, XHTML and similar, tutorials and snippets
  • Design on trends, web 2.0, inspiration, critique and praise
  • Opinion being commentary on the web from the staff, will probably delay this one for focusing reasons
  • Publishing blog platforms, forum systems, open source applications as well as paid ones, things you need to publish a website, basically
  • Strategy for launch and relaunch, monetization and SEO, things to help you succeed
  • Webapps is about online tools, necessities, desktop replacements, cool apps, things like that

There might or there might not be room for sub-categories. With tags, I personally think that pinpointing a post’s topic is better left to the tags, the fewer categories you can get away with, the better.

I’d say that the categories Code and Design are the most important ones, the primaries, with Publishing being secondary, and the rest being less frequent on the site. How does that sound to you? Let me know in the comments.

Feature
Post

Category
Publishing

Help Me Pick: Vanilla vs. bbPress

I need a forum for an upcoming project, and I need to decide which one. I should’ve done this a long time ago, or at least a last week, but I’m having a hard time making up my mind.

Vanilla vs. bbPressThis is where you come in, dear reader! I’m asking you, which forum should I choose: Vanilla or bbPress?

I came to the conclusion that it would be one of these two forums after contemplating these criterias:

  1. It has to be opensource and free. Lots of good commercial solutions are out, like vBulletin. Not a money issue, more like a principle…
  2. I want a PHP forum running MySQL (or similar). This is because this is something I know something about, and most hosts provide decent service.
  3. I want the forum to be pretty lightweight. Basically, I’d rather add plugins for special features, than have everything crammed in there at once.
  4. The forum needs to be pretty easily customized. So phpBB is out, and so is PunBB. Not that these are necessarily bad forums but phpBB is pretty clunky, and PunBB won’t commit to CSS full-time until the next version.

After much consideration, I went with Vanilla or bbPress. Both are opensource, lightweight, and cool new players. Also, I like the tag support.

So which one?

Pros & Cons: Vanilla

Let’s start with the good:

  • Seems to have decent support and a fair amount of extensions.
  • Easily integrated with X, including WordPress, which I’ll be doing for a client soon enough.
  • Nice “new” forum layout to build from, always a good thing.
  • Good reputation online.

Then the bad:

  • Nobody I know have styled nor run it, so I only have second-hand opinions.
  • Documentation could perhaps be better?
  • The nice “new” forum layout could mean that I have to reshape everything whenever I want a more customary approach.
  • Not sure about the theming…

Pros & Cons: bbPress

Starting with the good things again:

  • Automattic, makers of WordPress, is backing bbPress, which feels safe.
  • I have run several bbPress forums for editorial groups and such. Small, but they’re working OK.
  • Very fast and lightweight!
  • Akismet spam protection, thank you very much!
  • Theming to be close to WordPress, which is familiar to me.

And the bad things:

  • It’s not in 1.0 yet. Who knows what will happen? Is it really ready for a public site? (Probably.)
  • Maybe too lightweight? Everything besides writing forum posts is a plugin, not even support for private forums. That’s not good.
  • I’ve had issues with upgrades when using the Swedish language. This is a problem that should be fixed, but it could theoretically be an issue until 1.0.
  • The admin interface is poor at best.

Help Me Pick: Vanilla or bbPress?

I’d like to hear what you guys think, since I’ll be spending some time playing with whichever it’ll be, and that means possible tutorials and more for Devlounge. Might even release a theme or two, we’ll see…

Which one and why? And remember, it’s either Vanilla or bbPress, nothing else I’m afraid.

Feature
Post

Category
Publishing

10 Common Mistakes In Redesign

I’ve never been shy of throwing stones in glass houses, hoping that they should bounce away and not make it all come down on me. It’s more fun that way. With the Devlounge redesign around the corner (the theme’s core is more or less done – yes, there’ll be more previews before launch), and after that a similar treatment for The Blog Herald, talking common mistakes in redesign seems like a good idea.

Now, this is by no means a complete list or anything, every site and design has its own needs and do’s and dont’s. See as something to think about before redesigning.

  1. Launching before the new design is cross-browser tested. Seriously, sometimes you’ll stumble onto a redesign by a what you thought was a serious website, and it breaks in Safari, isn’t tested in IE7, or whatever.
  2. Launching without giving your readers a heads up. You should definitely inform your readership that a new design is coming, or have a really good explanation ready when you’ve launched. Chock-launching can work, but in today’s very open and transparent web I think you really should let people know that they might see another design next time they pop by.
  3. Removing all key recognition elements in one swipe. Don’t just null out your previous visual identity, make sure there are some elements left, updated perhaps but recognizable, so that your readers can tell that they’re visiting the correct site.
  4. Making everything harder to find. Let’s face it, you might want to move around elements in your design and that’s fine. Just don’t change everything at once, or if you do, make sure that everything is in the second most obvious place (the first being your old design’s locations of course).
  5. Jumping onto the popular style bandwagon. It’s easy to get caught up in the flavor of the day, being rounded corners or pastels. By all means, take the parts you like into your designs, but remember what you’re redesigning, maybe the style doesn’t fit at all, or maybe it just doesn’t benefit the site. If you really want to do the design of the day, then by all means do, but consider carefully where you use it.
  6. Launching too early. I know, I know, it’s very easy to launch early and say “I’ll fix the rest later”. Well, if you’re gonna do a beta launch, be sure you don’t pull a Google and stay in beta forever. Make sure you’ve got a list of features and additions ready, and plan them, so that your premature launch won’t come back and haunt you. Ideally, your design is done when you’ll launch, or at least appear done, then you can add to it and make it look like tasty bonuses!
  7. Redesigning too often. A new design, again? You should commit to your designs, give them time to exist. Maybe they turn out to be “bad” for your site, then fine, go ahead and fine-tune, but watch out for getting caught in the redesign loop.
  8. Removing features without an explanation. Some features and functions should never disappear of course, like the search box on most sites, but some might not seem necessary anymore. Well, that might be true for you, but you should make sure that it goes for your readership as well. I like to ask the readers, or at least post about why something was removed, with alternate (better) functionality for them to use instead. That way, they’ll complain if I’ve been stupid and ignorant in my feature-slashing, and the site benefits.
  9. Too drastic monetizing changes. This is a tricky one. On the one hand, you need to make money on your site, but on the other you don’t want to make the ads too obtrusive. Every change in advertising on your site, be it contextual text links, image ads, or whatever, should be made with caution. This is one point where the chock treatment will not work.
  10. Pushing too much new stuff. This goes for design in general of course, but adding too many things to a page makes it cluttered and that’s ugly. Since a lot of redesigns are pushed because of the urge to add new functionality, nifty new stuff you have to push out there, this is a common mistake. Don’t clutter it, prioritize, and be wary of what you remove to make room for the new things.

Want to add to the list? Post in the comments.

Feature
Post

Category
Design

A Great Example Of Integrated Tweets

You know Twitter, that lovely microblogging service that Gapingvoid just left because he didn’t do much more than, well twittered? The same service that Robert Scoble heralds, and Jason Calacanis is aiming to dominate? Yes, that Twitter, the same Twitter that I’m on, and sharing space with the British government.

Since Twitter is addictive, lots of bloggers have decided to start importing Twitter content into their blogs. It’s nothing new, with several plugins available, the most popular one might be Alex King’s Twitter Tools, but I don’t know for sure. Either way, it’s a sure way to make your blog totally uninteresting, ugly, and boring. Think about it, who wants to read your tweets in a bullet list, hours after they happened? Chances are, most people don’t want to read them at all, especially when you’re offering a discussion with some friends, interesting only to those involved, but nevertheless cluttering your blog in a most hideous manner. Don’t take that last link to seriously by the way, Jeremy came to his senses

Still, your tweets are content, and maybe you want to attract the people who actually do care about what you have to say on Twitter to your account. Then integrate it smoothly, like Twisted Intellect, the most beautiful example of displaying tweets on a site to date:

Pretty Twitter integration

Pretty huh? I’m sure there are several others who’s doing this right as well, but I was actually quite blown away by this today. I’m a fan of serifs though, especially classy work with italics, so the site pretty much appeals to me.

The Rules of Twitter on Your Blog

Follow these rules when integrating Twitter on your blog or site, and you’ll be fine.

  • Don’t treat tweets as regular content! Put them someplace to the side, by themselves. Posts are content, tweets are, well, tweets.
  • Don’t give your tweets too much space! Think about it, does they really add that much to your blog to begin with? Shouldn’t you push your real content with that space instead?
  • Don’t show too many tweets! Really, how interesting are they after a while? Better to show just a handful, than to push out a RSS feed from your Twitter account containing 10 tweets, where 7 are from days past.
  • Don’t integrate Twitter unless you use it! What’s the point of displaying your tweets if they are not up to date? I’ll tell you right now, there is none.

Ready to follow that? OK, then please, please, please ask yourself yet again if your tweets actually add value to your blog. Maybe a link to your account is good enough? Chances are, for most of us, it is.

Have you seen other great integrations of Twitter content on sites and blogs? What’s your take on all this? Tell us in the comments, I know I’m dying to know.

Feature
Post

Category
Design

The Next Devlounge Design: Mockup #3

I’ve been a bit busy the last week, which is why this mockup have been somewhat delayed. Among other things, I’ve moved to a new house, with lots and lots of weird things happening. Ghosts? Who knows…

Seriously, it’s time to crank up the pace a bit. I’ve tried the previous mockup design on numerous contacts, friends, and designers this past week, and there’s a consensus that it is good. So I’m moving onwards with it. That doesn’t mean that it is a final design, it’s still just a mockup, but this is the basic style we’ll be going with.

First Single Post Mockup

So with the front page somewhat specified, here’s the first front page mockup design. It is lacking comments at the moment, and I’m not happy with the box below the post either, it needs some flare and overall TLC. I haven’t touched the sidebar at all, see below.

Anyway, here’s the mockup.

Single Post Mockup #1

Thoughts On The Sidebar

Today’s Devlounge is using the sidebar on single posts to promote the blogger with a short author bio, a picture, and for pushing for RSS signups. While I like the author bio box and all, I’m not a great fan of this, since it can confuse the users. If you’re used to find certain things in the sidebar, and it isn’t there on all pages, then the user might be disoriented. Not a big deal, perhaps, but still.

In short, I prefer to not alter too much in the sidebar. What are your thoughts on this? Looking forward to hearing them, and of course your thoughts on the mockup as well. As always, they’re much appreciated, so share!

Feature
Post

Category
Publishing

What bbPress Needs To Really Work

I’m a dedicated WordPress user, and I know the system if not inside out so good enough to do more or less anything I want with it. That means I’m pretty psyched about the bbPress forum software, AJ’s written about it previously, the popular guide post. That was a while ago, October 2006 actually, but I’d say it still works out if you want to give bbPress a go. It might be a bit easier and polished today, but not much.

bbPress is still a bit from 1.0. Quite a bit, honestly. While I do think a forum system should be pretty slimmed down, not including everything I don’t need (but offering it as great kickass plugins), there are some things that bbPress lacks that just have to be in there.

  • Subscribe to updates. There is a RSS option, but I want an e-mail digest as well, telling me when someone posted in the thread I’m interested in.
  • Individual forum access. Sometimes you want locked forums, so why not let me set access on a per user basis? Or, failing that, for groups of users at least? And please let me have users in several groups, thank you very much. (Need private forums today? There’s a plugin, at least, although it is a bit lacking.)
  • User bling-bling. At least some bling… You know, avatars, signatures, those kind of things. Actually, those two would get bbPress a long way. Not being able to set up a signature even, that’s pretty weak if you ask me.

bbPress is still a bit from 1.0. Quite a bit, honestly.

One could also argue that bbPress needs more themes and plugins, since although there is quite a bunch of the latter, they aren’t really as refined as you’d think they would be, it being a sister project to WordPress and all. Also, the presentation is miles behind, especially now when WordPress is in 2.5 and sports a brand new look.

bbPress is in version 0.8.3.1 at the moment. While they say it’s not quite ready yet – obviously – I’d say it is pretty stable. I’m using it for some closed groups at least, but that’s about it.

Well, there are plans now, so I need to decide if bbPress is ready. In my opinion, it works, but it doesn’t work as well as it should.

What do you think? Is bbPress ready for a live site?

Feature
Post

Category
Webapps

Your Online Life As Content

Today we’ve got a bunch of great services online, some blog related, others just tools that help us in our everyday life. If we really wanted to, we could have more or less everything accessible, or at least replaced, by online tools and services. Think about it: e-mail and calendars have already moved online permanently for a lot of people, and nowadays the office apps are getting decent, you’ve got collaboration software, and even an online version of Photoshop! Add your bookmarks, web radio and music, online movies and TV, there’s a lot.

Why not share it? And give your site more life and flair at the same time?

Share Your Life

That way, colleagues and friend can keep up with your schedule, and you can link it easily.

If you’re using Google Calendar, and have public content in it, you can add it to your site using simple embed code. That way, colleagues and friend can keep up with your schedule, and you can link it easily. Other online calendars, including applications you install yourself, will probably let you do this as well, but my 100% non-scientific research shows that the Google app is the most used one.

Likewise, you can help people find you in the physical world, using Google Maps for instance. That way, driving directions are always available online, with zooming functionality and everything. Embed a map including important places on your blog, maybe with restaurant tips and directions to good bars? Or just get a map showing where your offices are located, either way will do. You can even do stuff with the street view these days!

Add Your Online Existence

I personally advise against displaying microblogging content as regular content

Do you Twitter or Jaiku, or perhaps Pownce? Why not share that content on your site? Bloggers can use one of the numerous plugins available, including the popular Twitter Tools for WordPress, although I personally advise against displaying microblogging content as regular content. It’s better to put one of the available badges (for Twitter and Jaiku) in the sidebar, showing your current status, or why not just pull the latest updates via RSS? Better yet, mash them up with Yahoo Pipes and serve your microblogging content live, using RSS.

Bookmarks are great, and you should share your finds. The most popular way to store bookmarks online today is del.icio.us, and you can of course get your latest additions for your site, or pull it with a plugin or via RSS. The latter goes for all good online bookmarking services.

Speaking of RSS, why not share your list with everyone? Either just link to the OPML file, which can be imported into any good RSS reader, or to a public showing. Google Reader users can display a clip of their shared items on their blogs, or just link the public page. If you’re a Bloglines user, you can create your own blogroll badge, or you can link to a public page there as well. I’m sure other online RSS readers have similar solutions.

My Leisure Time

Why not share what your do on your free time, for leisure? Using last.fm, you can tell everyone what you’re listening to, and even display it with a nifty little widget. Or why not start your own last.fm music channel, playing good music only? If you, like me, are in the Spotify beta, you can link your playlist, which is more or less the same as last.fm but cooler, and only for us privileged ones…!

We all love YouTube, so why not slip in a link to your YouTube favorites, or even a playlist? There are several ways to get YouTube on your site. Sure, you can always post the videos you like on your site, but that’s not always appropriate, and besides, if you’re an avid YouTube watcher then it would men a ridiculous amount of YouTube videos, right? Link your channel!

What about Hulu, South Park Studios, Comedy Central and such? Well, they just don’t offer anything besides embedding videos, and sometimes not even that. But you can always link your favorite shows, right?

What About Privacy?

Be sure to consider the privacy aspect of sharing your online life carefully

Obviously, there are numerous ways to let people into your online life. The question is, do you want to do that with everything? Maybe your bookmarks are private, or perhaps you don’t want to share your schedule with everyone? Also, do you want to let people know where to find you in the physical world?

Ask yourself these questions. You certainly shouldn’t share anything online that matters a lot to you, because it could get exploited and leave you in a fix in the future. Be sure to consider the privacy aspect of sharing your online life carefully, before starting to embed and share content from these great web services (and others) on your site.

That being said, it is certainly nice to get automatic content for your blog, for instance, just by using a service you would be utilizing anyway!