Re: [Fwd: Creating new pages with Wyona]

Although the Hello World Tutorial proposed by Markus would be a very helpful
learning tool, I'm finding myself to be more interested in the sample pub
proposed by Felix and outlined by Markus, simply because it is more
complete.  I am wondering if the OSCOM example pub doesn't already meet
these criteria?  If not, what is it lacking, or if it isn't lacking
anything, then what more complex feature does it include that disqualifies
it as an appropriately "simple" example?

I have some specific questions about the example below.
    a.. 3.2 the example (as proposed by Felix)
      a.. Simple layout
      b.. One simple document type
        a.. (title, subtitles, paragraphs, images, maybe a list)
        b.. which is editable through Xopus and Bitflux
      c.. - A basic navigation
      d.. Possibility to upload images
      e.. Possibility to create new pages
      f.. Possibility to publish pages
      g.. Basic access controlling with one user/one role/one policy
      h.. 3.2.1 play around with the example
               (just click and see)
      i.. 3.2.2 the example explained
               (what happens in which part)
Can everything above be accomplished using the current examples included
with wyona, such as the OSCOM pub?
      a.. 3.2.3 your own publication
               (copy the example 3.2)
      b.. 3.2.4 change the layout
What are the steps required for changing the layout?  Which files need to be
edited?
      a.. 3.2.5 add new elements
Does this mean add new elements to one of the existing doctypes?  What does
"element" mean here?
      a.. 3.2.6 add a new doctype
Which files need to be edited in order to add a new doctype?  Also, I have
been wondering, has anyone considered the possibility of creating a browser
based tool for adding/editing doctypes and/or manipulating schemas?  Ideally
such a schema editing tool would be usable by folks with little technical
skill or knowledge of XML, this is a person who just wants to be able to
create a new publication with a different set of doctypes, possibly chosen
from a variety of predefined doctypes.

The reason I make such a suggestion is that perhaps the reason people aren't
just taking the examples included with wyona and running with them is that
they find the structure of the included pubs doesn't fit with the intended
structure of their personal project.  When they go to alter the structure,
they find they need a solid grounding in XML, XSLT and Cocoon, which will
scare away all but those who already consider themselves to be developers.
This is fine as long as you only want developers testing wyona, but if you
want to grab other slightly less technical folks, you might want to find
ways to automate to some degree those tasks which would normally be
considered "developer" tasks.  This just involves anticipating common
document structures and giving the integrator a menu-driven choice between
them, so to speak.

If you think such a thing might be possible/desirable, I'd love to hear your
thoughts, particularly if you feel you have a grasp on some of the technical
challenges that might be involved in attempting to implement it, for I don't
really know what would be involved at this point.
      a.. 3.2.7 extend the access rights
Which files need to be edited in order to extend the access rights?  Would
it be possible to create a browser based tool for managing access rights
(similar to the schema/doctype suggestion above)?
      a.. 3.2.8 more sophisticated navigation
Which files need to be edited in order to alter the navigation
functionality?
      a.. 3.2.9 more sophisticacted file upload
Is file upload already included in one of the current pub examples?
      a.. 3.2.10 add the sheduler
Does one of the current pub examples include a scheduler?

Thanks,
Jason