[
Lists Home |
Date Index |
Thread Index
]
That's been my vision as well. The community should be a place to share
ideas, not just post links. In fact, the KB is generally the place to
link to other sources. The KB I think of as an organized set of
resources, many of which are already posted in other places. The
community should be as wiki-like as we can manage with Drupal.
JoAnn
-----Original Message-----
From: Jerry Silver [mailto:jerry.silver@blastradius.com]
Sent: Monday, January 23, 2006 6:46 PM
To: Carol Geyer; dita-fa-edboard@lists.xml.org
Cc: Greg Rundlett
Subject: RE: [dita-fa-edboard] Book versus Story
I've always imagined the Community pages to be Wiki-like, or at least
offering Wiki-style collaboration. That means allowing the community to
post entire articles about Best Practices, Enhancement Ideas, Case
Studies, etc. I'd much rather see living content (and content living)
on the site than turning the site into a collection of links. Of
course, certain types of content (events, news, products and services)
do lend themselves to being links to other content, mostly from vendors
who do have their own virtual soapboxes. But I'd like to see the site
become the location of choice for information that DITA users want to
share with each other.
I haven't questioned this mental model of a Wiki site, and assumed that
other members of the board shared this expectation. What do the rest of
you think?
J.
-----Original Message-----
From: Carol Geyer [mailto:carol.geyer@oasis-open.org]
Sent: Monday, January 23, 2006 11:38 AM
To: Jerry Silver; dita-fa-edboard@lists.xml.org
Cc: 'Greg Rundlett'
Subject: RE: [dita-fa-edboard] Book versus Story
Jerry,
Thanks for raising this issue. I agree, we should be very sure we've
made the correct choice on page formats before we go much further. If
the Board wants to switch, you're right, it's not a big deal for me to
manually make the change now.
I believe we chose "book" for KB and "story" for Community because we
felt the KB pages required more navigation, needed more parent-child
relationships, etc.
My understanding was that (aside from the User Groups, which will be
handled separately) the majority of user interaction with Community
pages will be to input content to existing pages, not to create lots of
new pages. In the few instances where a user does need to create a new
Community page (to post content he/she can't post on an employer's or
personal site), the navigation to the new page would be through links on
the main Community pages. For example, if an individual writes a white
paper on DITA and has no other web site on which to post it, and wants
to post it on XML.org, we would allow him/her to do that, but access to
the new page would be through a linked entry on the "Publications" page
(just like it is for all the external white papers). There wouldn't be a
strong need for the user to employ a structured navigation scheme for
this.
In addition to "story" pages, the Community section will include Forums
where users can exchange information in areas and ways not covered by
the standard Community pages, i.e., info that isn't news, events,
products, etc.
Alternatively, the KB pages are very hierarchical, and the "book"
navigation features are better employed here because we need to lead
readers through the pages easily.
I suspect you're envisioning a use of the Community section that I don't
see yet. Can you explain the use case to me?
Thanks,
Carol
Note: Greg assures me we can use taxonomies to make access to original
Community pages easier; we can ask him to provide details on how to do
that on Thursday's call.
-----Original Message-----
From: Jerry Silver [mailto:jerry.silver@blastradius.com]
Sent: Friday, January 20, 2006 7:15 PM
To: Carol Geyer; dita-fa-edboard@lists.xml.org
Subject: RE: [dita-fa-edboard] Book versus Story
Carol,
I'm curious about the reasons for this decision.
As we discussed at our last meeting, it would have been relatively
little work to manually convert the KB pages from Book to Story (using
cut and paste).
Story pages have no implicit navigation, so we would have to depend on
each Community member to manually create links to the pages they create,
using the cumbersome linking dialog in the editor. The editorial board
can be trained to implement a reasonable set of manual links, but we
can't expect to see much consistency on the community pages. So Stories
would seem to make more sense for the KB, while Books with their
automatic linking model would be a better choice on the Community pages
(although the linking is not very wiki-like).
It's difficult to express my requirements for navigation in the
Community section, other than to say it should be "wiki-like".
Although Drupal offers a lot of functionality, it's not really a wiki.
Wikis make linking very simple - they don't require a pre-defined
taxonomy, and simply generate meaningful links between pages by using a
simple tagging mechanism.
The Drupal freelinking module does implement wiki-style linking -
http://drupal.org/project/freelinking. Freelinking appears to be
compatible with both book and story. There is also a pure wiki module -
http://drupal.org/project/wiki.
Regards,
Jerry
-----Original Message-----
From: Carol Geyer [mailto:carol.geyer@oasis-open.org]
Sent: Friday, January 13, 2006 11:45 AM
To: dita-fa-edboard@lists.xml.org
Subject: [dita-fa-edboard] Book versus Story
In speaking further with Moshe on our requirements, he now advises that
we use "book" for the Knowledge Base pages and "story" for the Community
wiki pages. This will allow us to preserve the navigation we've been
using on the KB pages, and should reduce the need for converting the
majority of the existing KB pages.
If you've created KB pages that aren't in "book" format, and you have
time, please convert them yourselves. (Basically, this involves creating
a new "book" page, copying the content from the old page into the new,
deleting the old, renaming the new.) If you don't have time, I'll try to
do it early next week.
Likewise if you've created Community pages that aren't in "story"
format.
WRT navigation for the Community pages, please send me your
requirements. We'll need to work with Moshe on using Drupal's taxonomy
function for this.
Thanks,
Carol
-----Original Message-----
From: Jerry Silver [mailto:jerry.silver@blastradius.com]
Sent: Thursday, January 12, 2006 3:55 PM
To: Carol Geyer; dita-fa-edboard@lists.xml.org
Subject: RE: [dita-fa-edboard] DITA FA Board Discussions: 12 Jan
I thought we decided we would manually re-create the KB pages, rather
than having Moshe convert them.
We still need guidelines on setting up the navigation for "story" pages,
since they don't have an automatic navigation model like "book" pages.
Moshe is supposed to advise us on this.
J.
-----Original Message-----
From: Carol Geyer [mailto:carol.geyer@oasis-open.org]
Sent: Thursday, January 12, 2006 12:04 PM
To: dita-fa-edboard@lists.xml.org
Subject: [dita-fa-edboard] DITA FA Board Discussions: 12 Jan
We reviewed the technical priority list we compiled last week with Moshe
Weitzman, our Drupal consultant. Status is indicated below.
Per Moshe's recommendation, we've decided that, going forward, the Board
will:
a) Use "story" for new pages we create in the "Knowledge Base" and
"About This Site" sections.
b) Use "book" for new pages in the "Community" section.
Moshe will convert our existing book pages in KB and About to story
pages for us.
Technical Priority Status:
*Primary*
1. Privileges/permissions. Currently, the editorial board can't edit
existing pages. This is appears to be an on again/off again problem, as
some us could edit some pages yesterday.
This is fixed.
2. Left nav links need to be aligned properly. The fixes I requested
yesterday via email will be a big step forward.
Moshe will do this.
3. Database. We need to be sure the database is working properly, i.e.,
it's able to keep track of the pages that we've been adding.
Yesterday, in order to update a page, Jen had to submit it multiple
times until it found an empty node. Apparently, the page was stored at
the end instead of the beginning.
This is fixed.
*Secondary*
4. Graphic design.
Moshe will review the design we have, and let us know if there's any
problem with implementing it.
5. Forms for public input to Community Wiki pages.
There are lots of questions about getting this to work the way we need
it to, especially with regards to displaying items in chronological
order. Jerry will work with Moshe on this.
6. Text editor. Short-term, we can muddle along with what we have now,
but obviously, we need a better solution.
This may be fixed. Please post any additional text editor problems to
the Board list so we can discuss.
7. Formatting inconsistencies across browsers. On IE, the right nav
falls to the bottom of the page. You also can't select text in IE.
The right nav issue will be fixed when Moshe implements our graphic
design. The text selection problem is an IE bug.
*Other*
8. Forum support.
9. User group support--allowing non-editorial board members to create
new pages, post documents, etc.
10. Printing. At least some of us are unable to print pages.
We will deal with these "Other" tasks when the primary and secondary
items are resolved.
Thanks,
Carol
______________________________
Carol Geyer
Director of Communications
OASIS
Voice: +1.978.667.5115 x209
---------------------------------------------------------------------
This publicly archived list is provided by OASIS for the use of the
Editorial Board of the XML.org DITA Focus Area. Subscription and posting
privileges are reserved for members of the Editorial Board; others
should contact communications@oasis-open.org for assistance.
[Un]Subscribe: dita-fa-edboard-[un]subscribe@lists.xml.org
List archives: http://lists.xml.org/archives/dita-fa-edboard
Committee homepage: http://www.oasis-open.org/committees/dita
---------------------------------------------------------------------
This publicly archived list is provided by OASIS for the use of the
Editorial Board of the XML.org DITA Focus Area. Subscription and posting
privileges are reserved for members of the Editorial Board; others
should contact communications@oasis-open.org for assistance.
[Un]Subscribe: dita-fa-edboard-[un]subscribe@lists.xml.org
List archives: http://lists.xml.org/archives/dita-fa-edboard
Committee homepage: http://www.oasis-open.org/committees/dita
---------------------------------------------------------------------
This publicly archived list is provided by OASIS for the use of the
Editorial Board of the XML.org DITA Focus Area. Subscription and posting
privileges are reserved for members of the Editorial Board; others
should contact communications@oasis-open.org for assistance.
[Un]Subscribe: dita-fa-edboard-[un]subscribe@lists.xml.org
List archives: http://lists.xml.org/archives/dita-fa-edboard
Committee homepage: http://www.oasis-open.org/committees/dita
---------------------------------------------------------------------
This publicly archived list is provided by OASIS for the use of the
Editorial Board of the XML.org DITA Focus Area. Subscription and posting
privileges are reserved for members of the Editorial Board; others
should contact communications@oasis-open.org for assistance.
[Un]Subscribe: dita-fa-edboard-[un]subscribe@lists.xml.org
List archives: http://lists.xml.org/archives/dita-fa-edboard
Committee homepage: http://www.oasis-open.org/committees/dita
---------------------------------------------------------------------
This publicly archived list is provided by OASIS for the use of the
Editorial Board of the XML.org DITA Focus Area. Subscription and
posting privileges are reserved for members of the Editorial Board;
others should contact communications@oasis-open.org for assistance.
[Un]Subscribe: dita-fa-edboard-[un]subscribe@lists.xml.org
List archives: http://lists.xml.org/archives/dita-fa-edboard
Committee homepage: http://www.oasis-open.org/committees/dita
|
