Re: Getting Started With WO site
Re: Getting Started With WO site
- Subject: Re: Getting Started With WO site
- From: Chuck Hill <email@hidden>
- Date: Mon, 18 Jun 2007 22:45:06 -0700
On Jun 18, 2007, at 10:30 PM, Q wrote:
On 19/06/2007, at 2:02 PM, Chuck Hill wrote:
I am not sure that putting it in the WOCommunity site is the best
idea. I will propose that a top level split is of longer term
value. "spaces" in a Confluence website are somewhat isolated
from each other, but it is still easy to make links between topics
in each.
Agreed, my preference was more for using confluence than the wocom
space in particular.
Rather than have the stuff from the WikiBook jammed into WOCOM,
would it not be more useful to provide something along the lines of:
WOLips - for all things directly related to WOLips and Eclipse usage
Yup, that already exists as the WOL space.
WOCOOM - for community related things, news, plans, associations,
etc.
Wonder - for all things directly related to Project Wonder
YES.
WebObjects - for documentation on WebObjects
WOTutorials - maybe part of WebObjects, maybe a separate space
I don't think these should be separate spaces.
That depends on what goes in them. If the WebObjects one is devoted
to documentation that extends what Apple has in JavaDocs and other
docs, it may make sense to keep tutorial information separate.
I think that having a top level differentiation like that will
make it easier to locate the information that you want and easier
to decide where to place new material.
A logical page structure would also help this. However, search in
confluence is very good, and significantly more useful for finding
things than navigation alone.
A logical page structure would be great, but that requires more
planning and co-ordination than I fear will happen. :-)
Chuck
On Jun 18, 2007, at 6:00 PM, Q wrote:
++1 here. I really dislike trying to use the wiki book, I would
much prefer to see content marshalled into the WOCommunity wiki,
rather than into the wiki book.
If the WOCOM wiki was the official centre of these efforts I
would be much more included to spend time on it.
On 19/06/2007, at 8:45 AM, Chuck Hill wrote:
I also am less than thrilled with the WikiBook:
- the process of adding images is painful
- I am not sure if anything else can be added
- searching just the WO content is either not possible or not clear
- the markup is limited
- no one has control over the backups etc.
I have used Confluence quite a bit and find that to be much
better for documenting technical material.
Chuck
On Jun 14, 2007, at 9:22 AM, Steven Mark McCraw wrote:
Agreed. How do we (and I guess by we I mean everybody on this
list) come to an agreement on the one place that should be the
definitive posting grounds? Honestly, I sometimes find
navigating the wiki book less than ideal, but it's kind of a
minor irritation that I can live with if it solves the problem
of a central repository, and there's so much there already that
it seems like the most logical place to me. Whatever it is, it
should be publicly editable, I think, and it has to be
searchable and individual articles must be linkable. Is
anybody in disagreement that the wiki book is the best place
ongoing to post information? If so, can we start an effort to
shuttle information posted elsewhere into the wiki book if it
is missing? If not, what are alternative suggestions for the
central repository of information?
Thanks,
Mark
On Jun 14, 2007, at 12:10 PM, Dana Kashubeck wrote:
On 6/14/07 11:57 AM, Steven Mark McCraw wrote:
My understanding is that the webobjects wiki book (http://
en.wikibooks.org/wiki/Programming:WebObjects) is trying to
become the central point of documentation for WebObjects that
people post to. There's already a ton of info there, but we
all know it could use a ton more. At WOWODC, when the
experts panel was asked what could be done to help with
project wonder, this is what they came back with
immediately: We need people writing documentation, and this
is the place to put it. Even if it's bad, there are so many
people watching it that bad info will get edited out quickly.
I think there's a danger in having TOO many informational
sites. If everybody decides to wing it because they get on a
high at a developer's conference regarding being able to
document stuff to widen the movement, I think we will end up
with dozens of blogs, half finished tutorials, etc. There's
a reason there isn't much documentation on Wonder and
WebObjects: writing good documentation is HARD and time
consuming, and not a very glamorous task. So if you have 10
spare hours to write a decent article on a very specific
issue, I think everybody would be better served if that went
to the wikibook. That way, everybody can always point to one
resource as definitive.
I don't mean to be preachy about it or rain on anybody's
parade that is putting up yet another site about WebObjects.
What I just wrote might sound snappy or mean, but I don't
mean it that way. I'm just trying to advocate a central
repository for everything so people don't have to go here and
there to get various pieces of the overall puzzle. Maybe if
you start a site, you could also make sure that all of the
contents of that site are also posted in the wiki book in the
sensible place? Thoughts?
I was thinking the same thing. Last year there were some
really great efforts to put together "the site" for WebObjects
information. I think it was this one: http://
wiki.objectstyle.org/confluence/display/WOCOM/WOCOM
So there's that wiki, the wiki book, www.wocommunity.org,
etc., etc. I completely agree that there is a huge need for
documentation and resources and it is important for the
community to put these things together. But right now
everything just seems *so* scattered! Can those who have been
generous enough with their time please post their content on
one of the already existing sites?
--
-------------------------------------
Dana Kashubeck
Systems Manager
Riemer Reporting Service Inc.
http://www.riemer.com
Phone: 440-835-2477 x. 125
Fax: 440-835-4594
-------------------------------------
<dana.kashubeck.vcf>
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
40global-village.net
This email sent to email@hidden
--
Practical WebObjects - for developers who want to increase their
overall knowledge of WebObjects or who are trying to solve
specific problems.
http://www.global-village.net/products/practical_webobjects
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
40gmail.com
This email sent to email@hidden
--
Seeya...Q
Quinton Dolan - email@hidden
Gold Coast, QLD, Australia
Ph: +61 419 729 806
--
Practical WebObjects - for developers who want to increase their
overall knowledge of WebObjects or who are trying to solve
specific problems.
http://www.global-village.net/products/practical_webobjects
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
40gmail.com
This email sent to email@hidden
--
Seeya...Q
Quinton Dolan - email@hidden
Gold Coast, QLD, Australia
Ph: +61 419 729 806
--
Practical WebObjects - for developers who want to increase their
overall knowledge of WebObjects or who are trying to solve specific
problems.
http://www.global-village.net/products/practical_webobjects
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden