Wishlist wyona brainstorming

Roger Stupf <[email protected]>
Newsgroups gmane.comp.cms.wyona.devel
Message-ID <BA52BAFF.2DA5%[email protected]>
Dear list members

I take Markus' thoughts (see below) as an occasion to post my wishlist for
the wyona brainstorming day tomorrow...

Documentation/FAQ
^^^^^^^^^^^^^^^^^
I know it's not a very appealing subject for developers, but I think that
deepening and re-organizing the documentation would really help (potential)
users and admins.
- deepening: Quite a lot of the doucmentation is empty or the links lead to
the sentence "to be documented soon". Putting real content there would make
people's decision to actually use wyona CMS a bit easier.
- re-organizing: Maybe it's better to reduce the 4 sections
(user/admin/integrator/developer) to 3 sections (by either combining
user&admin or admin&integrator). This would help people like me who are on
the one hand user and on the other hand amdin or integrator finding the
documentation of a specific topic.
- re-organization II:
BTW: The user guide begins with the not very encouring topic "strange
effects". Maybe one could replace this by a FAQ (including e.g. the hint to
install MS-XML on windows).

Publications & CVS
^^^^^^^^^^^^^^^^^^
unipublic is AFAIK the first real-life publication using wyona cms. It would
be good to distinguish in future between "sample publications" and "my
publications" (on the document structure level and for the CVS).

Content Management: OpenOffice vs. webbased XML Editor
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
I like Julian's and Markus' idea of using OpenOffice to edit content, WebDAV
to access it and wyona CMS to manage it. This is certainly a way to go
especially for the migration of content from "office-products" islands to
the open conintent of everybody-accessible content.
But I think the future way to edit content would be using an web-based
WYSIWYG Editor (like Bitfluxeditor or Xopus) to really go into the direction
of the vision "the web is the content". To achieve this, these editor have
to involve into a direction where the have the same ease-of-use as
OpenOffice.

Link Management
^^^^^^^^^^^^^^^
One thing I am missing at the moment is a visual tool to easily create
"internal" links, i.e. links withing the documents of my publications. What
I have in mind is something like "point and shoot" in Golive. This would of
course include the automatic link actualisation if the target moves or is
renamed.

User Admin and Workflow
^^^^^^^^^^^^^^^^^^^^^^^
An easy-to-use visual tool (GUI) for user administration and the definition
of a worfklow are essential tools for an CMS admin that would improve the
acceptance of wyona CMS.


A last remark: I know wishing is easy and it's a big wish list.  And I know
that you all do a great job in improving wyona CMS. I just took this
opportunity to express the demands of an actual user of wyona CMS.

Good brainstorming tomorrow for the wyona team!

Roger

> 
> Am Freitag, 10.01.03 um 18:21 Uhr schrieb Julian Klein:
> 
>>> do you have any slide-specific wishes for wyona?
>>> 
>>> -gregor
>> 
>> My wish list for all this is that the revision
>> controls, ACL, locking capabilities of slide are used
>> for Lenya/Wyona since they seem to be very mature.
>> Again it makes no sense to put effort into rewriting
>> all these tools when they are freely available.  This
>> way one could use more than WYSIWYG editors like
>> XMLSpy, OpenOffice, etc in order to manage distributed
>> content.  Also, it would be great if the content store
>> was WEBDAV and DELTA-V conformant.  Moreover,
>> Wyona/Lenya could focus more on higher end CMS
>> functions (i.e. the scheduler, entity-based workflow)
>> all while cleaning the class library.  Again,
>> questions, comments appreciated.
>> 
> 
> Hi Julian, hi list,
> 
> scanning trough my mailboxes to get a hint about an actual problem, I
> stumbled across this message. Not the solution for my problem but quite
> a resemblance to some thought I had during the last days. Therefore I
> second Julian's opinion about the next steps to be taken: Concentrate
> on content management and enhance this functionality by integrating
> supporting technologies and improving the easiness of creating content.
> Or put it another way around: Wyona serves as a content management
> framework residing on top of a XML Framework (cocoon); therefore we
> have the glue, now we need to pick the best pieces and bring them
> together. And, if at last all of it is manageable trough a nice and
> sophisticated GUI, it would be a killerapp...
> 
> Why I'm so enthusiastic? (Am I?) Well... The whole day I was thinking
> about the dead lock of content editing and storage at companies. Most
> of the content produced is locked in a proprietary  format (a hint:
> word), and in most cases if you want to do something with it's
> contents, you will be firing up an office application even, if you only
> need a little snippet of that large text. On the other hand another
> problem in my opinion is , that all these files are stored in a
> filesystem. And the usual filesystems won't provide much information
> about the file and it's contents except from the "properties". Finding
> a file with a desired content can become tremendous... Furthermore the
> stored files are lacking features like versioning or rollback.
> 
> I know, that already others have encountered this problems. And, I also
> know, that there are commercial solutions on the market (thinking of
> document management systems like documentum). However, I don't know
> nothing about an OS Solution solving this problems. Wasn't there a need
> till now? I'm just wondering, if there wasn't the need to write
> documents longer than just a couple of paragraphs? What about different
> people beeing involved in the process of writing? What about using this
> contents in different channels? et cetera... There are thousands of OS
> solutions available to do a lot of things with Web content, but none
> able to deal with "Office" content.
> 
> That's why Julian's input seems so appealing to me: editing the content
> with something like OpenOffice, mange it with the help of Wyona
> (workflow, access rights and the like) and publish it trough the
> underlying cocoon-layer. Let me know, if I'm thinking to far or / and
> what you thoughts on this subject are.
> 
> Markus
> 
>> -Julian
>> 
>> __________________________________________________
>> Do you Yahoo!?
>> Yahoo! Mail Plus - Powerful. Affordable. Sign up now.
>> http://mailplus.yahoo.com
>> 
>> _______________________________________________
>> WyonaCMS-dev mailing list
>> [email protected]
>> http://mail.wyona.org/cgi-bin/mailman/listinfo/wyonacms-dev
>> 
> 
> 
> _______________________________________________
> WyonaCMS-dev mailing list
> [email protected]
> http://mail.wyona.org/cgi-bin/mailman/listinfo/wyonacms-dev
> 

--------------------------------------
Universität Zürich
unicommuniation
Roger Stupf, Leiter Weboffice

Schönberggasse 15a
8001 Zürich
Tel +41 1 634 44 17
Fax +41 1 634 23 46
[email protected]
http://www.unicom.unizh.ch
--------------------------------------
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.