[dojo-contributors] 1.1 overload

Nikolai Onken nikolai at nikolaionken.com
Thu May 1 08:23:38 EDT 2008

Get your daily dose of dojo cookies for your high tea or brunch:



On Apr 30, 2008, at 5:49 PM, Shane O'Sullivan wrote:

> Certainly I think that the latest 3 or 4 dojo.cookies on DojoCampus
> should be reflected on the front page, along with a link directly to
> dojocampus.org.  They are far more useful that the forum posts that
> are currently there.
> DojoCampus doesn't currently have a feed of just cookies, but I'm sure
> Pete could fix that.
> Thanks
> Shane
> 2008/4/30 Adam L. Peller <adam at peller.org>:
>> Customer service is an important component to our community -- and  
>> I don't
>> mean to dismiss the importance of what Pete said about respecting the
>> customer in conversations -- but nothing will replace web-based  
>> data.  So
>> we've got a great website, and we've talked about usability tweaks  
>> at DDD.
>> I know about Dylan's awesome links collection, but I just spent 2  
>> minutes on
>> dtk.org and could not find a reference to it.  (It's probably there  
>> -- call
>> me stupid)  Dojo Campus is so awesome, it's hard to understand why it
>> doesn't have space on our home page.  If we can identify the top 5
>> resources, we should make it painfully obvious how to get there and  
>> fix the
>> site.  Thoughts?  Fixing the landing pages and perhaps  
>> restructuring the
>> top-level organization is probably part of the navigation problem,  
>> though
>> that may not be a quick fix.  Is there anything from the usability  
>> study we
>> can use to make quick fixes?
>> -Adam
>> On Wed, Apr 30, 2008 at 11:17 AM, Peter E Higgins <dante at dojotoolkit.org 
>> >
>> wrote:
>>> Hi List,
>>> I wanted to take a second to send out some kind of evangelizing  
>>> news! My
>>> first ever call to arms, as it were.
>>> We're seeing an influx of new users to Dojo for a number of reasons,
>>> and would like to maintain the momentum caused by 1.1 and all the
>>> great improvements it brought. As we bring in new users, I just  
>>> want to
>>> reiterate that *what you say and how you say it matters when we're
>>> talking to new users*.
>>> The goal is to help them adopt Dojo so that they can solve hard
>>> problems for their users. With that, giving support or answering
>>> questions is best served by following the Edward Tufte  mantra of
>>> giving presentations:
>>> Don't "know your audience". Know your *material* and *respect* your
>>> audience.
>>> There are so many great new and exciting resources available, It's
>>> important we take the time to not dismiss "really common"  
>>> questions and
>>> problems people are experiencing, and using our expertise to fill  
>>> the
>>> blanks. There are a number of ways to provide lasting information:
>>> Comments in API pages about best practices, FAQ entries, Campus  
>>> Cookies,
>>> your own blog, Forums, responding to mailing lists, to name a few.
>>> Rather than say, "google this", let us make a conscious effort to  
>>> fill
>>> in these blanks, and provide links to solutions. If A link to a  
>>> solution
>>> isn't available, I urge you to consider writing one.
>>> If there are navigation problems with the website or things aren't
>>> coming up right in Google results, lets figure out ways to fix it.
>>> Dojo Campus in particular provides a powerful way to "store what you
>>> know" so that you don't have to keep re-answering questions.
>>> Campus welcomes all submissions, and is a great place for that  
>>> kind of
>>> "wisdom", links to test pages (most test_*.html files have  
>>> examples of
>>> things people want, just don't know where to look) ...
>>> Remeber to point people to resources like:
>>> http://dojotoolkit.org/key-links
>>> which points to resources like:
>>> http://sitepen.com/labs/guides/?guide=DojoQuickStart
>>> http://api.dojotoolkit.org/
>>> http://dojocampus.org/explorer/
>>>  ^  And in the case of explorer, you can link directly to  
>>> examples, or
>>> even better, Provide an additional demo for inclusion. They are  
>>> small,
>>> concise, easy to write, and do WONDERS for people's understanding  
>>> of the
>>> toolkit.
>>> Just remember, Dojo's potential is only surpassed by it's API  
>>> surface,
>>> and it can be admittedly overwhelming to a beginner. I know we all  
>>> have
>>> very busy schedules and obligations and lives outside of Dojo, but  
>>> your
>>> 'extra mile' to provide _your_ expertise in some aspect of it  
>>> would go a
>>> long way in ensuring the continued success of the toolkit.
>>> Let's get away from knowing how great Dojo is to showing how great  
>>> Dojo
>>> is, and help me back up my claims of Dojo having a very solid,  
>>> friendly,
>>> open community who is always willing to help. heh, "Make me proud".
>>> Thanks for listening, and keep on rockin', everyone!
>>> Regards,
>>> Peter Higgins
>>> _______________________________________________
>>> dojo-contributors mailing list
>>> dojo-contributors at dojotoolkit.org
>>> http://turtle.dojotoolkit.org/mailman/listinfo/dojo-contributors
>> _______________________________________________
>> dojo-contributors mailing list
>> dojo-contributors at dojotoolkit.org
>> http://turtle.dojotoolkit.org/mailman/listinfo/dojo-contributors
> _______________________________________________
> dojo-contributors mailing list
> dojo-contributors at dojotoolkit.org
> http://turtle.dojotoolkit.org/mailman/listinfo/dojo-contributors

More information about the dojo-contributors mailing list