day 1 keynote

idea: “instawalk”? an alternative version of a campus tour?

neat! GE & CSX intermodal (music) video. scored by guy from Ladytron. highly recommended. 🙂 (also on soundcloud)

“so I get to make music videos about trains. super cool.”

are there natural partners for us to connect with our audiences? like is there actually a way to reach to someone like John Green (sp?) after that tumblr where someone noticed a catalog photo with the [????] t-shirt?

so I’m wondering what the metrics are for a project like this (GESpringBreakIt) in relation to the overall business…

if even you spend a bunch of time/effort getting the word out before a social media event, news really doesn’t get out until things actually start. (which kinda makes sense.)

and I keep thinking about the student projects project, where I’ve been getting stuck with the tech (argh gnarg), instead of having a chance to think about the communication and content goals. Maybe we should talk about not actually trying to use Portfolio as a DB at all, but to use it like we do with photos on the web, as a place to explore (?!) and cull from. but that definitely requires thinking about an editorial calendar for these things. (and how that connects with alumni profiles and student profiles, faculty profiles (?!), etc., etc.)

morning musings

Even though it’s totally backwards from what you’d expect with the direction of my journey, I’m finding myself crashing out early and then waking early. (Doesn’t help that my hotel room has absurdly noisy HVAC.) So I’m in a chain coffeeshop a couple minutes walk away, looking out on an unfamiliar city.

(Minneapolis, MN, for the “Confab” content strategy conference. I’m here through Saturday afternoon.)

The most startling/dismaying thing, actually, is that the trees here are still entirely bare. Not “on the verge of Spring” bare, but entirely midwinter-style bare. When I left home, the poplars in the front yard had not only shed their dreadful “flowers”, but were fully leafed out. And yet the temperature is about the same. Not the weather: there was lightning last night, and supposedly we’re in for thunderstorms today.

Everything from yesterday’s workshop is rattling around in my head. How do I put it all into practice? What’s going to be most useful?

Got downstairs & realized I’d locked myself out of my room. Got to the coffeeshop, started checking my email, and realized I don’t think I have my badge. So I need to get back to the hotel room before breakfast & get all that taken care of. Good times.

All the mochas I’ve had here have been too hot. Not sure what’s up with that.

I want to find a yarn store while I’m here, but between time, distance, and weather, I’m not sure that’s going to happen. I’m not going to run out of yarn, though, I’m pretty sure of that. I’m working on a sweater vest for C, which turns out to be a fantastic project for doing while listening & taking notes. Vests for everyone! (Although actually after this I’ll probably start on more socks.)

Went out to dinner last night with two total strangers, and had a great time. (Slogan of the evening: thanks for the guac, Hallmark!) It was fun to get out, to talk about professional stuff with new people. It’s funny, in this crowd I feel more like a techie, more like a programmer, whereas in almost any other tech event, I feel like only a semi-programmer, if that makes any sense. It’s all relative? Or at least it’s all imposter syndrome. (I also have related thoughts about gender and the difference between Confab & other conferences I’ve been to, but I’m not ready to articulate them yet.) But at the same time as all that, I’m feeling REALLY good about how our team is doing at work. Not that we don’t have lots still to learn & do, but we’re in a good place and doing great stuff. I’m also more convinced than ever that an iterative design/development/content approach is the right thing, that big ta-da style relaunches are more trouble than they’re worth. I know it can’t last forever, but right now things are good.

And after spending the last day explaining Evergreen in person to a bunch of people, I feel even more strongly about what the college does and is, and how special it is.

But I really do need to get back to the hotel and get a new key and go get my name badge. :\

content strategy 101

“Is planful a word?” audience: “No”

guides the planning of what we are going to do and not going to do with our content

a different set of questions: not just what, but a bunch of other questions. (THIS SLIDE.)

for what it’s worth every morning I wake up feeling dumb and not caught up

core strategy.
content components: substance, structure
people components: workflow, governance

to talk about the web as a platform is a category error – jeremy keith quote (conference crossover FTW)
“we’re not going to talk about refrigerators”

role clarity, process and tools

“we think if we have this magic word governance that all of our content problems will go away. No.”

the case study: junglebox.net

RANDOM FLAME TRANSITION.

stakeholder: who is accountable, who is responsible, who are the leaders of the team

side conversation about content strategy & agile. “Our number one [role?] is to keep asking questions”

interesting to think that TBH we are neither Agile nor Waterfall.

when you begin [content audit] understand the primary buckets of information and how they relate

could I write an XSLT for going through all the pages in a folder? get a CSV that could be imported into Excel?!

exercise: do your own content audit (use this for user workshop)

gradual continuous audit is kinda like painting the Golden Gate Bridge. (intriguing)

links to additional resources for auditing

“content wrangler” (which has ALWAYS been my role, all the places I’ve worked, all the way back to the CMT newsletter)

“group therapy” (ahahahaha. seriously, I need to write the actual version of that blog post.)

“where was I? bitter? listening? right.”

“tell me more about that” (HOLY CRAP I THINK I’VE ACTUALLY HEARD HOLLY SAY THAT.)

fascinating interview experience

“facilitate discussion across disparate disciplines”

suggestion to invite people out for coffee interviews – half an hour, “hear more about what you do” (is that feasible as a smaller scale version of the “work session”?)

first question to ask of a stakeholder: “what keeps you up at night?”

we should totally do a research thing across print & web, to go out and talk to various prospective student audiences. can someone not-me do that?

yay, card sorts! (except, gotta back up first…)

so in our current process, maybe even before figuring out how to organize it, talk about who owns it, how it gets updates, etc.

“respect the complexity”

“As a bear, you have some core objectives”

super-vague financial services industry “strategy” that totally reminds me of the credit union’s mission statement.

strategy statement (this slide.)

should we do any of this before Sandy leaves?

the strategy can limit what content initiatives get started. “we’re not going to go down to the campground, we’re going to the river”

she actually suggests starting with the tactics of content strategy, that actual strategy is HARD.

“as a content strategist, you need to know a little bit about a lot of things” (again, that’s pretty much how I’ve been in every job ever, even pre-web.)

messaging pyramid: I actually feel like we’re really doing well with this, or at least that’s the direction we’ve been approaching asymptotically.

1-3-6 exercise, is also in the book.

“content strategy is not a project. content strategy is a process”

“what is it that we’re going to shift?”

the messaging pyramid needs to go to all the deans, senior team, etc.

“your message should not show up as content on your website”

really, seriously, this needs to be the thing we do at our next team meeting.

messaging pyramids: per audience!

this would be great to do in conjunction with our existing audience & goals.

Exercise! [note: this is some serious noodling around…]

an education you can afford, that allows you to connect your interests and goals, that makes sense in the real world

we are a place where you can really explore and discover, where you do more creative and exciting things than anywhere else.

we give you a chance to get an education that uses all of you

we give you an excellent education that isn’t like anywhere else

a school where you can be you while being successful as a student, a person, a citizen.

Evergreen is a college where students use their whole life experience and connect across disciplines to do more with their future.

But effective feels like the wrong word. Successful, purposeful. Get careers (and graduate without a lot of debt), but also be good citizens, engaged, creative, thoughtful. An education that exposes you to more.

See more. Do more. Make the connection. Be exposed to different perspectives.

It’s interesting because I’ve had to go through and do the explanation a few times here in person of “what even is Evergreen”.

Mentioned that when she was asking how that went, and interesting discussion of difference between business position and messaging. And the message is more the emotive part.

Again, try the 1-3-6 exercise in a CMS user group? Which is nice because it gets people thinking about other folks’ websites.

Style guide. OH HAI.

She references the mailchip guide, which is what we were working with a while ago.

Voice: who are you, centrally.
Tone: its implementation in a specific audience/circumstance

what are our tone adjectives? and what are the examples? – we need these for the CMS users!!!

Friendly

Yes: Connect with everything you need to get started and succeed in college.

No: We are very happy you are here and we look forward to helping you succeed at Evergreen.

Smart
Yes: We give you the power and the responsibility to take charge of your education. See an academic advisor to get a broader perspective on choosing and using what you learn.

No: Evergreen students need to take charge of their educational development, since there are no required courses, and we encourage you to do this in consultation with an academic advisor.

Creative
Yes: instead of taking a bunch of unrelated classes, you learn about the interconnections of subjects in the real world.

No: In order to address this need in a rigorous and effective way, the College took two years to develop a new way to connect faculty and students that preserved the centrality and integrity of full- and half-time interdisciplinary programs.

It’s funny, I found a lot of both the yes AND no bits throughout the site. I think our writing has gotten so much better in the last year.

Not what we talk about, but how we talk about it

Find the extreme examples, maybe even from competitor sites? Like what Justin did with the intro sentences in that one workshop.

“Content Center of Excellence” 🙂

Empowering them?

“write like you talk”

give more constraints to help people from feeling overwhelming

a continuum: “welcoming, but not pushy or demanding”

editorial calendar

“You can’t know all the things!”

Portal: what are the top tasks? Do we have analytics? (I think so….) Audit all the materials that are focused on internal audiences.

The last step in our process of sheparding them should be developing an editorial calendar?

“Making plans to review or create content”

so also relates to the This Is Week X concept.

OH HEY. If we have these editorial calendars for each section, can that all feed INTO “this is week X”?

And for connecting some of the pieces that are NOT for prospective students: the magazine, news site, and something else that I can’t remember.

(oh, right, the Evergreen Mind blog.)

So maybe DK isn’t entirely wrong about having a sequence of stuff, an editorial calendar for admissions — but to think about it in a different way?

“also the cake. the cake is very powerful.”

PAGE TABLE. THIS IS THE TOOL I’VE BEEN LOOKING FOR.

If you commit to this content, you’re also committing to this maintenance schedule. <3

But you don’t do this for every page, but key pages.

Are the page tables and the wireframes being created together? (audience Q) that would be awesome, but usually wireframes are already done.

what is something bad that keeps happening?

symptom: we can’t get stuff from faculty.
problem: our internal setup isn’t actually organized around the pieces of content that we’re creating. faculty don’t have any direct

symptom: last minute magazines

symptom: freakout from specific stakeholder(s)

Knitting and coding, part 1

purple socks
Socks I made for myself

This summer I learned how to knit socks. And not just socks, but two-at-a-time magic loop socks. Which if you’d asked me two years ago, when I’d made a couple of scarves (and as it turned out, was actually doing the knit stitch wrong), whether I could’ve done such a thing…I’d’ve been exceptionally skeptical.

When I started that project, I didn’t know anything about sock construction, and I’d never used the “magic loop” technique. And even with a group of fellow knitters working together, I just got too frustrated (there was a LOT of cursing, and not just from me). So I used one of my favorite debugging techniques: picked out the smallest possible piece of the project, and figure out what’s going on with that. I made a coffee cup cozy, so I could understand the magic loop part. (Magic loop involves doing some weird stuff with a reeeeeally long circular needle instead of several double-pointed needles (DPNs). It’s actually easier in the long run than using DPNs in some ways, but it’s a different way of thinking about the creation process.) That got me to the point where I understood enough to try two at a time, and socks start out as just plain old tubes, so that gave me enough time to get really comfortable with all of those parts before I tackled the weirdness of sock heel construction.

The first time I made a sock heel (which in this particular style has three components: a flap, a turn, and a gusset), I was basically just following along by rote, as I’ve done many times particularly with JavaScript. “Cargo cult coding” — just copy this thing and if it works, it works, if not…who knows? The sock heels were the same way, reading the instructions very meticulously and just doing exactly what they said.

I’m on my sixth pair of socks now (although that includes two pairs of baby socks for my nephew), and now I understand the process and the technique enough to even second-guess a pattern or make up for a mistake I may have made earlier. (Or most importantly: how to adjust a pattern designed for DPNs to magic loop.) There’s parts I can’t always keep straight in my head, not unlike knowing that a function exists but not being 100% sure how it’s spelled or whether there’s a underscore. (Damn you, PHP.) Which side of the sock gusset should be SSK and which side should be K2tog? Sometimes I just have to do one and see if it looks right. Sometimes knitting could really use code hinting…perhaps the material itself is the code hinting.

