drupal upgrade timeline

I upgraded a Drupal installation for a test project last week, just a point upgrade. In the interests of my own memory, here’s the timeline, copied from a bunch of post-its on my desk. Times noted are when I started doing each task.

9:06 mysql backup

9:14 file backup

9:16 set offline mode

9:18 switch to standard theme

9:19 disable extra modules

9:23 local new files (I have no f’ing idea what that means: moved the new version into the regular local folder?)

9:25 delete files on server and upload new version

9:31 try to run update.php

9:33 realize that I accidentally deleted/forgot to re-upload settings.php, modules & themes

9:40 run update.php

9:41 upload new versions of webform & nodequeue

9:43 re-enable modules

9:47 run update.php again (for the upgraded modules)

9:48 switch theme

9:49 switch to online mode

So: 43 minutes altogether, 33 minutes with the site offline, 9 minutes of THAT being the result of user error. (I suppose one should always allow time for user error.) Not bad.

Oh, and I’m going to the Drupal MiniCamp next weekend. πŸ™‚

Somebody’s Face in a Book

I had been deliberately avoiding Facebook (Your Face in a Book Dot Com, as Kermit calls it)….

But Kermit, who has been collecting people he used to know, IIRC in part to have some sort of jumbo-tron party sometime in the next 2 years (?), told me that Marsha, one of my high school valedictorians, fellow Academic Decathlete, is a web designer. Working in higher ed. (I’m almost surprised we hadn’t crossed paths somewhere already.) And that was the thing that kicked me over into signing up.

I have a MySpace account, mostly for professional reasons (back when I was at Pierce), but I only ever ran into one or two people from my past, and I don’t ever log in.

Facebook, OTOH, is chock-full of people I haven’t seen in a long long time. Which is kinda cool, on one level, but also a little disorientating.

Back in college & slightly thereafter, we used to describe the intersections of various social groups as “when worlds collide.” Actually, my relationship with C turns out to be one of those moments: I met him at the children’s museum, where I’d worked with one of his best friends for a couple of years. But as it turns out, one of his high school buddies is a guy I knew briefly when I had a…fling (?) with one of that guy’s friends. (It’s a long story.) Said HS buddy even “warned” C about me, not that that changed anything…and I’d even already told C that particular wacky story, IIRC.

I’ve rarely been good at handling those moments. It’s not the healthiest thing in the world, but I get into being one way with one set of people, and a slightly different way with another set of people, and so on. When the Venn diagrams interset, I don’t know how/who to be.

So in Facebook, I’m “friends” with a couple of people from work, some of my web-friends, people I knew in high school and college (not always very well), some very good friends from my past, my ex-roommate, my ex-boyfriend, a couple of cousins, etc., etc. It makes for not know which “voice” to use, or what bits to “disclose” (it’s not that I have tons of secrets, there’s just some things I’m more private about), because it’s all pretty much right there in these weird mixed friend groups.

About that…friend? Really? Ugh. The guy my sister had a crush on in junior high? Not a friend. My co-workers? Not friends. High school acquaintences? Not friends. (As lovely as all those people may be.) I’m all for being in contact with all these fragments of my life — it’s like the reunion that never ends! — but “friend” not so much. (I think LinkedIn does this pretty well, honestly.)

I feel like I’ve kinda got this down with the other “social media” stuff that I do, although I veer back & forth about who to be with Twitter, so I’ve just set up Facebook so that (a) anybody can see it (if you knew me back when & are curious, you can look w/out making a connection) and (b) it imports all the stuff from other things that I’m up to. (With the exception of Twitter. I don’t know why; something about that just doesn’t feel right.) And then I can just keep being this particular Elaine and using this particular voice. Such as it is.

the redesign

A little over a month has passed since we launched the new website at work, and I realized that I want to write down the whole process out here before I forget everything!

It started last fall; I organized usability testing with about a dozen credit union members. That was fun, if tiring. They came in and used the website on a laptop in a small conference room while we were videotaped. I had some specific tasks I was interested in, plus I had them show me what they do most often. (Don’t Make Me Think continues to be worth every penny I paid for it. Bought it myself at Half Price Books, years and years ago. I should probably go get the 2nd edition!)

That found the usual glaring issues, some of which I even corrected in-between testing sessions, as well as some bigger process problems, general surfing tendencies, weird usability issues, clutter, etc., etc. Over the fall I went as far as I could with the old design to make it more usable, but at some point I just had to break from the old and try something new.

Aside from usability, the site suffered from an over-reliance on the main logo colors, which are quite vivid and should really be used like chili powder: sparingly and for specific effect. (It’s something you see a lot in academia, too, especially on school sport sites. It seems like the obvious thing to do, and yet it can really overwhelm the content.) And it didn’t really use any of the design styling of our print materials.

So I had some ideas about what to emphasize, some new colors to take from our larger corporate palette, and some basic shapes. I also knew I wanted to drop from three columns to two. Which led to the usual sketching, futzing, walking around the block & muttering to myself and so on.

Eventually, I was struck with the Big Idea…

Five years ago, I went to WebVisions sort of by accident. At that event, I saw Jeff Veen give his big talk about making the web better. (I’m sure it was more specific than that, but that’s the jist that stuck with me all these years.) And one of his examples was the HayNet site (which, sadly, has been entirely redesigned — this guy has a screenshot of the old version), and the “Got hay? Need hay?” navigation. (Here’s a picture of him doing what looks like the same presentation, more or less, in 2006.) At the time, it cracked me up, and it was such a weird example that it stuck in my head.

I think I also read a blog post around the same time, probably complaining about stuffiness in credit union website designs, or at least lack of creativity.

