Use RapidWeaver's %pathto()% syntax in javascript files

It may take me a while sometimes, but there is one simple truth about my workflow, I always strive to have the most efficient way of getting things done. This is especially true in RapidWeaver theme development. Developing themes for RapidWeaver is not like standard web design. You have no way of knowing how each user will structure their site, what plugins they'll use, what they'll add to their pages... All of these uncertanties leave us as developers scratching our heads sometimes, trying to sort out ways of dynamically including things and stuff without the end user being able to break it.

PHP would be the obvious choice here, but we don't have the luxury of knowing what the end users hosting environment will be and whether they could, or even would be willing to support a host of PHP functions. So the next best thing is javascript; yes it's a little slower and it does depending on the end user having javascript enabled, but the ubiquity of javascript has never been as great as it is today.

One thing that has plagued RapidWeaver developers for some time is how to utilize RapidWeaver's %pathto()% syntax, the bit of code that allows RapidWeaver to imprint the end users chosen common file path, in any other file other than the index.html template file. For any javascript file that has required the inclusion of another file, we've previously had to fill our html with scripted variables for each file, each using the %pathto()% syntax and so forth until we have built a separate path to each file from outside our javascript that actually requires it. Since RapidWeaver will only write the path to files it can actually find, you need to do this for each and every file.

Today I had an AH-HA moment while in need of multiple paths to be defined for use in various javascript files. I decide to write a small bit of code that grabs RapidWeaver's %pathto()% syntax while it chases a real file. Then I strip out the actual file name, and KABLOW! you have a common file path in the the form of a javascript variable, ready to be used in any javascript file you like.

Download the bit'o code here.

Realmac Software release LittleSnapper/QuickSnapper one-two punch!

Realmac Software has just made LittleSnapper official, bringing this very powerful screen and web snapping app out of beta and into the general public. I've been fortunate to be playing with this app for a week or so, putting it and it's integrated web service, QuickSnapper through their paces. This isn't just you normal screen snapping app. It's a lot more than Skitch (which has never left it's apparent state of perpetual beta) and has many advantages over it (with one or two slight disadvantages). And the web service, not unlike ScrnShots is a robust and attractive place to be and get inspiration.

LittleSnapper allows you to treat a collection of screen and web snaps more like a library, and iPhoto Library if you will, allowing you to tag them, rate them, make notes and annotations, view the source code for web snaps. This gives you not just a library of images, but a tool box of thumbnails complete with source code for studying, origins, ways to note what you liked about it, etc... There really isn't many things to compare it to. It is one of those trend setting apps that has more or less made it's own niche. Certainly a web designers must-have app.

And then there is QuickSnapper... While at first glance, it's not all together different from what other similar scree/web shot sites are doing and on it's own it wouldn't be particularly exciting (except that it looks damn sexy). What set's it apart though is that it was built to support the LittleSnapper app, and not built the other way around. That's where these other screen/web snap sharing site have gone wrong in my books. They've built the site and now in order for you to get your stuff up there, they've made a half baked "utility" that will, if you are lucky, let you upload something... sometimes.

QuickSnapper, on the other hand was built with LittleSnapper integration in mind... exclusively. With the click of a button, LittleSnapper loads up a snap to your account. In turn, with the click of a button on QuickSnapper, you can pull down a shared snap into your own LittleSnapper library... click... that's it! A complete, happy snapping, bio circle of screen and web snapping goodness. Does it get any better than this? Me thinks not!

Oh, and BTW, the screen grab of LittleSnapper? Yeah that was taken with LittleSnapper and is hosted on QuickSnapper...

From pixels to paper, we're getting noticed

There is no greater flattery than to be made an example of so when we were asked some time ago if we would consent to being published in DesignMeltdown's, The Web Designer's Idea Book, I was truly honored.

Today, I received my copy in the mail and was thrilled to find these kind words on page 102 along side a screen shot on page 103:

"A great example of a unified design is the seyDesign site. It has an office theme, and everything flows together perfectly. The corkboard background creates a terrific foundation to tie the site together. It essentially gives the office supplies a place to exist."

Of course this isn't how the site looks today, but for this 2007 iteration of seyDesign.com to be forever immortalized in print is a true sense of accomplishment. All in all, RapidWeaver developers as a whole had a good showing in this book with various sites. Adam from Elixir Graphics has already written about his contributions. and I've heard there are more, I just haven't had time to look through each page yet.

To get yourself a copy of this most excellent web design resource, go to Amazon.com.

To be Strict or not to be

I am about to geek out so bad it will make your eyes roll back and have you snoring before you finish the first paragraph. But to be honest, it's not for you that I write this stuff, it's for posterity and so that I can always look it up in the future, if such a thing should ever happen to me again.

I have finally nailed down an obscure little bug in cataLog (and in turn Acumen) that was causing the second level navigation to jump up about 14 or so pixels when the user used the "Tidy" setting in RapidWeaver and when the user used code or content that tripped the "Tidy" setting into converting the document into a Transitional DOCTYPE. The reason the bug remained so illusive is that this set of circumstances was not immediately clear and is not necessarily something the end user is mindful of.

My repeated testing, assuming that there had to be a difference in the content area or navigation area, kept leading me down the wrong path. One assumes, when "Tidy" is at work, that the HTML of the document is somehow being altered or "tidied up" as it were. And this is where I continued to search extensively but came up empty handed every time. Having exhausted nearly all HTML avenues and having run countless DIFF comparisons I finally turned my attention on the one thing in each document that I knew was different; the DOCTYPE. By simply switching the DOCTYPE from Strict to Transitional, regardless of whether the embodied code was in fact one or the other, I could trigger this odd navigational occurrence.

As much as this was a major breakthrough in the tracking of this bug, I now knew that the game had gotten that much more complex. I was no longer dealing with a bug in my code or the theme as a whole. I was now dealing with what was potentially a rendering bug, or interpretational difference in the two DOCTYPE's, meaning that the bug being presented may very well be an issue in the HTML standard itself. Eeek!

Since I knew that the navigation in question uses inline-block as a value on its display property, and since I am well aware of the lack of widespread support that inline-block has among browsers, I knew that this was probably the place to look. I need to look in the CSS of the second level navigation.

Through considerable trial and error I found that an attempt to display the ancestor, or hidden navigation inline was what was causing the trouble. In DOCTYPE Strict, the combination of ul {display: inline;} and ul ul {dispay:inline-block;} caused the initial ul to have height, despite having tried to suppress it with ul {height:0; margin:0; padding:0;} etc... While in DOCTYPE Transitional, the initial ul rendered correctly (which is to say it didn't render at all and had no height), so the latter ul would shift up to takes it's position. The fix was simply this: ul {margin:0; padding:0;} with no attempt at any display value other that what it would naturally inherit (which would be "block").

So is this in actual fact a bug in the Strict DOCTYPE standard? It's hard to say really. In the making of RapidWeaver themes, we pour a lot of effort and trickery into making things happen the way we want them too. In the case of split navigation we use the same set of code in multiple locations and simply turn on or off the bits we want shown or hidden. This probably is not a typical practice in web design but a necessity in RapidWeaver theme development. Still, why would one DOCTYPE behave differently from another where such a small property in concerned?

seyDoggy is back in the office.

We are back from or little vacay, and back on the horse, if you will, working through a pile of emails and such. On our agenda this week is to address a few bug issues in some of our RapidWeaver themes, namely a footer issue in wideNas, and a couple of mystery bugs that occasionally rear their head in cataLog and Acumen. We should have all of these addressed this week with their respective update installers ready for download.

And as always we are ever moving forward and onward with the theme developments and ideas. We have quite a list of them to get through over the next year or so so you can be sure to see one or two new themes from us every month. Yes that is an ambitious plan, but this is what we do after all, we might very well be the only full time RapidWeaver theme developers now who do nothing else.

And speaking of RapidWeaver, did you notice that RapidWeaver 4.2 has been released? Yes indeed. I have not yet tried it myself, but I have downloaded it and will be getting into it shortly. Learn more about it's release here.

We're off to London!

I'm off to the UK for a bit of a holiday. We take flight at 9:40 pm October 23 (that's today) and will be gone for about 10 days. We'll be back to answer your support questions on the week of November 1st. Remember that if you have any major concerns between now and then you can always try posting them the the Realmac Software forum and I am sure one of the kind and knowledgeable folks there will help straighten you out enough until I get back.

We'll try to keep you posted on our daily outings. That's likely to occur on Twitter so if your inclined to keep tabs on the leisure time of a theme developer geek like myself then you can come follow me.

Anyhow, stay safe and we'll catch in a few days time.

RapidWeaver's %pathto%, TextMate can help

It's no secret that many RapidWeaver developers are quite close and help each other out quite a bit. It's also no secret that in order to develop RapidWeaver themes you need to use some pretty powerful tools. Some of use TextMate, the most powerful one in my opinion. There are so many ways to extend TextMate's features to streamline our workflow, one of the simplest is to edit existing bundles by tweaking their commands or snippets or making a command or snippet of your own.

So back to the RapidWeaver developers... recently, Giuseppe at Bonsai Studio shared a TextMate snippet with the other developers. A snippet that would write a very specific RapidWeaver string that we tend to use quite a bit:

<script rel="stylesheet" type="text/css | text/javascript" src="%pathto(script/filename.file)"%></script>

I jumped all over this because as you may know I am a huge TextMate nut. However, the snippet didn't quite run the way I wanted. So I set about to make it the way that was most useful to me. The main difference being that mine would highlight the file path when activated making it an even faster shortcut for me.

But I didn't stop there. I wanted one that would handle <link> as well. So the result is to snippets that quickly write a <script> string and <link> string that include the %pathto% syntax.

So if you are a heavy TextMate user and happen to develop RapidWeaver themes then you might be interested in these two snippets.

seyDoggy teams up with DEVi8.design

It's always a sign of progress when a company forges new relationships and we are not the exception to that rule. A couple of months ago, seyDoggy and DEVi8.design started talks to bring a vision of DEVi8.design to life. A little over a month ago a deal was inked to turn a concept design of DEVi8.design's Chris Cifonie into a full featured RapidWeaver theme.

Today, the fruits of that collaboration were launched in the form of a seyDesign RapidWeaver theme called DEViANT Pro. Thanks to Chris' vision and our technical know-how we have managed to make a RapidWeaver theme unlike many out there. It's clean, simple and open feeling yet under the hood lies a powerful beast capable of changing to your every whim.

The biggest struggle in making the original vision a reality was making the layout "soft" or flexible, while still maintaining a graphically driven feel. This was done with the use of several transparency tricks and background colors combined to give maximum control with graphic polish. The end result is a theme with width variations, full color control and a handful of other great features that should please the most particular RapidWeaver users. Not content to stop there, we found a great opportunity to take this theme one step further and add 3 tier split navigation to this already awesome theme.

All in all we couldn't have been happier with the outcome of this theme and I must say it was a pleasure to work with Chris Cifonie on this project. His designs are a treat bring to life.

Old Friends on New Horizons

In late 2005 Chris Pavlicek (of Varsis Studio) and I started talking about collaborating on RapidWeaver themes. We both had something to offer the other; Chris with his unmistakable design style and willingness crack any code and me with my promotional skills and desire to make clean organized and effective code. By mid 2006 we were putting out some pretty revolutionary stuff.

After 3 years and many themes later, Chris and I are talking again. This time it's about me taking over his theme library, the one he has (or used to have) at Varsis Studio. Chris is really focusing hard on his RapidWeaver plugins which as any software developer will tell is very demanding on his time. Before the new seyDesign.com was done we were talking about this and working out the small details.

Today we're starting to see the results of all that talking. I was able to release Varsis Studio Fade on seyDesign.com. Fade is a RapidWeaver theme that Chris did up for a pro developer bundle back in January of 2007. I've spent a few weeks on it, gutting from the inside out and filling it full of new features.

The rest will follow over time, interspersed with a few seyDesign originals, and who knows, maybe even another Varsis/seyDoggy collaboration.

Join the March, kill IE6

Designers have talked about it for years, while some big names in the industry have already taken action, even the little guys are taking a stand... the message has never been more clear; it's time to stop supporting IE6.

So that's when I come across IE Death March, a site calling for action against the support of Internet Explorer 6, a 7 year old browser. In this post, site creator, M. Dave Auayan urges web designers and developers to cease support for IE6 by March 2009.

In that time, we will be taking a long hard look at browser stats to see if the numbers support this action. The last thing we want to do is alienate a large section of people, but we also don't want to be continually held back in our design visions simply because a nearly decade old browser can't keep up. I know one thing for sure, IE6 support will become a billed-for feature.

My top 5 web development tools

As a small web design outfit in Kitchener I have to be particular about my development workflow and the tools I use. I can't afford to continually invest in new wonder apps that do a bit of this and a bit of that, and do this thing well but not that thing, but this other app does that thing but not... well, you get the point. So I have to really focus on what makes me money and will continue to make me money going forward. So I have compiled a list of apps that make web design and development on the Mac possible for me.

1. TextMate

   There is text editors and then there is TextMate. Renowned for it's unparalleled abilities to handle a seemingly limitless set of languages, TextMate makes writing ANY code fast and painless. I use TextMate for every bit of text editing that I do, XHTML, CSS, XML, PHP, SQL and javascript, just to name a few. It's not free but you will agree that there is no other text editor that comes close to TextMate.

2. MAMP

   If you are already a pro web designer you are already aware of the need for a live server environment to test out whatever systems you happen to be developing at the time. You also no that uploading to a remote location is time consuming and working SFTP, SSH or WEBDAV can be unstable. You best bet is to have a local server, but if that is not within your means (or know-how) then you need to look at MAMP. MAMP is a nicely bundled package of MySQL, Apache and PHP that allows you to run a web server safely on your own computer. Though Apache and PHP are already included on you Mac, they tend not be as current as those found in MAMP. MAMP also allows you to quickly change your servers from one project to another to keep your perceived root URL common across all your local web work. The best part is, the only version of MAMP you really need to get this done is free.

3. Safari

   Don't hate for this. I don't mind FireFox and I think FireBug is great but to be honest I never use either one on a regular basis. Safari, on the other hand, in an indispensable tool for me. By enabling the developer features of Safari I am able to peer into the DOM for those tricky to view javascript behaviors and see what is really happening on the client side. Safari, of course, is include with your Mac operating system.

4. PhotoShop

   What is web design without the design? There are a ton of free options out there, but lets be honest, there is no substitute for the real thing when it comes to mocking up proposed web layouts. I agree PhotoShop is outrageously priced but in the grand scheme of things, if you are getting paid for your work then the cost of this app is nothing more than a tax write-off at the end of the year.

5. Parallels

   You can dispute me on this choice because I honestly have no experience with anything else. The work involved in getting 3 valid VM's working for the purpose of testing 3 related and equally crappy browsers, IE6, IE7 and IE8, leaves me with no interesting in going through anything remotely similar in the near future. But my point is this, you need to have a way of testing Microsoft's Internet Explorer, version 6, 7 and 8 and whether you do this via Parallels or VMware is of little consequence to me. It needs to get done all the same. The cost of each is comparable to the other.

If the above list is all you ever invest in for your web design and development career then you are in excellent shape.

The beauty of RapidWeaver meets the power of TextMate

As a web designer and fairly huge Mac geek I am one of those guys who gets rather passionate about certain apps and workflows, etc... Those of you who have read one or more entries on nutMac.com, a Mac workflow blog I write for on occasion, you'll know that I am a big fan of Path Finder, Quicksilver and TextMate, three apps that rule my world. Recently, suspecting I wasn't tapping into TextMates full potential, I purchased TextMate - Power Editing for the Mac by James Edward Gray II. Well I was correct in my suspicions, since by chapter 3 I had already learned so many more tricks that I couldn't wait to get back into coding just to put what I had learned to the test.

One trick I had always been vaguely aware of, and apparently by name only, was the "Edit in TextMate" feature. I had looked at activating this at one time but had decided it was terribly complex for something I could just set of a Quicksilver trigger for (which I did, or so I thought). Having just skimmed over what this "Edit in TextMate" feature was, I figured this was just some short hand trick for forcing various files types and folders to open in TextMate as opposed to their default application. In fact, this is a power user feature that allows TextMate to hijack the editing fields of other apps (the search field in Google home page, or in this case, the blog post field of Blogger, my Fluid SSB app).

Here is where the little light bulb went off in my head... Could this be used in RapidWeaver? Now let me start by saying I LOVE RapidWeaver, I really do, but when it comes to HTML code editing, which I do on a continual basis, I can't stand not having my TextMate features and functions handy. I have always found myself writing code in a dummy TextMate file, then copying and pasting it into RapidWeaver. And when I would have to make a change I would copy the code into the dummy TextMate file and so on until I was satisfied with the results.

So to make a long story short, after years of using TextMate, I finally enabled the "Edit in TextMate" feature and tried to invoke it in a RapidWeaver project and POOF! It works like a charm! Now I can place my caret in any RapidWeaver field (main content, sidebar, titles, custom fields, etc...) in RapidWeaver and type ctrl-cmd-E and edit the contents of that field with the power of TextMate.

Can't do nuttin' for ya man!

This is about as dorky as I'll ever get... erm... well anyway, back in the day when I was about 15 or so (19 years ago *sigh*) and heavy into the budding gangsta rap scene, I went to a club in Waterloo, Ontario called The Twist (now Revolution night club) to see this guy, Chuck D and Public Enemy. Though it's all a part of my past now I still like to break out the odd P.E. track and get down wit' mu bad self (as bad as a 34 year old white guy from Kitchener, Ontario is going to get I guess).

To this day me and an OLD buddy of mine will, without reason, randomly email each other once or twice a year with snippets or full course lyrics to P.E. tracks we listened to in the days gone by. Today a Flavor Flav track came up in my iTunes, Can't do nuttin' for ya man, and I set out to get the lyrics and send them off to my buddy. That's when I discovered on the front page of the Public Enemy website, Chuck D using a mac!

Erm... yeah... there is really no connection I am trying to make here... just that he was my hero growing up... I use a Mac... he uses a Mac... OK, shut up already, I KNOW I'm a dork. You don't HAVE to rub it in! :)

