Implementing my new design was fairly straightforward once I had the design done. The major challenge was locating all of the embedded style information in Radio scripts that would hamper the rendering on my desktop or on my weblog. To my surprise there were only three scripts that contained embedded style markup that caused my design to break. I removed the div, span, and font markup from them and tested it. I've provided links to the three scripts that I am using right now below. I am sure there are other macros that contain style markup, but they don't affect my weblog or desktop site.
One question remains: where do I store my CSS files? I decided to store them outside of Radio on my server. I suppose I could store them in the gems folder or create another folder specifically for CSS files and direct it not to render. The way I have implemented CSS is using the link tag to a file that uses the import at-rule. This method fires off a separate TCP stream through which all CSS files are downloaded rather than downloading them inline. The Radio cascadingStyleSheet macro renders the CSS markup inline, which weighs down your pages.
Here are some observations from my experience. Radio needs two sets of completely different templates: one for desktop and one for weblog. Currently, your weblog and desktop are linked by the Main Template. The desktop site, at least for me, is pretty data intensive with my editing interface, news aggregator, and other data widgets, plug-ins, and tools I use. My weblog is pretty linear so that it doesn't need a lot of real estate. Radio needs an easy to link to archiving mechanism that makes sense to readers of the weblog. I'm using outlines to create links to monthly and weekly archives. The weekly and monthly archives don't mean much right now as I can't figure out a way to create a list of posts from titles and permalinks.