Together, it turned into a navigation concept: 80% of our site content falls into “Have money?” or “Need money?” so that became the guiding idea for the homepage. (Figuring out how to link to that other 20% was the big challenge, which I’m still kinda working on.) I swear the general design just flowed naturally out of that idea + color palette + common shapes.

But of course there was plenty more refining to do. Many of my internet friends were helpful in this phase, but I should give the special shout-out to Dylan, who looked at several iterations, pointed me at grid design resources, and, well, gave me the finishing touch for the homepage.

The whole grid “fad” took off as I was working on this, and that stuff ended up being really helpful in placing the different elements of the pages so that they didn’t feel entirely random. The final result isn’t quite a grid, because the math with mixing pixels and percents and ems was just too much for me, but it’s darn close.

And unusually for me, I did all the original design work in Photoshop. The design I had in my head would’ve been too challenging to mockup in HTML/CSS right off, especially since I needed to have samples to show my boss and an internal committee.

I had an opportunity with this redesign to look at online banking, too: not the internals, but the frame and the navigation. I was brutal in paring down the navigation to the honest-to-god basics. (So brutal, in fact, that I had to do some adding & tweaking post-launch. I’m still glad I started simple.) I thought really hard about the verbiage, and making it as clear as possible.

So once the first draft was done, I went out to a branch and hung out for a morning grabbing random members & asking them to look at the printouts. (I gave them Starbucks gift cards.) The feedback was really helpful, as always, and prompted some modifications, but also confirmed that I was heading in the right direction overall. The branch staff looked at them too, and were really excited. That’s especially nice because IME internal folks can sometimes be the hardest on a website redesign. The lingo doesn’t bother them; they know where to find stuff, etc.

Then it was time to start turning the pretty pictures into actual HTML & CSS, which was much less difficult than I’d anticipated. Of course that homepage split slant thing is kinda complicated, and yes, there are a few IE-specific hacks. (max-width, a bit of hasLayout, some width issues that I think are box-model wackiness) But in general it’s really, really simple. Two columns with the left column absolutely positioned, a header and a footer. I used Eric Meyer’s Reset to clear out most of the default styling. A basic print stylesheet; a basic mobile stylesheet (which I think still needs a little work).

I made a few sample pages, and put them out there: first for employees, then for members. For members, I created a comment form, too, so I could get the feedback. It was even more helpful than the morning hanging out in the branch. Yes, the usual mix of “OMG how cool!” and “OMG how horrible!” but also some specifics for tweaking.

Among other things, the general impression that the home page was a little…bland. So I tried a bunch of ideas that never got anywhere, some of which were, honestly, fabulously ugly. This is where Dylan gave me the idea of a subtle touch that added just the right amount of visual complexity. Yay for public domain photos!

At the same time, I was working on setting up my site templates, specialized styles, and Online Banking. That last was a fascinating challenge, about which I will say no more, other than that I’ve learned to do crazy, crazy things with JavaScript, and jQuery rawks.

Then launch day. I came in extra-early, did my switchover while the Online Banking person was doing her switchover, and there it was.

Of course, that’s never the end of things. There were long-standing typos discovered, extra-weird browser glitches (WebTV? SRSLY?), and quite a few tweaks and corrections for Online Banking.

But after a week or so, it was mostly settled out. And I’m happy. I feel good when I look at it, more than anything I’ve ever designed before. Other people seem to like it, too. “Clean” and “professional” seem to be the adjectives of choice, and those are adjectives I can be proud of.

I was also pleasantly surprised that the Need money/Got money navigation was generally very well-received. Only one person was really unhappy about it, and quite a few others mentioned it specifically as a positive. I felt like I was going out on a bit of a limb, but it turned out to be worth it.

I know I’m not done, not really. A website design is never actually done. I keep looking at it, I keep listening to member and employee comments, and it will change over time. That’s just how it is.

(PS to self: I’d like to add a side-by-side screenshot here.)

DrupalCamp: Views

Jennifer’s Drupal Cheat Sheet (I think I’ve linked to this via delicious at some point)

Some references to what she’s used for this.

Pages to be made with Views: Upcoming classes, Courses We Offer, Instructors

Having a good (pathauto-style) URL helps for getting blocks onto pages, matching with wildcards.

Views under Site-Building. Starting point is a lot like starting with a content type, and similarly no 2 views can have the same machine-readable name.

Basic choice is page vs. block. Basic explanation of blocks. If it’s going to have a URL, it’s a page, if it’s going into some other page, then it’s a block. Can make the same View have a Block & Page version. (?)

View types (more types avail thru modules) – full node, then another full node; same thing with teasers; table (grid, one row/node); list; Calendar & date browser she’s never used. (Very curious about the date browser) Here she uses table.

“Front Page View”?

Pagination options. Alpha pager module available. (For youth site taxonomy pages?)

Filters (I think this is where I got stuck) – oh, scheduling! Maybe I need to add effective date as separate from the actual publication date. “Field_course_date: Date” or something like that – greater than or equal to now.

(musing out loud: unique *something* with an effective date today or earlier?)

if you have sorting enabled on a table, don’t use default sorting?

clicking on Edit on the page created by a View goes to the View editing page.

“clone” (kinda like that thing in the intranet software)

sorta wishing I were coming tomorrow. special topics for theming sounds interesting, as do Panels & Image Handling.

Views Theming Wizard?

export/import, can’t use on the same site, but from one site to a different site with the same structure. also used as a way to do staging from dev to production.

audience q: how would you improve views? to be able to put into a table a field from a reference node. yeah, that would be cool. she’s thought about writing a module to do that. “there may be a module that does that, but I haven’t found one.”

the drupal slogan: “there’s a module that does that.”

“Views Union, I tried, it’s awful.”

Can do some crazy thing with list view as a dummy view and then frankenstein together something. Whew.

Exposed filters. O hey. That would be nice for jobs.

Adds an “exposed filters” area after clicking “expose” button. Locking the operators makes the most sense. [“Digital painting” class? That would be RAD…is that the subject for Painting the Web? πŸ™‚ ] “Always lock the operators…makes no sense to the end user”

Could you set up the filter zone as checkboxen rather than one of those weird select things?

And is there an Ajaxy way to filter w/out clicking submit? (jQuery) An audience q that’s fairly similar…

“Views Filter Block” makes the filtering zone take less space.

[oh, another diversity point: this seems like a wider age range than one often sees. the occasional “kid” but also quite a few oldsters.]

Instructor page with Upcoming & Past/Current class lists – Block Views.

[more] link on Block vs. pagination on Page

Empty text if there are no results “This teacher hasn’t taught anything yet” or on a page view w/exposed filters “try your search w/out filters” or similar.

Can’t do “only classes that this teacher has taught” in filters. Nothing here that’s dependent on which page it’s being shown on. Aha.

Arguments…

based on the URL, pass info to do extra filtering. Oy that looks complicated “argument handling code views” search πŸ™‚ arg(0) = node, arg(1) = 34 (or whatever)

set the instructor number that goes into the argument to the number of the node.

so why do you need pathauto?

to put it on the page, edit Blocks. oh, and it’s just in the content block. (I missed how to make sure it just shows up on the right pages. oh, that’s where pathauto comes in, pattern matching.)

I think I’m going to ask my Q about the weird rates stuff on the DUG list, or maybe go to one of their meetings.

DrupalCamp: CCK

weird screen problems!

Basically, this & the Views session after lunch are one session.

Hey, she’s using an example. Excellent, I always learn better from examples. An art organization that offers art classes.

Planning, writing out ahead of time what you’ll need. Connecting instructor & course to create a scheduled class. (Some of what I was trying to do with rates?)

Each piece of information should only be entered one time. (Ala normalizing databases.) Linking to those pieces. (Yep, she just said the same thing re: database design.)

Now the how-to. “Content” in the CCK section. (for downloading)

When you start, all that’s there is Page & Story. After CCK is installed “Add content type” tab/link is available.

Machine-readable name is usually same as human-readable, but w/out spaces, etc. (node template teacher.node.tpl?)

Descriptions matter most when you have lots & lots of content types.

Every node has a title & a body. Full stop. But may not make sense in context of node. (In this instance, what about alphabetizing? Oh, she’s renaming it as “Displayed name of this teacher” — so presumably you could add first & last names separately? Although that seems annoying.) “Your main goal is not to get phone calls…support calls from the users of your site.”

Usually leaves minimum at 0, because users often have partial information. (I like how much she’s thinking about the needs of the data entry person.)

More thoughts about workflow in re: published by default — is that what you want?

Discussion of whether to use Body for something like Bio, because of conflicts with creating Views and/or Templates. (Looks like she learned something new! Fun.)

Create fields once the content type has been created.