cataLog, RapidWeaver and good timing

Wow! I am blown away by the response to our latest theme cataLog Pro. In what I think is both a case of timing and luck, cataLog Pro for RapidWeaver 4.0 has surpassed any other theme in our library for initial launch numbers. Timing being a factor for a few reasons:

• RapidWeaver 4.0 is fresh in peoples minds
• There is a lot of new activity and 3rd party development surrounding RapidWeaver
• There are a great deal of new users
• RapidWeaver is fast approaching critical mass

And as always, luck can always play a big part in these things. Some themes I've made in the past have been the right idea at the wrong time and have picked up more and more as time went on. cataLog Pro seems to be a case of the right idea at the right time. This, apparently, was a theme that fit the bill for so many people with a need for it at that moment. I've received countess emails to that effect, "This is exactly what I needed for a project I was starting."

With RapidWeaver really taking off as it has off late, I really ought to do another talk at WatRMUG (Waterloo Regional Mac Users Group) and reintroduce the Kitchener-Waterloo users to website building, the RapidWeaver way.

seyDesign 2008 made the cut

With all the commotion as of late it must have totally passed me by that seyDesign.com got a permanent listing on DesignSnack (probably a few weeks back now). It's always an honor to appear on sites like these, especially this one, because it helps you gauge your designs and see if you are really making the grade. Go ahead and give it a vote if you like seyDesign 2008.

