Send fluid-work mailing list submissions to
[email protected]
To subscribe or unsubscribe via the World Wide Web, visit
http://fluidproject.org/mailman/listinfo/fluid-work
or, via email, send a message with subject or body 'help' to
[email protected]
You can reach the person managing the list at
[email protected]
When replying, please edit your Subject line so it is more specific
than "Re: Contents of fluid-work digest..."
Today's Topics:
1. RE: UX Toolkit. What? (Moore, Kathleen E)
2. Re: UX Toolkit. What? (Jacob Farber)
----------------------------------------------------------------------
Message: 1
Date: Thu, 29 Jan 2009 16:31:22 -0500
From: "Moore, Kathleen E" <[email protected]>
Subject: RE: UX Toolkit. What?
To: "Eli Cochran" <[email protected]>, "Jess Mitchell"
<[email protected]>
Cc: fluid-work List <[email protected]>
Message-ID: <[email protected]>
Content-Type: text/plain; charset="us-ascii"
I share that reaction.
Kathy
Kathleen Moore
Web Manager
Boston University School of Management
[email protected]
617-353-2685
From: [email protected]
[mailto:[email protected]] On Behalf Of Eli Cochran
Sent: Thursday, January 29, 2009 4:24 PM
To: Jess Mitchell
Cc: fluid-work List
Subject: Re: UX Toolkit. What?
My concern is that "Handbook" doesn't seem to encompass the
"resources"
aspect.
- Eli
On Jan 29, 2009, at 12:24 PM, Jess Mitchell wrote:
What about a Design Handbook that contains guidelines and resources
and
how tos, etc.? Is the former a name and the latter an explanation of
the contents?
And does the former capture enough of what you'd expect to see
inside in
a pithy and catchy name?
Let's let this soak for a day and see what other suggestions we get...
J
~~~~~~~~~~~~~~~~~~~~~~
Jess Mitchell
Boston, MA, USA
Project Manager / Fluid Project
[email protected]
/ w / 617.326.7753 / c / 919.599.5378
jabber: [email protected]
http://www.fluidproject.org
~~~~~~~~~~~~~~~~~~~~~~
On Jan 29, 2009, at 3:04 PM, Eli Cochran wrote:
+1 for Design Guidelines and Resources
Being less ambiguous is better since this is clearly one of those
areas
where we're touching on some terminology which is used by different
people in different ways.
- Eli
On Jan 29, 2009, at 11:38 AM, Daphne Ogle wrote:
I agree that "Design" is better than designer's since it leaves it
more
open.
I have one more to add to the list: Design Toolbox
Although as I write it I'm not sure it encompasses the best
practices & guidelines aspect?
I'm leaning toward: Design guidelines and resources
-Daphne
On Jan 29, 2009, at 11:00 AM, Anastasia Cheetham wrote:
I always wondered about the use of the word "toolkit" in
this case, since what we're talking about seems (to me, at least) to
actually include more than just tools. There is also a lot of
education,
guidelines, best practices, etc., in addition to the actual tools. For
this reason, I like "handbook" - I think it covers the broader ground
that we cover.
Regarding "design" versus "designer's," I thought one of
the goals of the <thing> was to provide design help to a wider
audience
than just designers, i.e. to also be useful for developers, etc. For
this reason, I think I prefer "design" to "designer's."
So:
+1 for "Design Handbook"
--
Anastasia Cheetham
[email protected]
Software Designer, Fluid Project
http://fluidproject.org
Adaptive Technology Resource Centre / University of
Toronto
_______________________________________________________
fluid-work mailing list - [email protected]
To unsubscribe, change settings or access archives,
see http://fluidproject.org/mailman/listinfo/fluid-work
Daphne Ogle
Senior Interaction Designer
University of California, Berkeley
Educational Technology Services
[email protected]
cell (510)847-0308
_______________________________________________________
fluid-work mailing list - [email protected]
To unsubscribe, change settings or access archives,
see http://fluidproject.org/mailman/listinfo/fluid-work
. . . . . . . . . . . . . . . . . .
.
Eli Cochran
user interaction developer
ETS, UC Berkeley
_______________________________________________________
fluid-work mailing list - [email protected]
To unsubscribe, change settings or access archives,
see http://fluidproject.org/mailman/listinfo/fluid-work
. . . . . . . . . . . . . . . . . .
.
Eli Cochran
user interaction developer
ETS, UC Berkeley
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://fluidproject.org/pipermail/fluid-work/attachments/20090129/31c92af0/attachment-0001.htm
>
------------------------------
Message: 2
Date: Thu, 29 Jan 2009 17:07:44 -0500
From: Jacob Farber <[email protected]>
Subject: Re: UX Toolkit. What?
To: "Moore, Kathleen E" <[email protected]>
Cc: fluid-work List <[email protected]>
Message-ID:
<[email protected]>
Content-Type: text/plain; charset="iso-8859-1"
I really think the whole point for this discussion, and why a lot of
people
have propped up Design Handbook, is not because of what the title
technically encompasses - its simply because its a name that's
likely to get
the attention of a inquisitive visitor / designer / developer /
whomever and
from there they will get to see what its all about.
The real win would be to get them to take the first step and click
the link
to begin learning, no matter how technically accurate the title may
be.
I really hope this doesn't sound too blunt or heavy handed. I just
think
we're getting to attached to the technicalities behind the name.
Jacob
On Thu, Jan 29, 2009 at 4:31 PM, Moore, Kathleen E <[email protected]>
wrote:
I share that reaction.
Kathy
Kathleen Moore
Web Manager
Boston University School of Management
[email protected]
617-353-2685
*From:* [email protected] [mailto:
[email protected]] *On Behalf Of *Eli Cochran
*Sent:* Thursday, January 29, 2009 4:24 PM
*To:* Jess Mitchell
*Cc:* fluid-work List
*Subject:* Re: UX Toolkit. What?
My concern is that "Handbook" doesn't seem to encompass the
"resources"
aspect.
- Eli
On Jan 29, 2009, at 12:24 PM, Jess Mitchell wrote:
What about a Design Handbook that contains guidelines and resources
and
how tos, etc.? Is the former a name and the latter an explanation
of the
contents?
And does the former capture enough of what you'd expect to see
inside in a
pithy and catchy name?
Let's let this soak for a day and see what other suggestions we
get...
J
~~~~~~~~~~~~~~~~~~~~~~
Jess Mitchell
Boston, MA, USA
Project Manager / Fluid Project
[email protected]
/ w / 617.326.7753 / c / 919.599.5378
jabber: [email protected]
http://www.fluidproject.org
~~~~~~~~~~~~~~~~~~~~~~
On Jan 29, 2009, at 3:04 PM, Eli Cochran wrote:
+1 for Design Guidelines and Resources
Being less ambiguous is better since this is clearly one of those
areas
where we're touching on some terminology which is used by different
people
in different ways.
- Eli
On Jan 29, 2009, at 11:38 AM, Daphne Ogle wrote:
I agree that "Design" is better than designer's since it leaves it
more
open.
I have one more to add to the list: Design Toolbox
Although as I write it I'm not sure it encompasses the best
practices &
guidelines aspect?
I'm leaning toward: Design guidelines and resources
-Daphne
On Jan 29, 2009, at 11:00 AM, Anastasia Cheetham wrote:
I always wondered about the use of the word "toolkit" in this case,
since what we're talking about seems (to me, at least) to actually
include
more than just tools. There is also a lot of education, guidelines,
best
practices, etc., in addition to the actual tools. For this reason,
I like
"handbook" - I think it covers the broader ground that we cover.
Regarding "design" versus "designer's," I thought one of the goals of
the <thing> was to provide design help to a wider audience than just
designers, i.e. to also be useful for developers, etc. For this
reason, I
think I prefer "design" to "designer's."
So:
+1 for "Design Handbook"
--
Anastasia Cheetham [email protected]
Software Designer, Fluid Project http://fluidproject.org
Adaptive Technology Resource Centre / University of Toronto
_______________________________________________________
fluid-work mailing list - [email protected]
To unsubscribe, change settings or access archives,
see http://fluidproject.org/mailman/listinfo/fluid-work
Daphne Ogle
Senior Interaction Designer
University of California, Berkeley
Educational Technology Services
[email protected]
cell (510)847-0308
_______________________________________________________
fluid-work mailing list - [email protected]
To unsubscribe, change settings or access archives,
see http://fluidproject.org/mailman/listinfo/fluid-work
. . . . . . . . . . . . . . . . . .
.
Eli Cochran
user interaction developer
ETS, UC Berkeley
_______________________________________________________
fluid-work mailing list - [email protected]
To unsubscribe, change settings or access archives,
see http://fluidproject.org/mailman/listinfo/fluid-work
. . . . . . . . . . . . . . . . . .
.
Eli Cochran
user interaction developer
ETS, UC Berkeley
_______________________________________________________
fluid-work mailing list - [email protected]
To unsubscribe, change settings or access archives,
see http://fluidproject.org/mailman/listinfo/fluid-work
--
Jacob Farber
University of Toronto - ATRC
Tel: (416) 946-3002
www.fluidproject.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://fluidproject.org/pipermail/fluid-work/attachments/20090129/8826688d/attachment.htm
>
------------------------------
___________________________________________________
fluid-work mailing list [email protected]
To unsubscribe, change settings or access archives,
see http://fluidproject.org/mailman/listinfo/fluid-work
End of fluid-work Digest, Vol 23, Issue 71
******************************************