With every new technique (language, stitch, etc) I’m full of frustration and self-doubt: nothing makes sense, I can’t believe this could possibly work, I’m not smart enough, dextrous enough, etc., etc. I cuss at the materials/tools, myself. And then it just CLICKS. I don’t know how that happens, really, although a lot of it is getting the right help.

I’ve learned over time what kind of help works for me. I had the worst time learning JavaScript. THE WORST. I was a full-time webmaster, writing quasi-applications in PHP, and I still couldn’t make heads or tails of JavaScript. It was the saddest cargo-cult coding when I even tried. Then I read DOM Scripting (mostly on a looong bus ride from Lakewood to Auburn, IIRC) and it made the critical connection I’d been missing, which was to tie it to something I understood really well (HTML) AND to use it in contexts that I actually needed.

Similarly, the whole Ajax thing seemed sort of strange and magical and confusing — and then I was a tech reviewer for Adding Ajax, and that connected what I already knew about writing little PHP things to the JavaScripty bits, and I realized it actually wasn’t that big a deal. I mean, yes a big deal that it can be done, but not as huge as I’d made it out to be.

I mentioned earlier that I spent the first few months knitting wrong. For the knitters in the audience, I was knitting into the back of the loop; which is a subtle enough mistake that it doesn’t look totally wrong, especially when you’re just learning it at all. But it throws off the gauge and the feel of the knitting, so things don’t fit quite right. And it also meant I had a hard time understanding how to increase stitches, which is what I was trying to learn when I discovered my problem. And what I discovered, in addition to the solution to my problem, was the kind of learning materials work best for me with knitting.

Surprisingly enough: not video at all or photos generally, but the right sort of drawing, ones that show the three-dimensionality of both the yarn and the needles (and fingers, to be honest). Along with text that uses the things I already know, written clearly. Not unlike what I need from coding help.

I’ve been sitting on this post for a couple of weeks, so I’m just going to leave it here. There are some other connections in my experience of both knitting and coding, that I’d like to write about later:

  • Picking patterns is a lot like picking modules, plugins, and other open-source tools.
  • Craftsmanship in general, knowing your tools and materials.

Thoughts on free labor

Been thinking about a few things since reading Ashe Dryden’s (amazing!) post on The ethics of unpaid labor and the OSS community. Go read it; there’s a lot there, and what I’m writing here is just noodling at the margins.

First, I read Linus Torvalds’ “Just for Fun” a long time ago, maybe just after it came out, since Wikipedia lists it as being published in 2001, and I distinctly remember reading it at the beach in Steilacoom when we lived in Lakewood, which was 2001-2002. So my recollection is vague, but it seemed to me that he was in some way being publicly supported (welfare? student?) when he first started working on Linux. And so I wonder how much a good safety net, in assuring some amount of financial stability, would allow more people to participate in open source.

Second, my first fulltime job was at a children’s museum, and I worked with a woman who was an excellent artist but who didn’t get a lot of respect at work. (I wrote a bit about her for Ada Lovelace Day in 2009.) The managers finally started putting her talent to use, but she confided in me once that it wasn’t as awesome as she’d thought it would be, partially because doing art for work left her with less energy for art on her own time. It’s something I’ve since heard elsewhere in other endeavors, and sometimes experienced myself, but I always associate it with Mona because I knew how gifted she was.

Third, the part I can’t entirely wrap my brain around is this idea that you’d want to hire or work with people whose main hobby is the same thing as their job. Doing other things gives you perspective. Even if they’re not serious important things like taking care of kids or working an extra job. I took a class over the summer, and it allowed me to be more of myself AND I got a better idea of what our audience is doing. I knit, and play games, and work on my yard, and those things are intrinsically pleasurable (mostly), and also make me a well-rounded human who talks to people who aren’t programmers and things about problems that aren’t in code. (Except the knitting is totally code.) I believe in my heart that whole people make better stuff.

DrupalCon 2013 other stuff