I think it was more than a year ago now when the 2007 version of seyDesign got listed on this site so it's nice to see that my designs are still on track and hopefully improving in the public eye. And speaking of seyDesign 2007, that site is actually appearing in Design Meltdown's The Web Designers Idea Book, due out in October, which is just about the biggest honor any web designer can have bestowed upon him. Hopefully the site appears in a good light and not as an example of what not to do, lol. So if you are a seyDoggy or seyDesign fan, or just a fan of great web design, head over to the Design Meltdown store and pre-order your copy.

Enter The Web

I took a support call from a customer one time and it came up in conversation that he uses WYSIWYG web editors such as RapidWeaver or DreamWeaver to visualize what he is doing with his web designs. He then asked me what I use... "Nothing," I replied, "not until I am done, pretty much."

Baffled, he asked how I could possibly grasp what was going on without seeing it in from of me. I proceeded to compare it to a musician reading sheet music. The musician doesn't need to here the music to know what it will sound like when performed off the sheet. That analogy did nothing form him.

I then drew the comparison to The Matrix, "You know when there are watching all those characters fall on the screen, but to them it paints a picture of what's going on in there? It's the same thing for me (and most web designers I imagine)."

"Wow!" he says, "So you can just see it in your head?"

"Yup."

"Cool," he says, contemplatively, "can you fly too?"

