Participant 2

TASK 1

Database blew up, so moving to Task 2.

TASK 2

page = static
not phased by vt
"just the same old" > vertical tabs.
article = dynamic
article = dynamic
used breadcrumbs to go back home
finding content -> admin/content/node

TASK 3

straight to blocks
then to menu
Straight to blocks, then menus.
seems more confident with menus, looking at it for a long time
Trying to remember how to put a node in a menu - hasn't used it for a while.
ISSUE: Looking at the menu, but no obvious way to put the content into it, so trying to get back to what he created.
back to the original node, then menu settings.

TASK 4

"trying to find out content I just made" then went to node edit of that article - his words
was expecting all content to appear in menu
now task 4
is getting distracted on the goal. focussing on permissions instead of content types
Knows about users and permissions.
Creates a role first.
ISSUE: edit role is completely useless page.
(except to change the role name)
seems to be locked into the users section
hasn't looked outside of that since task started
looking hard under content management for adding type
realized it was under site building eventually
Got to content types with some guidance.
(probably because bojan said "content management")
confused by title and body field labels
Thinks the field labels are default values.
Knows about promoted to front page option.

TASK 5

Looking for 'content' heading in permissions, found 'Node' instead.
But got there anyway.
Giving edit own and edit any permissions.
know about content permissions and configuring them with confidence
'without more information I would probably check any of these that say workshop'
assumes there are more settings that need to be set in order to give this access to speakers

TASK 6

thought "tag"
expects tags to already be on the node edit page
went straight to create workshop. looking for tags/category immediately
Clicking through the node/add form looking for it.
assumes permissions problem
Originally posted an article which has the tags field.
Associates the workshop content type with speaker role - even though he's user/1
looking under node permissions settings
sees taxonomy
now looking at user settings
really thinking this is a user issue
now thinking content type
opening everything
when editing content type
Sighs every time he opens the comment settings fieldset.
not seeing any options to setup taxonomy from within the content type config
finally sees taxonomy
finds taxonomy
move taxonomy to site building??
this interface is confusing.. would read help text
if that does not help, would resort to d.o docs
confused by the default vocab setup for articles
gets that there are different types of vocabularies
"Looks like there might be different types of vocabulary and tags is just one of those types"
setting up free tagging.. though we are asking for a strict number of terms
goes to list terms before add terms
adding beginner/intermediate/advanced to tag list
people <3 admin/content/node. Everyone goes there every time they are looking for their content.
"I see tags up here and I'm curious what the circle is"
interesting side point, free tags are not weightable, so if one were to create a list of free tags using views or what not, you could not sort by weight
ultimateboy: you can do it on the term edit form.
not for free tagging
ah.. not drag and drop
when told we wanted to link to all beginner workshops at once, he chose the original workshop as the parent
(in menu settings, while creating the content)
didnt see the "beginner" tag in the lower right of the node
or didn't realize significance
what is the difference between main menu and navigation
ISSUE: username on Navigation menu title makes it hard to find in admin/build/menu overview
might be an issue on the tags
ISSUE: you can create a menu item from node/edit but not from taxonomy/term /edit
might be solved by a better UI for adding menu items in general
wants to create a 'page' to list taxonomy terms
ISSUE: cannot enable a vocab to act on a type from the content type config
Editing content to try to remove the submitted information.
looking under authoring information vertical tab
Made it to content types after ruling out authoring information.
display settings patch = success.. again ;)

TASK 7

immediately thought block
"blocks are the pieces able to be positioned on the page"
always opens up fieldsets.. just in case there is something relevant "makes me feel better"
looking at all possible settings "makes him feel better"
All radio buttons are empty in the "Show block on specific pages"
task 7 follow up
remembers to remove block from /admin by using page specific visibility settings
actually, role specific visibility settings first. then page specific
slight misunderstanding of the task

TASK 8

module page is "simple"
impressed with its organization
first time he used it: "impressed"
everything is in once place
knows he needs to go to the node to change the path
fine with vertical tabs
wonders he can put spaces
find path settings in new tabs easily

TASK 10

ISSUE: there is no task 9 ;)
:)
went to node/x/edit to enable img tag
thinks a module might allow img tags
quickly realizes that it's not. calls it 'basic functionality'
paraphrase "its pretty basic functionality and therefore cannot be a module"
thinks it might be a content type setting
realizes it's not a content type setting, looks at modules again
potential issue, with image api in core, this would add a module to do images...
Wonders why there's no tag in default html.
default html tag list in filtered HTML even.
expects to be able to change settings for text formats from the text format widget on node/x/edit
thinks it may be a permissions issue now
"I might actually click on this link (help) to get more information"
ISSUE: filter help page is broken
(content too wide)
finds "text formats"
finds text formats
ISSUE: configured/edit/configure
expects to be able to 'edit' text formats, clicks configure instead because 'it's there'
ISSUE: configuration options should be under the edit tab

TASK 11

thinks "block"
Looking in blocks for search.
assumes search is already enabled
Looking for search in 'disabled' blocks region.
Now looks at modules.
realizes that it is a module
thinks search might be a module
enables search.module
fails to notice search block got automatically enabled
(its not a block, its in the theme)
Both users missed the searchthemeform arriving when enabling search.
Go to blocks anyway.
(it's both)
still does not see the search box from the theme
has no idea why search does not work
a bit confused about why he's getting no search results
no clue why search is not working after enabling
maybe the content is not searchable
maybe need to configure something else
goes to admin search
When something doesn't work, knows he might need to set something else up (permissions, settings etc.)
realizes site has not been indexed yet
reindex site clicks on it .. thinking like it will reindex website
ISSUE: ^
ISSUE: reindex is a verb.
refresh page.. still not indexed
^true
ISSUE: when search is enabled and 0% of site is indexed, warn user.
no clue how it will read information to make its index
Knows what cron is.
maybe index site when search is enabled?
runs cron manually
ISSUE: cron is not enabled and yet there are no errors or warnings on the status report
Used the dsm() to check that cron worked.

TASK 12

realizes it's likely a module
(if we are going to say that you need the path module, we should say that you need the trigger module)
Looking in logging and alerts for e-mail notifications.
thinks it would be under "logging errors and alerts"
I don't think we should say path module. but we can have that discussion later.
Looking at update status next.
beeradb: agreed
looking at modules page now
looking at modules list for a long time. hoping for a keyword to jump out
"content", "notification", "email", "alert".. looking for any of them
wonders if it is "tracker"... skip right over trigger
ISSUE: cannot find configuration options for newly enabled module
sees trigger
enables trigger!
Finds trigger after ruling out tracker.
interesting to note (not in any way related to this task), he does not use the firefox search... that was dries argument against the built in search to the perms page
^I would love to have an ajax search on perms page .... like as in cpanel
ISSUE: trigger UI sux
ISSUE: chose publish post - not creating.
finds the configuratble action
ISSUE: cannot send email on saving new post or updating post even though you can do it on each trigger separately
he is more of an end user vs a site admin
Used to setting up sites for himself, not setting it up for other people.
noticed vertical tabs!
doesnt seem too impressed.. but he did notice them "it makes sense"
"trying to remember how it looked before, looking at it now "it makes sense""