Driving to Portland – this trip was literally the farthest I’ve ever driven anywhere, the most I’ve ever driven on the freeway, and the first time I’ve driven in Portland. (A city I find remarkably confusing. As I said to Elizabeth: I haven’t been to Portland if I haven’t gotten completely turned around at least once.) And it was fine, even with rush hour in driving rain. The rental car had satellite radio, so I listened to BBC World Service most of the time. I got to enjoy a lovely drive along the Columbia River by the airport. Cruise control was helpful with the long stretches as well, definitely helped my old-lady-knee. I only drove into the convention center area once, on Friday, and otherwise it was very straightforward to drive from my hotel to a park & ride and catch the Max into town.

About that hotel – I’m still annoyed at ending up staying Jantzen Beach (which is a long story) but the hotel was decent enough, and I even got to watch the latest Game of Thrones.

And I also stayed with Mom and Elizabeth in their new pad way out in northeast Portland (practically Gresham), which is a nice place. Even got to have a home-cooked meal, first time eating that way with Mom in probably close to 15 years. I stayed with them Monday night and Thursday night, which made for much more relaxing drives from Olympia to Portland and back.

The “hallway track” – I enjoyed visiting with people I’ve met before (Catherine, Kronda, Dave, Greg D), people I’d only known from the internet (Eaton, Relly, Ashe), and people I met for the first time (Beth & her partner (Matt?), Johanna). I never did get to play Bad Neighbors. 🙁 I think I got some good advice, though, on actual work-related stuff. And it felt good to be in a community, even if I had to deal with occasional bursts of social anxiety and/or imposter syndrome.

By the time I checked in, they were already out of women’s XL shirts. I actually haven’t yet tried on my women’s L; we’ll see how that goes.

The conference website was horribly slow, and terrible on phone/tablet; the app wasn’t available for Android. But the printed schedule booklet was actually useful.

The food was a mixed bag. I actually liked the Tuesday lunch best (sandwiches), over the hot buffet lunches on Weds & Thurs. Wednesday’s lunch was particularly meh. I was very glad that Pantheon (?) had a food truck with breakfast sandwiches on Wednesday, and that I went to j Cafe on Thursday for a breakfast sandwich. Protein FTW.

I didn’t actually go to any of the social events. Loud parties not really my thing, plus the whole mess of the Jantzen Beach hotel. Did get to go out to dinner with a bunch of people on Wednesday, and then saw the opening act of a show after. (M. Geddes Gengras, trance-y synth music; I bought a cassette.)

I took notes (as terrible as they turned out to be) on the Transformer, and I’m glad I had that instead of a full laptop, much lighter, especially for what I was using it for. I have a hunch I may have actually lost some of my notes to the dreadful wifi, although it’s hard to say for sure. I possibly should have used just a text editor instead of the WordPress app.

Coat check was awesome, and more events should do it. (Same with free transit pass, BTW.) If I’d had a nicer knitting bag, I’d’ve just gone with the tablet & knitting, rather than my big Timbuk2 bag.

Overall, I’m very glad for the opportunity to have gone to DrupalCon and I would definitely do it again.

Edit: also, I got to spend a little time (not nearly enough) with Elizabeth late Thursday afternoon, going shopping on Hawthorne. (Bike for her, yarn for me.) It was super-fun, and I was happy to chip in to get her a cool new bike.

DrupalCon 2013 session roundup

So my individual panel notes are terrible, or at least remarkably cryptic. But I’ve gone through and gotten the highlights from all of them, which should help with using this info later. I’d also like to write up something about the non-session parts of the event, maybe later today, maybe this weekend.

Tuesday

Large-Scale Drupal at OSU — dry, mostly geared towards the Ops side of things. Lots and lots of detail, managing huge numbers of sites. One thing that I want to remember for later is that they’re now using more Organic Groups vs separate sites.

Asset Management in Drupal 8 – part of the Scotch initiative, using some external thing called Assetic, to better manage inclusion of JS & CSS in Drupal themes & modules. Looks intriguing, not sure how much it’ll be in the final D8, or in what form exactly. If it works, it could be amazing, and a huge improvement over both D7 and Cascade.