Sadly no.

seyDoggy and RapidWeaver, a new approach

What am I up to right now? Doing what I love doing best; creating new works of wonder for a platform... erm... designing themes for RapidWeaver.

I know I am only speaking to 5-8% of the general population when I say this, but if you are one of the lucky ones who owns a mac, then you owe it to yourself to at least check out RapidWeaver. It's a great, do-it-yourself web authoring app that is insanely extensible by virtue of its proud and dedicated 3rd party development community (of which I am a long standing member).

I have been developing RapidWeaver themes on a professional level for nearly three years. In that time themes have gotten more and more advanced with each new version of the platform. Cric from Rapid-Ideas was the first theme developer to really take themes to that new level of versatility years back when he introduced the first theme boasting some 500,000 variations. Pretty soon we all followed suit.

Before long though (myself included), we all had products that would take a month or more to complete, nearly as long to update, would upload dozens of css files, a multitude of images and scripts, complex themes mean more support... themes and the site they make were getting slow and fat! The mental taxation on the end user swimming in a sea of variation to make a site that only uses 10% of a themes ability is immeasurable. And it goes without saying that this method of theme development is getting costly, especially if a new theme is a dud.

For the last few years I have been looking at ways and approaches to trim the fat. #1 priority was to eliminate support. While developing themes for THEME WEAVER I really looked at streamlining their approach so that support would be nearly non existent. I found that fewer options in a RapidWeaver theme were the key. This was hard to adopt in my own, already established theme library, so I looked at ways of simplifying the user experience.

