Participant 6

TASK 1

[2:06pm] Chooses MySQL because she's used it before.
[2:06pm] Appears to think that she is naming the database "usability2" instead of installing drupal into that db
[2:08pm] Task complete.
[2:08pm] "I dont really know what I did"
[2:08pm] "I don't really know what all I did".. thought she was creating a database
[2:09pm] didn't understand what it is all about, where it is, why it's important, etc.

TASK 2

[2:09pm] Not comfortable with the different bits of LAMP stack yet.
[2:10pm] reading all the welcome text.
[2:10pm] wondering whether or not to create conent or configure
[2:11pm] says if she was doing it for herself, she would configure first
[2:11pm] clicks "create content" in step 4
[2:11pm] Using welcome text for navigation.
[2:11pm] wondering whether or not use article or page
[2:13pm] Does not appear phased by text format widget or vertical tabs
[2:13pm] Good explanation of text formats.
[2:13pm] understands text formats
[2:14pm] ISSUE: Full HTLML text format does not say that all tags are allowed
[2:14pm] Understands why there is not a wysiwyg in core
[2:16pm] used to admin_menu.module
[2:17pm] gotten really used to using it.. having a hard time navigating /admin
[2:17pm] looks to be trying to change the front page url to node/x
[2:17pm] rather than using the promote options.
[2:18pm] Found 'front page promotion' in the content types description
[2:18pm] "doesn't really make sense to promote a page to the home page"
[2:18pm] "It doesn't really make sense to promote a page to the home page"
[2:18pm] doesn't get that "content types" sets default settings. Thinks only articles can be promoted to front page
[2:18pm] Going to create an article instead of promoting the 'page'.
[2:19pm] ISSUE: 'page' is badly named and largely misunderstood
[2:19pm] Thinking about using a block instead of the article now.
[2:19pm] But sticking with article for now.

TASK 3

[2:20pm] "oh geez... ok"
[2:20pm] "oh geez" - when hearing the task description.
[2:20pm] straight to admin/build/menu
[2:20pm] knows she needs to use menus
[2:20pm] hesitation about which menu to use
[2:20pm] reading description of all 3 default menus
[2:22pm] decides against menus, thinks she'll "cheat" and use a block
[2:22pm] Reading block help text.
[2:22pm] seems to be comfortable using blocks.
[2:23pm] uses panels on her personal site
[2:23pm] Maybe used to panels?
[2:23pm] "was set up for me, I don't see it here"
[2:23pm] ISSUE: there is no linking between menus and blocks
[2:24pm] Creating a custom block for the link.
[2:24pm] ISSUE: PHP stuff appears for brand new users
[2:25pm] ISSUE: we need to stop anyone from melting down my servers by actually using PHP
[2:26pm] BUG: block module should require PHP module to use it for block visibility.
[2:28pm] "there it is, yeehah!"
[2:28pm] thinks views is part of core, or at least that she has the option of using it

TASK 4

[2:33pm] Idea: patch core to have Taxonomy -> Classification for a test or two?
[2:33pm] Deliberately avoiding using menu settings in node/add instead of using admin/build/menu
[2:34pm] Knows that main menu appears in the theme - so wants a different theme which puts it in the right sidebar.
[2:34pm] Not yet connected blocks and menus.
[2:35pm] loves using blocks. doesn't appear to realize she can control menus with them.

TASK 5

[2:36pm] realizes a content type should have "unique characteristics"
[2:36pm] understands content types.
[2:36pm] not clear why workshop should be a unique content type, because there are no unique fields or permissions defined at this point
[2:37pm] really wants admin_menu
[2:37pm] went to admin/content/node
[2:37pm] looking under content management
[2:37pm] not looking under site building at all
[2:37pm] just found "content types"... adding a new one.

TASK 6

[2:39pm] totall understands user management. great explanation.
[2:39pm] user management > roles
[2:39pm] "this is pretty straight forward"
[2:40pm] added role, configuring perms
[2:40pm] no understanding of inhereted perms
[2:41pm] appears to understand permissions better than 90% of #drupal.
[2:42pm] task complete

TASK 7

