wiki re-org (Re: How to organize the reorderer family on the wiki?)

Jess Mitchell jess at jessmitchell.com
Fri Sep 12 14:42:23 UTC 2008


Just to clarify, I erroneously said below that Daphne was doing the  
template for the design top-level pages.  I talked to Daphne about  
this earlier this week and it was enough to throw me off.  FLUID 1133  
assigned to Erin starts to get at this work...

Best,
Jess

~~~~~~~~~~~~~~~~~~~~~~
Jess Mitchell
Boston, MA, USA
Project Manager / Fluid Project
jess at jessmitchell.com
/ w / 617.326.7753  / c / 919.599.5378
jabber: jessmitchell at gmail.com
http://www.fluidproject.org
~~~~~~~~~~~~~~~~~~~~~~




On Sep 11, 2008, at 9:47 AM, Jess Mitchell wrote:

> So, what I'm hearing is the following:
>
> Jonathan (all a's) volunteering to take on a clean-up of the  
> Components page http://wiki.fluidproject.org/display/fluid/Components
> Erin working on a template for the individual component's top level  
> page
> and
> Daphne working on an easy template for the design top-level page
>
> So, something like the following would happen hierarchically:
> Components (all of them) landing page with representation of  
> families and little text but with clickable screen shots that take  
> you to the
> 	Individual Component landing page
> 		Individual Component Design top-level page.
>
> Is that accurate?
>
> best,
> jess
>
> ~~~~~~~~~~~~~~~~~~~~~~
> Jess Mitchell
> Boston, MA, USA
> Project Manager / Fluid Project
> jess at jessmitchell.com
> / w / 617.326.7753  / c / 919.599.5378
> jabber: jessmitchell at gmail.com
> http://www.fluidproject.org
> ~~~~~~~~~~~~~~~~~~~~~~
>
>
>
>
> On Sep 11, 2008, at 9:16 AM, Jonathan Hung wrote:
>
>> I agree that we should group pages together that belong in a  
>> family. However, I'm cool on the idea of adding yet another layer  
>> on top of existing component pages.
>>
>> One idea would be to show the relationships in a hierarchy on the  
>> Components index page (http://wiki.fluidproject.org/display/fluid/Components 
>> ). At the same time, make it clear on a component child page that  
>> it belongs to a larger family of components. This could be  
>> reinforced through a side panel again indicating the hierarchy /  
>> relationships with components.
>>
>> Thoughts?
>>
>> - Jonathan.
>>
>> PS. I've noticed my name is being typoed in the email address line.  
>> There is no "o" in my name, a's all the way! :)
>>
>> ---
>> Jonathan Hung / jonathan.hung at utoronto.ca
>> University of Toronto - ATRC
>> Tel: (416) 946-3002
>>
>>
>> On Wed, Sep 10, 2008 at 11:07 AM, Jess Mitchell <jess at jessmitchell.com 
>> > wrote:
>> Good point Daphne and thanks for bringing this up!
>>
>> My feeling is that we really need to take on the burden of making  
>> sense of these families and parents for folks.  And I can imagine  
>> that one page that introduces the components (like Erin's landing  
>> page for components) that also demarcates the differences among  
>> family member and their relationship would be a good start to  
>> getting these three together.
>>
>> Does any of what I just typed make sense?!
>>
>> Woah,
>> Jess
>>
>>
>> ~~~~~~~~~~~~~~~~~~~~~~
>> Jess Mitchell
>> Boston, MA, USA
>> Project Manager / Fluid Project
>> jess at jessmitchell.com
>> / w / 617.326.7753  / c / 919.599.5378
>> jabber: jessmitchell at gmail.com
>> http://www.fluidproject.org
>> ~~~~~~~~~~~~~~~~~~~~~~
>>
>>
>>
>>
>> On Sep 9, 2008, at 8:44 PM, Daphne Ogle wrote:
>>
>>> As a follow up to the previous email about naming the reorderer  
>>> family...
>>>
>>> What comes next is how it should be organized on the wiki.  Inline  
>>> edit currently has the whole family in one design space:
>>> http://wiki.fluidproject.org/display/fluid/Inline+Edit
>>>
>>> but the reorder family is split and the parent and each child has  
>>> their own design space:
>>> http://wiki.fluidproject.org/display/fluid/Reorderer
>>> http://wiki.fluidproject.org/display/fluid/Layout+Customizer
>>> http://wiki.fluidproject.org/display/fluid/Lightbox
>>>
>>> There are definitely benefits to both (In the meantime, I'm going  
>>> to just create some child pages in the lightbox space so I can  
>>> move forward).
>>>
>>> It seems like the children should at least be connected but  
>>> perhaps having them all in one space is overload?
>>>
>>> Daphne Ogle
>>> Senior Interaction Designer
>>> University of California, Berkeley
>>> Educational Technology Services
>>> daphne at media.berkeley.edu
>>> cell (510)847-0308
>>>
>>>
>>>
>>
>>
>
> _______________________________________________
> fluid-work mailing list
> fluid-work at fluidproject.org
> http://fluidproject.org/mailman/listinfo/fluid-work

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://fluidproject.org/pipermail/fluid-work/attachments/20080912/66cbcdde/attachment.html>


More information about the fluid-work mailing list