To do this I started to employ javascript to do some of the dirty work for the end user; rounding corners, adding drop shadows, etc... But with this came compatibility issues with other 3rd party RapidWeaver products, namely plugins that used javascript as well. Though things were getting easier for the end user, for me? not so much. For the last year I have been enjoying great success with very little support; a stellar combination, but on the back of an aging library of themes. I needed new products, ones that I think are hot, designed the way I want them, easy to use, require little support, lightweight, cost effective to make...

That's when the lightbulb went off. I want to make themes for me, a designer... I want to make designer themes! And so a new line was born at seyDesign.com; Designer themes, a new line of RapidWeaver themes that are just good looking and nothing else. Not ground breaking, not revolutionary, not stuffed with feature over feature... just hot themes!

Yesterday saw the release of the first RapidWeaver theme born of my new approach; Tagg.

iPhone 3G, Apple App Store and FlipSide5

With the launch of both the new iPhone 3G and the new Apple App Store, things around seyDoggy have been a little harried trying to cross all our t's and dot all of our i's in preparation for the big day. Everything went smooth without so much as a hiccup. I had to pull a couple of all nighters but all for the good of the site.

So it would appear that both FlipSide5 and Michael Sanford are leaving an indelible mark on the industry. Revered in many articles as the man and company to watch simply for the passion they pour into their products, one thing is clear, the level of commitment is unparalleled (and I speak from experience).

Since everything went fairly smooth, I thought I would take a moment to breeze past my local Rogers store on Ottawa and Fischer-Hallman in Kitchener and scope out the iPhone lines. If the crowds were gone I would have stopped in to grab a 3G. No such luck as the crowd was camped out in lawn chairs and been since the store opened hours before.

It's the whole package that counts.

Sometimes it's not the big things that make all the difference in how a company is perceived as either professional or amateur. Sometimes it's the littlest, nearly overlooked details. A perfect example of this is how a DMG is put together, or how an installer is skinned. This is how I came to find myself killing a few hours today by rebuilding all of the most recent update installers for seyDesign theme updates.

Some time ago, seyDesign.com became the first RapidWeaver theme developer to use update installers to deliver their theme updates in the form of an application that installs only the changed components as opposed to distributing the entire patched theme to end users. seyDesign.com recognized that many users, having had made many modifications to their themes, or having added bits and bobs to their themes innards, did not appreciate all of the work involved in returning their theme to their custom state. Update installers avoids many of these troubles, most of the time.

Being an early pioneer of these practices I hadn't taken a whole lot of time to learn how to make this process my own, instead, treating it as a utility, not another opportunity to spread corporate identity. Since the seyDesign 2008 relaunch, however, I knew that the time was now to make things pretty, to follow suit with the look of the site.

Next up I'll be rebuilding all of the theme DMG's to look just as good.

We finally launched seyDesign 2008

Did you hear that? That was the sigh of relief heard around the world. Why? Because I just launched the biggest site porting I have ever done in my career with nothing more than a few typo's to sully to good name of seyDoggy. In case you've missed the buzz, I am talking about the LONG awaited seyDesign 2008 relaunch, a rather large on-line store and resource that sells RapidWeaver themes.

On the surface it doesn't look like such a big deal right? But underneath it all is a site that consists of more than 280 pages which include product write-ups, downloads, support areas, contact forms and store pages. Nearly all of this was rebuilt from the ground up; new copy, new graphics, new style, new typography... a ton of work! But the most challenging in any site relaunch is not have any broken or orphaned links, files or downloads. So far I have only managed one broken download link. Not bad out of 280+ pages.

Now that I have this monster behind me, it's time to celebrate the Canada Day long weekend the best I know how... CAMPING! I will catch you all again on July 2. w00t!

Digg this! | Vote for it!