[2:42pm] I think she has access to our google doc
[2:42pm] uses word terms.
[2:42pm] immediately knows to use taxonomy
[2:42pm] • ultimateboy maybe wonders if she read up on our blog posts... ... ...
[2:43pm] "my impression of vocabularies is that they are main groups of terms. and uhm there are some limitations because you cant create terms in one vocabularly and use those terms in another vocabulary"
[2:43pm] understands that there is no overlap allowed between separate vocabularies.
[2:43pm] (i.e. no shared terms)
[2:43pm] awesome. taxonomy nailed.
[2:44pm] eh.. maybe not
[2:44pm] Creating a hierachy within the tags vocabulary
[2:45pm] should that even be possible?
[2:45pm] Workshops -> (beginner, intermediate, advanced)
[2:45pm] yeah definitely
[2:45pm] hierarchical tags? really?
[2:45pm] nonstandard, but working.
[2:46pm] wth! associating terms now
[2:46pm] Adding related terms as well.
[2:46pm] wants beginner and intermediate to be associated. "thinking of ways that might help me"
[2:46pm] Making this task far too complicated
[2:48pm] clicks split summar button "silence"
[2:48pm] "it's weird how body is separated from the other field, and the other field has no title"
[2:49pm] after fumbling around in the dark she guesses what it does pretty accurately.
[2:49pm] seems to understand the teaser more than most..
[2:49pm] Looks like she knows what a teaser is, but not what the teaser splitter does.
[2:50pm] opens parent item dropdown, and then just ignores it
[2:50pm] great success.
[2:50pm] • ultimateboy really likes that patch
[2:51pm] (I posted a link yesterday, but we probably shouldn't, since it may be possible to identify people that way)
[2:52pm] NOTE: scrub links from posted irc logs.
[2:52pm] trying to enable tags on workshop now
[2:52pm] navigates to content types, and edits workshops.
[2:52pm] can't find a way to enable the taxonomy
[2:53pm] seems to conceptually understand almost all of this, but sometimes has issues with execution.
[2:53pm] "a ha"
[2:53pm] goes back to vocabulary edit, enables it for workshops.
[2:53pm] admin/content/taxonomy - spotted content type settings as soon as she edited the vocabulary

TASK X: hide author and post information

[2:55pm] totally nails it.
[2:55pm] task complete.
[2:56pm] yo dog, I heard you like blocks. So I put a block inside your block....

Task X: Display conference address on righthand side

[2:57pm] immediately realizes she should use blocks, goes to block pages, executes cleanly.

Task X: make the conference information appear at /generalinformation

[2:58pm] assumes path.module is already enabled
[2:58pm] knows of pathauto
[2:59pm] realizes she would do it sitewide
[2:59pm] used word "enable"
[2:59pm] has now found the modules page
[2:59pm] has found and enabled path.module
[2:59pm] seemed intrigued by the new field modules
[2:59pm] Looks at Fields briefly.
[2:59pm] Not the first person to do that either.
[3:00pm] "what do you think of this page".... long silence.
[3:00pm] too much help text on modules page
[3:00pm] PRESENTATION: "maybe it's good to be a little bit intimated about enabling and disabling modules"
[3:01pm] after enabling path, "im not quite sure where that is going to pop up"
[3:01pm] "I'm not quite sure where that's going to pop up, so I'm going to check my content to see if I have a new choice here, yaaay I do!"
[3:02pm] crosses fingers no forward path please.
[3:02pm] "oopsie"
[3:02pm] uses back button.
[3:03pm] "content has been modified by another user, cannot be saved"
[3:03pm] presentation quality right here...
[3:03pm] finds error weird, because that would mean two people are editing it at the same time
[3:03pm] "hmmmm"
[3:04pm] problem solving skills = good
[3:04pm] realizes using back to edit it created a "conflict"
[3:05pm] Clicked "create content" instead of administer content, momentarily lost.
[3:05pm] copys the absolute path into the path field.
[3:06pm] copies*
[3:06pm] BUG: No validation on the url alias field on the node form.

TASK 10

[3:08pm] Planning to look in permissions for text format allowed tags.
[3:09pm] conceptually understands input formats. Doesn't know how to change them though
[3:09pm] ISSUE: URL Aliases = path
[3:10pm] thinks it might be module related
[3:12pm] Creating a new text format to allow the image tag.
[3:14pm] ISSUE: text format UI sux

[3:15pm] paraphrase "everyday I struggle with menu building, taxonomy"
[3:16pm] Knows how to do content administration, finds site building challenging "making a unique homepage with static and new content"
[3:17pm] "i love drupal, I love the idea of drupal"