web

Part 3 of a series: Building out a full Drupal site in a weekend.

Now that my feet are firmly on the ground (and hopefully will stay that way for a time), I have a little time to write about the final stages of the Open Source Catholic website development... even though it's tagged as in 'beta.'

On the plane flight home, I was mostly finished creating the theme for the site. I hadn't opened it up in IE 6/7/8 yet, but I knew the main three or four bugs that would crop up, and prepared for them. I decided to write some postings (two articles, two blog posts, and a website review) for the website, as it's never a good idea to try to build momentum for a website on which nothing exists!

Part 2 of a series: Building out a full Drupal site in a weekend.

Well, one plane flight down, and a conference to go, I have the main structure of the theme set up (locally; haven't pushed it out to opensourcecatholic.com yet). I decided to go with Zen 2.x's -dev releases, for the simple fact that it's new and the way the Zen project is moving. There are a few rough areas in the documentation, mostly in the 'Readme' file for installing a subtheme, but I got through everything okay.

This theme, I hope, will make its way onto the fine Drupal.org theme repository; getting a CVS account, I'm sure, will be fun ;-)

Today I contributed my first 'original' piece of content to Drupal: a handbook page entitled Create a CSS-Only Theme. Since the first time I heard about the Stark theme (a Drupal theme which does nothing but expose all the 'stark' html output of Drupal core), I've been thinking of ways to enable designers to quickly build out unique and beautiful themes for Drupal. In Drupal 7, I think this will be a reality. (And maybe, just maybe, I'll create a theme for inclusion with Drupal 7 in the next few months).

I was browsing the Drupal Theme Garden a few days ago and was reflecting on how incredibly boring (if not ugly) a large share of the themes looked. Out of all the themes I viewed (over 50), I might consider using only 10 or so on a production site for a quick project that I didn't want to create a theme for.

Later on, I read this post on Steven Witten's blog [Acko.net] from 2007, and read through every single comment, because I am extremely interested in the issue of Drupal theming. If you are at all interested in helping Drupal be more themeable and appealing to designers, you must read the post linked to above. Go ahead - read it. I'll wait...

...okay, now that you're back,

A few of the comments in Steve's blog post deserve a mention...

From the blog posting itself: "Not enough Drupal people are savvy enough about theming and design to help out with even small tasks (like a banner) or even give quality tips and feedback on other work. The result is that theming and design receives little attention. Most contributed themes and sites could look a lot better, if they just themed it some more. And getting patches into core that give the defaults a little more oomph is tough, as they are often considered to be useless embellishments.

In the past year, I have seen more and more mobile visitors to some of the websites I maintain, and the lion's share of those mobile visitors are using Safari on the iPhone or iPod Touch. A few of the sites receive more than 5% of their visits from such devices. For those sites, I thought it would be fitting to give them a little better mobile treatment, optimizing the layout for the iPhone.

Earlier today, Apple announced they were starting a beta service of iWork applications online, free for anyone (with a licensed copy of iWork '09) to try, called iWork.com. The premise is this: You make a document in, say, Pages, and then click a button to put it online. You let your editor/friend know the document is online, and then he or she can login to the iWork website, view the document as you created it, and put sticky notes on it. This way, the editor/friend doesn't have to have a certain application (like Word) on his or her computer to view or make notes on your document.

Apple's not the first to have a product like this—Google has had its 'Docs' suite of online writing/sharing applications for a couple years already (it's free and it also lets everyone work on the document together)—but they have the opportunity to win the Online Office Suite battle, which has barely begun.