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