Higher Ed Unconsortium (panel from 3 CA colleges) – this session had the unfortunate luck of being in a dim room right after lunch. I do like the idea of “messy, hasty pluralism” in terms of trying lots of things in parallel. Want to see their project (http://edudu.org/) at some point.

Post-Mobile – great presentation, not tons new to me, but gave me some things to think about in terms of structuring content for remixing, including the possibility of an entirely different model of content ownership. Cryptic thing from my notes: “model meaning, not presentation (and maybe not ownership, either)”

Content Strategy the RPG – mostly made me feel good about what we’ve been doing with content strategy. Interestingly enough, she recommends manual content audits (vs automagic) so that content owners feel the pain. Three things to look up more about: “page table”, a LEGO methodology, and “orbital content.”

Wednesday

Keynote (Karen McGrane) – Just pure awesome. Interesting that she’s very positive towards Drupal overall, but quite (justifiably) critical of some new initiatives, inline editing in particular. Things to look into: content strategy that includes digital signage; “content packages”, metadata is the new art direction.

Design Ops – Sort of a weird beat poetry/performance Tumblr presentation. A couple of specific things to look into: experience maps, continuing to develop a UI library.

UX Spaces – An interesting technique for handling UX development within the constraints of implementing in Drupal. (I think it can be generalized to UX in relationship to CMSs in general.) Sort of a diagram: in a “space”, there is data, behaviors, and users. Think subject verb object. And having those diagrams allows for reworking into Drupal things. Some interesting modules mentioned: Display Suite, Geofield, OpenLayers, Image styles, Lightbox2, Node Ownership.

Using Twig – The new templating language for Drupal 8; it was “committed” to core on Friday. A interesting demo of the simplicity and readability of the system, plus some ideas for how it might be more deeply integrated into Drupal. I’m very excited about this change. Looks to be easier than both the current Drupal template system AND what’s available in Cascade.

Thursday

Keynote (Michael Lopp) – I am deeply ambivalent about this presentation. Some of it rang true (the general concept of the Engineer, the Designer, and the Dictator; I think my life goal may be “Content Engineer”) and some of it felt off-putting and elitist. In particular, the idea of substituting a person’s digital life for a resume or business card strikes me as prejudiced against people who aren’t able to participate that way: newbies, people with lots of non-work responsibilities, the shy, those under various NDAs, etc., etc. And of course there was the whole “mom as non-technical user” thing that was just a cheap laugh and totally distracting.

Drupal 8 Configuration System – Missed a chunk of this, and ended up sitting way off in the corner, so I feel like I didn’t get as much out of this one as I wanted. That said, I think this is yet another excellent step towards a Drupal that’s going to be significantly easier to run and comprehend. I like the idea of taking configuration out of the database (because I’ve been bit by that), and it sounds like they’ve done a lot of work around creating a good flow for dev > staging > live. (This is not a huge surprise: the very first presentation I saw from Greg, he talked quite a bit about those issues in his work at the Seattle Times.)

Responsive Discovery – Very thoughtful & moving and also good stuff about doing research and tools for understanding process. See http://responsiveprocess.com/ and http://hellofisher.com/secret.php for good stuff.

Friday

Code Sprint – I didn’t get to do much at the code sprint, but I did figure out setting up a Drupal 8 environment on my laptop, got to meet some people, and clicked “re-test” on a bunch of patches for Twig. I’m glad I went, and I’d do it again.

responsive discovery

note: cmi d8 init presentation was interesting. I think it’ll be useful.

haveaproblem.com

responsive process website

experience map: this might be JUST the thing for admissions

lunch & learns: talking to the content creators

ux spaces

“everybody has a role to play in ux” (re twitter convo from last session)

a bounded set of interactions: action <_ ->content model

in a site w/4 menu items, each one is a space

they can be nested

( subject verb object ?)

as a [role], I want to [do a thing] in order to [benefit]

(true thing I heard yesterday: “as a user, I may or may not have committed murder”!)

some interesting module suggestions — take a look at those.

I like this sketching technique for thinking about navigating through the catalog, maybe also the research/application process?

designops

closed mode vs open mode

experience map

making fun of using twitter bootstrap?

our own UI library? Justin has gotten a pretty good start on that, but we definitely need to get that broader & deeper.

make the docs (not too many) – share the docs – maintain the docs – ux dashboard

make a decision RIGHT AFTER the testing