Component landing page redesign status?

Daphne Ogle daphne at media.berkeley.edu
Mon Nov 17 18:27:14 UTC 2008


I'm planning to do some organization with inline edit for the summit.   
So I'll take that one on today to get cleaned up.

-Daphne

On Nov 14, 2008, at 12:11 PM, Erin Yu wrote:

> The Uploader would be a good example.
> http://wiki.fluidproject.org/display/fluid/Uploader
>
> Not all components will have the same set of children pages, because
> each one is at a different phase. The Uploader example shows the
> general sections. The design-related contents are summarized in the
> Design Overview page (a sub page of the component landing page).
> Here's the Uploader Design Overview page.
> http://wiki.fluidproject.org/display/fluid/Uploader+Design+Overview
>
> Erin
>
>
> On 14-Nov-08, at 2:47 PM, Anastasia Cheetham wrote:
>
>>
>> On 4-Nov-08, at 5:26 PM, Daphne Ogle wrote:
>>
>>> The question of an exemplar is a good.  Erin, is there one that you
>>> would say is an exemplar to make sure the rest match as closely as
>>> makes sense?
>>
>>
>> Did we ever come to a conclusion on a component landing page that
>> could serve as an exemplar for updating the rest?
>>
>> I'd like to help get all the component pages up to snuff in
>> preparation for the all-hands, and it would be good to know where to
>> look for a reference.
>>
>> -- 
>> Anastasia Cheetham                   a.cheetham at utoronto.ca
>> Software Designer, Fluid Project    http://fluidproject.org
>> Adaptive Technology Resource Centre / University of Toronto
>>
>
> _______________________________________________________
> fluid-work mailing list - fluid-work at fluidproject.org
> 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
daphne at media.berkeley.edu
cell (510)847-0308






More information about the fluid-work mailing list