Borrow a field from another content type. (Borrow a feeling? πŸ™‚ Also, can’t have 2 different fields with the same name.

She probably should’ve left off  one of her content types before the presentation?

Node reference comes bundled, btw, but has to be enabled.

Ah, now I can see that you can use a text field w/validation for dates. (And does ANYBODY use datestamp?)

On Node Reference, Use select list when only a few, use autocomplete text field when lots & lots.

Hundreds of other CCK content type modules. (Although not so many for D6. Oh, had good chat over the break with Greg (heyrocker guy) and ??? (tall guy, maroon t-shirt) about whether to go D6 or D5. Sounds like for a new site, D6 is the better way to go, even though some modules are still missing, buggy, etc. That’s just where the energy is.)

Covering some particular issues in the image type, including checkbox. (Oh, can put name of person in alt attribute via theme!) If resizing pic, don’t worry about max file size?

If stuff isn’t required, make sure the theme doesn’t break down. Definite focus on making it work easy for data entry, make the Drupal developer do all the work. πŸ™‚ You can also have a default image. Audience member had problem with default image, conflicts with “required.”

Discussion of weight and D5 vs D6. (Hiding weight & using drag/drop? teh HAWESOME.) But…she’s missing some key modules. Grr. This is the basic issue with deciding on a version: D6 is just a better user/admin experience while D5 has more stuff.

“Mrs. Jane Q Smith III”?! heh. Ah, she has done just what I was thinking. First/Last name are fields for sorting & searching, but hidden on the display page.

Can use a single date field for start and end date, and a single date field for times.

CCK field “Date” — viewable via Calendar, Date API? (missed some of that.)

More detail on the Node Reference type; checkbox for which node type(s), and then also advanced that uses Views for selecting.

Now for Taxonomy…mismash of wording references (as mentioned in Drupal 101) “kinda schizophrenic” — and apparently another thing that got better in D6.

[so what’s the deal with lunch?]

Back to the planning list. How did we want to organize this stuff? 2 sets of terms: one set for subject area, one for age level. Better explanation of when to use taxonomy! Things that cut across multiple content types. A class has subject area & age level; an instructor has subject area(s), and a scheduled class draws both from class & instructor, so doesn’t need either.

(She did a bike trail site? Fun.)

Chewing on how to

Question about how/whether to use synonyms; she hasn’t used them, not sure how they work in practice.

Are there performance penalties for using CCK vs writing your own module? Might be faster, but harder to maintain. At what size site does it matter? Audience member answer, would have to be something damn huge (my words) for it to matter at all. Drupal.org uses CCK, handles the server load on the server end. Another audience member suggests that with shared hosting it might actually matter. Jennifer mentions caching, “turning off Views UI gives huge performance boost” and same with other unused modules. NWSource guy said their bottleneck was the database, everything is in CCK. And “so much easier”

CCK & custom modules can interact in weird ways, too.

[note for the gender-sensitive…I’m impressed at the balance here in attendees. I think Jennifer is the only woman presenting, but she is fantastic.]

DrupalCamp: drupal 101

Or 105, as the presenter says. (CivicActions)

He asked a bunch of questions about experience. Not covering installation.

As you as you go into that core file, just imagine me with a ruler smacking you on the wrists.

Document your code.

Civicactions.com/drupal_glossary Γ’β‚¬β€œ created to give to their clients

Ò€œnodeÒ€

scale of modules that goes from very tiny to very big. CCK, Views & Panels are absolutely critical, can build almost anything with those.

taxonomy – makes Drupal powerful. taxonomy is the entire system of vocabularies: sets of terms. vs tagging/folksonomy? now you can set up a vocabulary that’s a free-tagging type, users get an auto-complete field to show the already-created terms but allow new terms on the fly. so…module Taxonomy Manager. πŸ™‚ how very drupal. heirarchical vs non.

(wrists hurt. gr.)

be cautious about hierarchical vocabs, too fancy = not used, at least with user-generated content.

in all cases: things build on each other. he’s working on a decision tree whether to use a taxonomy vs a custom field. wd be very interested to see that.

complex concept, which I missed part of: a blog entry about a restaurant that connects to a recipe, and it’s all about Chinese food. (ah, the “Chinese” part needing to be a vocabulary term to get the cross-associated stuff going.)

in many places category is used to mean term, vocabulary OR the whole taxonomy system. way confusing.

term -> vocabulary -> taxonomy

“admin menu” module. very clever. going into the permissions section & roles. you can also duplicate a role & then add on more permissions. (or remove? not sure.)

I wish I’d taken

Q: heard not to use user #1. is there a big reason? …other than being able to do anything accidentally? That would be the main reason. So user 1 should just set up the admin role, and then user(s) with the admin role do everything else. (some stuff about how they handle lots of different sites in a uniform way in their agency)

CCK. basic CCK, then modules for different types of content. (so is this where I’d get started with module-writing?)

Description…would be useful in an intranet?

(meta: is this session answering my questions? Maybe not. What are my questions? How could Drupal be used for an intranet? When the hell is D6 going to have all the modules I want? Also, he’s doing a lot of reading the screen.)

Restrict how many of each node type a user can create. Huh.

Use pipe character in list of allow values, then can change the labels as necessary still using a short value. I’m not sure I get the application, but it’s a clever concept.

Date vs datestamp? He doesn’t know the difference. (hm)

Sets all the date stuff early, because all the modules inherit that default, but can be changed individually.

Head screaming. Should’ve gotten coffee. Oh, while I’m drifting away from the presentation, this morning: just barely made my bus downtown, then when I got to the Oly transit center, realized that I forgot the laptop powercord & extension cord. (Also, I forgot my camera, but that’s less important.) Made a snap decision to go back home & get them, because not being able to take notes…well, those who read this know about how crazy-making that would be for me. Thought I could go home & catch the bus to get back downtown only a half-hour late. Saw the bus…leaving…as I was crossing the street to the stop. Walked downtown at near-top speed, probably about a mile, in the hopes of getting there in 15 minutes. Uh, no. (Darn close, though) But the bus was still there! Only, it wasn’t the 7:30 bus, but the 7:45. Apparently the 7:30 bus never ran or something. But after that, things went pretty smooth. Walked straight from Oly express to Seattle express, and just a couple of blocks from there to the W Seattle bus, and then across the street to here.

Image cache.

Theme layer vs configuring in the content type.

No recurrence in dates/times, which is apparently a long story.

drupalmodules.com vs. on the drupal site. best way to rate is to look at the issue queue, and if user # is under 1000, that’s a good sign. but drupalmodules has ratings. also has firefox search plugin.

Views – a query-building system. which nodes, what order, what fields from each node. Use the description well! Sign it if you have multiple people! Can easily have 30 views and not know which does which.

Argument is an advanced topic.

Whooboy that’s a huge list of filters.

Panels allows arranging views, nodes, etc. into more complex designs w/out themeing. (Session on that tomorrow.)

book review: The Principles of Project Management

disclaimer: I was given a copy of this book to review by the author, Meri Williams, who I met at SXSW 2006.

Oddly enough, this book arrived just as I was starting to re-read The Art of Project Management. So I couldn’t help but compare as I went, although I’ve now finished Principles and have yet to finish APM again.

I’m not a project manager. But I play one (on TV?) from time to time, as I think most “knowledge workers” do. I have 3 fairly sizable projects at work right now, in addition to the ongoing work, micro-project, etc. (For the curious: a micro-site for a new product, an interesting educational micro-site, and a complete site redesign.) I don’t have a “team,” but I have too much going on to just wing it. Although that’s what I tend to do, both at work and with my side projects.(Not to mention that my house should probably be considered a Project, and would probably benefit from some Project Management.)

In brief: Williams is focused on the person new to managing projects and getting through something right now with specific tools & tips. Berkun is more philosophical and psychological (although there’s plenty useful goodness, too), with a more literary tone. Either one is well worth the read.

On with the review of The Principles of Project Management…

I really appreciated the checklists, examples, and warning notes; I’ve littered the book with post-it notes reminding me of things to do, or try, or at least ask questions about. For those managing actual teams, the advice on work styles and issue tracking seems quite useful. I haven’t tried anything yet, so I’m not sure which will be most useful in practice. (Perhaps I should re-review in 6 months or so?) I was, however, inspired to put together a work breakdown spreadsheet for one project, which has already helped me clarify my deadlines.

I will quibble with the stand-up meeting suggestion, though. (Berkun suggests trying them as well, in a brief aside on meetings in general.) Stand-up meetings are harder than they sound, and require the same kind of focused facilitation as any other meeting.

I say this from some fairly painful experience: at my last job, I suggested the idea, and we did a daily stand-up (or huddle around the phone to include teleworkers) for a while, and it sucked. They can be just as dull and useless as any other meeting, unless everyone is interested in making them work, and there’s someone in charge pushing them to be useful.

One minor annoyance: at least two or three of the project phases are described as “most important” in the opening paragraphs of the related chapters. The writing also has a feel to it which I assume is either British or South African — there isn’t anything incomprehensible, but it does give an American a bit of a pause in places.

The section in Closing on handling a “total disconnect” was brief but encouraging, and as someone who’s experienced a few, gave me some thoughts about how to handle future situations.

The appendices have plenty of useful resources, including recaps of some of the tools mentioned in the main text. To my amusement, Berkun’s book is listed in the “further reading” section, which should signify the quality of the other recommendations.

Overall, I think it’s a great introductory text, particularly for people who are moving from doing to managing, or who are working on larger projects by themselves. The tone is friendly, professional, and constantly encouraging, making for a slim volume of helpfulness.

(As an aside to the whole review, I think I really need to get around to reading the Mythical Man-Month.)

mobile web revisited

This doesn’t come from one panel in general, but was spurred on in part by the panels on Saturday, but also from the overall SxSWi experience and things I’ve been mulling on for probably almost a year now.

Mobile web, in non-geek (non-affluent?) audiences, is probably still two or three years off. I’ve said it before, and I’ll say it again: it’s too expensive with not enough value for most people. As long as the carriers keep pricing where it is (for T-Mobile, my carrier, that’s an extra $20/month…per phone*), it’s going to come in slowly for a while. If the economy goes downhill, expect that to be even slower.

But after SxSW, I’ll add that there is an “on the other hand” — people who have mobile web are nuts about it. Admittedly, that may be because they’re already nuts about the web. (Sampling bias, etc., etc.) But it also seems to fill some rather particular wants. Yes, I was involved in a discussion in a bar where Wikipedia was used to settle an argument. (Margin of win in 2004 presidential popular vote, if you must know.) I saw mapping going on, and of course the incessant Twittering.**

So eventually it will be big, but eventually is driven by money. If the carriers want mobile web to take off, the pricing will change, and it’ll happen sooner. If not, it won’t.

What about the iPhone? I don’t see the iPhone tipping anything yet outside of geek culture. Here, in my real physical existence, I know one person who owns one. And he was at SxSW, which I think just proves my point.

And I refuse to speculate on wacky stuff with the Android Project, VoIP, or anything that’s not found in a booth at the mall.

There is, however, a third hand: texting. Texting is friggin’ huge. It’s so huge that even I got a text package added to our phones, and I am notoriously a mid/late adopter, if only because I’m cheap.

What does that imply for my professional world?

If we launch anything mobile web (be that site or banking), it would be inappropriate to expect it to be a huge hit right away. It has to be looked at as an investment for the long term: 3-5 years out. Doing it now is a case of getting practice, getting the bugs worked out, and maybe getting a little publicity. That’s not a bad thing, but it does mean managing expectations. And we need to expect that we will need to do something eventually, because it’s coming. Eventually. (…which seems to have been a long time already.)

Something that does texting, OTOH, could be a big hit right away, IF it meets an actual need. That means thinking deeply about context: who is using it? Where? To what end? Or to revisit Kathy Sierra: how does a text message from your credit union help you kick ass?

[update: for extra sarcastic goodness, see 5ives.com.]

* Most families, of course, are going to have multiple phones. So x2 for a couple, x3 to add a teenage kid, etc., etc. Plus don’t forget that phones that can do decent web are bigger (generally) and cost more money. As I heard at WebVisions last year, most people pick the cheapest phone that comes with the plan they want.

** I think of Twitter as the poster child for potential mobile social applications; I also think it’s interesting that they cross over all the online possibilities, including texting. That was my reason for adding texting to my phone plan.

tools for enchantment revisited

As I said in my mondo summary, I thought this particular panel deserved a few more summary and/or explanation and/or planning notes. I’m finding that my thoughts on this fall into a couple of categories.

First of all, I find myself wanting to go nuts on our intranet. It should be attractive and interesting, to provide a rich environment for learning at work. It should reduce stress. “Do something cool within 30 minutes.” Work more with HR/PERC to include more features on physical activity. Plus I want an entirely new way to think about knowledge transfer and reference materials, with lots more of people helping each other and getting good at asking smart questions, bringing each other in on jargon, etc.

On the public side, I want to find more ways to feature how members got what they wanted by being members, getting loans, etc., etc. The education site (my last project before sxsw) pulls back at me, too; storytelling to increase learning, plus using that learning to increase understanding of financial issues; and the same thing with the email newsletter, creating a higher-resolution experience? (It’s still a little vague.)

And a couple of a little reminders: make sure that features, esp. in online banking, show up in the right places (as much as I can); and check on getting good help for banking users.

summary notes: day-by-day

I’m planning, additionally, an “executive summary” (which may just go to my boss), and additional posts on: mobile web, casual gaming (maybe), Kathy Sierra’s talk, and municipal/public wifi.

Thursday, March 6

Travel day. Up early, to bed early. Cold & rainy in Austin, too rainy to get the bike.

Friday, March 7

Session: Respect!

Top folks from Happy Cog, including Zeldman, plus Doug Bowman from Google. Mostly, this panel provided a lot of validation of common experiences amongst web folk.

The most interesting takeaway: using something “unobtrusively visible” to have (written) conversations among different parts of the team; everybody can “overhear” what everyone else is doing. They use Basecamp for that, but I imagine there’s lots of ways to handle it.

Also that day…

Picked up bike. Weather better, but still on the chilly side. Broke my camera (slammed into an escalator railing) and rode 4 miles each way to get it fixed.

In the evening, went to the Higher Ed Meetup with Andrea, mostly as a lark. There were no get-togethers of financial web folk that I could suss out, and I didn’t run into any other singletons, either. πŸ™ But it turned out to be interesting, both personally & professionally, and useful as well. Point for work: got a contact from Pat for a WordPress guy who might be able to give me some comparison options for CMS stuff v. Drupal. (That makes more sense to me than it does in writing. Honest.)

Saturday, March 8

Session: What Teens Want

A group of teenagers (13-17, IIRC) plus an adult moderator. Important caveat that these teens go to either a tech academy at a local high school, or a prep school; YMMV.

Fairly marketing-savvy: they know that ads pay for stuff, but they also hate ads. Pop-up ads came in for specific and repeated denunciation.

Almost all have myspace accounts, which they refer to as “my myspace”, otherwise favorite sites were based on other interests (gaming, fashion, etc). None use mobile web. (I have more thoughts about mobile web to write in a separate note.) Although “casual” games are fairly popular and of course texting is big. Pac-man, for some reason, is quite the thing.

Cost came up as a factor repeatedly in mobile phone discussion, regarding phone type and features used; almost all rely on parents to fund their phones/plans.

Session: The Contextual Web

Nick Finck on mobile web; I had hoped that this panel was about more contexts than that. He covered the general idea of context in re: the web, which was useful in its own way as a reminder. Raised a question of curiosity about the context of online banking, which mostly takes place during the work day, presumably at work. What are we missing about that context? Also, all of his examples used the iPhone. (See mobile web notes for more on that.)

Also that day…

Sunny, but chilly. Lunch (etc) with H.A., which was wonderful. More futzing with camera.

Sunday, March 9

Session: Wireframing in a 2.0 World

Two of the ClearLeft guys. This was the only panel where I really got into the meebo discussions; I had to quit because I couldn’t chat & take notes at the same time. But that discussion was interesting, and confirmed my own hunch about their process: namely, that it ends up with something that looks too pretty. Plain, yes, but “designy.”

But I did really appreciate learning the general outline of the technique. JavaScript libraries used to create simplistic prototypes. It might be helpful for future projects. (Jumping forward: it makes me wish the panel on JS libraries had been remotely useful.)

Session: Emotional Design

An interesting mixed panel that actually had a blended presentation that worked well together. I have to make special note of this; like the previous panel (in the same room; hmmm) they stood, passed the mic back & forth, and had a single set of slides. It was too dark to see them very well, but otherwise it was an excellent presentation style.

As far as the actual content: an excellent examination of emotion towards things (where software is included as a thing), with the exception of a few almost-sexist quips. Things to look into or ask about: what does it feel like when something fails in Online Banking? how can the website make the connection with positive associations with branch/people? what is the internal meaning that people attach to credit union membership? what is the first impression of the website (or anything else, for that matter)? what do we want it to be? Also (this comes up again later): you can’t really promote what you don’t love.

Session: Logos (are bad)

Didn’t get anything out of it; felt like an uninformed ramble. Left early. (I ended up talking to Christina Wodke at Fray Cafe that night, and managed to express my unhappiness with the experience without being mean. That’s all I’m going to say in re: the Facebook interview debacle, which oddly enough, I missed by being in this panel & the next one.)

Session: Stories, Games & Your Brand

Something about panels right after lunch, I guess. This one felt too insular among the panelists, or maybe they’d already figured out that most of the audience was fairly familiar with the topic?

A few notable gems, though. To get to the elves thing, Office Max tried 20 different games the Xmas before; whatever you want to say about whether it helped them as marketing, it’s important to see the experimentation. Penguin Books uses a special “innovation budget” for some of its online writing experiments, rather than seeing them as marketing.

Plus a reminder about the huge casual gaming audience, which is usually described as middle-aged women, but cf. teen panel for other interested groups.

Session: Tools for Enchantment

I’d been curious about Kathy Sierra’s presentation style for a while, and I really enjoyed it; both the slides and her speaking style, plus the few audience participation bits. My one complaint is that she sometimes went a bit too fast, and skipped things under the assumption that we had seen a prior presentation. This session was dense with little bursts of ideas & food for thought. As in: I’m printing my notes right now so I can mark them up to make decent summary. [update: here’s my extended post]

Also that day…

DST = EPIC FAIL, according to Andrea. Or not. But wow it was dark in the morning.

MetaFilter meetup was very energizing at lunchtime; an interesting discussion of how people are online v offline, plus yes, Jessamyn & Gus do know each other. (So very small world. Gus, aka Jill, is someone I’ve known since junior high school. Mmmmm, band camp.) And silly things with photos/captions.

I hit the trade show for a while, which was more fun (and useful) than I would’ve expected. Connected with Dave O. at Raincity Studios, which might come in handy for Drupal stuff later, plus that was just a funny meeting. (Chit-chatting usual booth style, then he introduced himself, I went “oh, you’re Dave; I’m C’s wife.” “C with the big ideas?” “Yes, that would be the one.” Heh.)

The books at the Blurb booth were beautiful; I’d recommend them to anybody doing visual arts/photography. The Brain Machine at the Make/Craft booth was startlingly relaxing, and the booth itself was like being in the giftshop at the old museum. Checked out the Pro Drupal Development book at the Friends of Ed/Apress booth, but passed it up for the time being; I’m going to wait for one on Drupal 6. (Later this year?) Also had a very nice conversation about southeastern Arizona, where Grandma & Grandpa N lived, with the folks at the Film Tuscon booth, which comes back in a bit.

Most cool was hanging out at the O’Reilly booth. Catherine Nolan, who I worked with when I did tech review for Head First JavaScript, is hysterically awesome. Simon St. Laurent, the editor for Shelley’s book, came up and said hi too, was super-nice, introduced me to a guy (whose name I’ve forgotten!) working on a book about online communities, which sounds potentially quite interesting. (A side note about ’08 vs. ’06: I felt much less star-struck this time around, which overall was a good thing.)

Went to the Fray Cafe in the evening, which was as fun and funny and moving as Ralph led me to believe. Prompted by the conversation with the Film Tuscon folk, I told the story of my grandparents — an enormously long pause in the middle is all I remember, and then the MC getting people to applaud me into talking again. That led to the conversation with Christina Wodke, as mentioned earlier.

Then probably the best serendipitous moment of the entire trip, and one of my rare bursts of quasi-star-strucked-ness (?), running into Dori Smith in a parking lot, after midnight, and then talking for an hour. (Turns out she worked with credit union software, ages & ago. Good to know. We talked CU culture for a bit. So I guess that means that I did connect with someone CU-related. Hey!)

Monday, March 10

Session: The Web That Wasn’t

My notes, my fairly damn copious notes, seem to have vanished utterly. And I’ve already cleaned off and returned the borrowed laptop, so if they were in a text file, they’re still utterly vanished. This was one of the more interesting sessions, too. (expletive deleted)

What sticks after a week & the flu? “The Buffalo Public Library of 1983” (an article from 1883, in which a librarian imagines something that sounds suspiciously like the Intarwebs); Paul Otlet’s crazy library/index-card thing in Belgium: apparently, you could telegraph them a question and get it answered for a small fee, like a verrrrry sloooow Google. Destroyed by the Nazis. Ted Nelson is kinda nutty.

The most useful part of the session was the author bringing together common themes of visions of web-like things: two-way links, meaningful links, annotation, persistent identity/trails. In conversation with C later, it occurred to me that many of these are made unlikely by spam; their visions were (of necessity?) of smaller self-contained non-commercial systems. Also, (and this just hit me) perhaps they have something useful to add to an intranet?

On the bright side, re: notes: I did add some of his suggested items to delicious, all in the post of March 10/11.

Session: keynote with Frank Warren of Postsecret

My notes are nothing, really; just things I typed somewhat randomly while being deeply intensely moved. Something about Postsecret just hits me right in the freaking gut. It’s also a good reminder that as the personal use of the web spreads, more and more people are going to have bits of themselves, “non-professional” bits, out there, and not be willing to erase them for corporate life. (Had a conversation later on a similar topic over drinks. Obviously, and as long-time readers will know, this is something I’ve been thinking about for a Really. Long. Time.)

Session: Video Games & Corporate Training

One of two “core conversations” that I tried out. An interesting experiment; worth the effort in general, altho this one was a bust for me. (My notes have my thoughts on the format.) The casual gaming thing came up again, this time around training on specific topics. Casual gaming, like mobile web, may deserve its own post.

Session: Target Lawsuit Update

Most of the technical issues are so familiar to me at this point as to be not worth repeating. OTOH, it was helpful to see the list of types of “public accommodations” which I hadn’t seen before, as well as a number of particular notes about the legal issues that had previously escaped my attention. “a service related to a public accommodation” seems to be a key phrase.

There are things I need to check up on; right now the thing that probably requires most work is probably the least important: adding captions/transcripts to the TV & radio ads on our site. Also, it sounds like this whole thing is something to keep an eye on.

Also that day…

This was the day of truly insane rain. I missed the first session hoping that it would let up enough to bike in; ended up walking instead. Somebody told me that Austin & Seattle actually get a similar amount of rain; it’s just that they get in 10 minutes what we get in 2 weeks.

I think this may have been the day I finally got my camera really working, better than before even. (Smacking it while the lens was still open. Don’t ask.)

Lunch with Andrea. Really good lunch with Andrea. Reminder to her: when you have time, watch The Venture Brothers; the thing that your idea reminded me of was in the Brisbyland episode in Season 1. And I think I realized that what I want out of my (long-abandoned) Media Diet idea is something fairly semantic-web-like. Maybe an actual reason to learn RDF?

Another trip to the trade show, with more time at O’Reilly. (Minor ego-boo: Catherine introducing me to (?) as “one of our tech editors” (or something to that effect).) And bought the newest Postsecret book — signed — as a surprise present for Elizabeth, which she got in the mail yesterday.

That was also the night that I attempted to go out and didn’t end up having a whole lot of fun. Wanted to go to SXNW party, since it’s peeps from this part of the world, but I just can’t stay up that late, and the thing I went to before that to pass the time was immensely boring, plus I got cold. (Yeah, I’m kind of an old lady.) But some lovely random person left a lei of silk flowers on my parked bike, which made me smile.

Tuesday, March 11

Session: CMS Roundup

I was honestly not expecting this to be as good as it was. I missed the beginning because of a really interesting conversation that I’ll get back to shortly. IMHO, there is no reason to spend big bucks on a CMS. (I was going to add a caveat, but let’s just assume that every blanket statement has a caveat. Even that one.)

Going with open source means paying for knowledge (consultants, staff time, etc), but that seems to be true for any CMS being implemented in a commercial setting. Drupal is powering some pretty damn good (and good-looking) commercial sites. With the color picker, it’s possible to do micro-sites with one-off skins, similar to how sites on our intranet work now. It can handle external data being passed through without disturbing the original source. (Or something. I’m not entirely sure I understand how that worked.) But it has a hard time with singletons & edge cases in general.

Expression Engine is also looking good, and seems to have a lot built in; along with the WordPress conversation I had with Pat, that might give me several comparisons to make. (Should talk to Andrea about that too; isn’t HSU using EE?) Also, Jeff Eaton from Lullabot has a nice turn of phrase; the notes include my favorite bits.

About that conversation: I’d forgotten my mini-schedule, so I was asking around at the Lego pit for room info. I ended up talking to a Yahoo person, initially about CMSes. If I got it correctly, they have a few units using Drupal for intranet stuff, which was very interesting to hear. Plenty of pros & cons.

But also, the person was allowed to say, but not allowed to write themselves, that a bunch of stuff (code? it was morning, and I’ve had the flu since then) is going to be released open source this summer. Call that my scoop of the week. πŸ™‚

My source was really excited about some of the things going on at Yahoo, but really frustrated with PR folk for not being able to say more sooner; feels like that’s what makes it look like they’re “me too” with Google: they’ve been working on X for however many months, Google announces super-experimental-beta of X, then later when Yahoo announces their version of X, it gets called copy-cat. An interesting perspective. I continue to hope that they fend off the approaches of MSFT.

Session: Core Conversation: Specialization v Doing It All.

My notes are about 3 lines of not-notes, which is sort of sad because it was a really interesting discussion. HUGE group, 4 or 5 rows deep, but really engaged (and getting the last row to stand up made it possible to hear).

My odd realization was that becoming a web generalist was actually a form of specialization: before Pierce, my jobs included (mixed together): event management, database design, print production, admin support, grantwriting, teaching, managing other admin staff, and other stuff I’m forgetting at the moment. My faux title at the museum was Random Chaos Girl, after all. πŸ™‚

The question of which was “better” seemed to come down to organization size and personal temperament. For specialists (and for all of us, really), it’s important to be aware of the needs & skills of other specialists; for generalists (and I suppose people in general), to know enough to know the limits of what’s knowable for you, and when to call in the specialist.

Also, the moderator is part of a design/dev group that’s an un-company, which sounds very very interesting. Self-organizing groups & all that. Something to think about for myself for later?

Session: Secrets of JavaScript Libraries

I had really high hopes for this one; as did a lot of other people, apparently, because it was packed to the gills. But I was sorely disappointed. This ties with post-lunch on Sunday for the session low point.

Too large of a room, and I was in the last row, so I could neither hear nor see properly. The code samples in particular were entirely unreadable. There was no discernible structure to the presentation, and the panelists didn’t have a good flow amongst themselves. Might’ve gotten more by hanging out longer at lunch, alas.

Session: Municipal WiFi

I ended the sessions (more about that later) on something of a personal note, as well as on way too much caffeine. (Spilled my mocha on the carpet, even, in my excitability.) Like the Kathy Sierra presentation, this has too many interesting bits to summarize without a marked-up printout.

But it energized me enough to think seriously about how to do something locally, plus I have contacts I want to make. C & I had a pretty good chat about it on the way home from the airport, too, which once we are both healthy we’ll need to get back to.

Session: Futurists’ Sandbox

Ran into Glenda & Andrea (and masses of other people) outside of this one; it was the only one that really interested me, and was so full that we were sitting on the floor. But it was too weird, honestly, to stick with. A faux funeral/eulogy? I couldn’t get into it, not sitting on the floor anyway.

So we 3 all bailed together, and to good effect, I think. Ended up at the Hampton, for excellent conversations over drinks. Particularly enjoyed chat with Andrea, Tom & Jeff of Blue Flavor, and Paul Boag about self-branding, blogging/flickr boundaries, etc.; my long-standing rules of blogging. And before that, about driving/walking/biking in Seattle, etc.

Also that day…

Finally the weather got nice. (grr)

Had lunch with a nice fellow from Belgium named Hans. With that & Drupal, I think Tuesday may have been Belgian Day. πŸ˜‰ Always interesting to meet new people, learn what else is out there in the world. We talked CMS for a bit, and he suggested looking at Django; so yet another thing to go on the list!

Tuesday was my one and only “party night” at a conference that seems to have acquired quite the reputation. But I am a mild partier, so nothing particularly wild to report. (As if I would.) More fantastic conversations, including an incredibly thoughtful (if shouted) one about politics, with people I had not met until right then. On the walk to the hotel, got to put in my 2 cents about the importance of CCs in training of web people to someone where it might actually make a difference. That’s always a nice feeling.

Wednesday, March 12

Another glorious day; had immense fun biking to the post office with Elizabeth’s gift and then to Whole Foods, although getting from Whole Foods to the bike shop was a frustrating puzzle, even tho they are on the same road. Dropped off the bike, checked out of the hotel, hung out at the Hideout (reminder to self: name of the place where I had best. mocha. ever.), and then to the airport. Kept running into SXSW people, which was nice/weird/melancholy. Then airplane, then home, then…well, flu.