AW: Re: [Wyonacms-users] [Fwd: Creating new pages with Wyona]

Hi all,

let's do it!

Alex McLintock was the first one to suggest to use a "real" site. I would love to make target-x.com Open Source. until now I used the ethz-mat Pub as basic for Target-x. This weekend I wanted to write the tutorial "Database reporting with ESQL and FO", but for that I had to change my pub again. I wanted to switch to OSCOM but I had heaps of problems.

The new pub should use an xconf file that contains all the properties of the page (e.g. <name>tarGET-X.com</name> <motto>find instead of looking</motto> <pagebackground>#000000</pagebackground>...). That way you can edit it with e.g Xopus2. 

NO xml code or cocoon sitemap hacking for the user!!!!!

The NEW pub should have this "basic" components (the focus is to "add" (activate) a Database to wyona):
- db2xml and back
- fo, Reporting from DB with fo
- XML search engine
- Link - engine (like php nuke <- add Links and after Revision put them live)(DB based <- with e.g. HSQL)
- guestbook (DB based <- with e.g. HSQL)
- Forum (DB based <- with e.g. HSQL)
- Tutorials how we did all that with Wyona and other cocoon tutorials


My plan is do follow this steps to get started:
>>1) static HTML Hello World (only Cocoon)
>>2) XML, XSLT Hello World (only Cocoon)
>>3) Adding the Wyona Toolbar
>>4) Making the Hello World editable with Xopus and Bitflux
>>5) Making the Hello World publishable
>>6) Making the Hello World creatable (Hello Pluto, Hello Neptun, etc.)
>>7) Adding Access Controlling to the Hello World


What do you think?

King regards!

-----Ursprüngliche Nachricht-----
Von: Markus Vaterlaus [mailto:[email protected]]
Gesendet: Freitag, 25. Oktober 2002 22:11
An: [email protected]
Cc: [email protected]
Betreff: [Wyonacms-dev] Re: [Wyonacms-users] [Fwd: Creating new pages
with Wyona]


Hi all,

Am 25.10.2002 12:06 Uhr +0200 uebermittelte Felix Maeder folgende Zeilen:
>>I have been talking to Markus Vaterlaus about this topic and I 
>>suggested something like a "Hello World" in ten steps:
>>
>>1) static HTML Hello World (only Cocoon)
>>2) XML, XSLT Hello World (only Cocoon)
>>3) Adding the Wyona Toolbar
>>4) Making the Hello World editable with Xopus and Bitflux
>>5) Making the Hello World publishable
>>6) Making the Hello World creatable (Hello Pluto, Hello Neptun, etc.)
>>7) Adding Access Controlling to the Hello World
>
>
>I don't think this is the best way to go because it takes too long 
>until you actually have a working publication. If you are newbie and 
>are trying out a new product, you want to *see* something very 
>quickly, otherwise you will lose interest pretty soon. I would 
>propose a more result-oriented, less didactic approach:
>
>1. In the distribution there should be a simple "Hello World" publication:
>- Simple layout
>- One simple document type (title, subtitles, paragraphs, images, 
>maybe a list) which is editable through Xopus and Bitflux
>- A basic navigation
>- Possibility to upload images
>- Possibility to create new pages
>- Possibility to publish pages
>- Basic access controlling with one user/one role/one policy

I agree with the idea of Felix. Most User quickly want to see 
results, otherwise he will drop wyona and head for another solution. 
And actually Wyona doesn't offer a satisfying and easy way for the 
first steps.

Therefore I propose that we'll take his idea as point 8 of the list 
above. Steps 1 to 7 are providing some basic information intended to 
give the newbie better understanding about wyona and the related 
technology. Step 8 is provided as working example (!) and offers a 
good description (comments all over the code...). The following steps 
as proposed by Felix are taking place within this example.

For me, the important thing seems, that this example should fullfill 
2 purposes:
- starting point for the more savy newbie (does know CMS and XML/XSLT).
   he can start right away with a new sample publication
- starting point for the newbie (might know something about CMS or XML/XSLT)
     - has a working example with which he can play around
        (clicks an sees what happens)
     - if he will carefully read, he can create a new publication <g>

Out of this follows, that there should not be any obligation for an 
user to take steps 1 to 7. However, if he does, he gets a lot of 
valuable information, which will help him to better understand wyona. 
Consolidating all inputs from this list and from the discussion with 
Michi I think a structure like outlined below would be best for the 
support and documentation pages of the project.

1. Documentation
1.1 Good to know
1.1.1 Mailinglists
1.1.2 Cocoon
1.1.3 XML / XSLT
1.1.4 Java
1.2. User Guide
1.2.1 FAQ
1.2.2 The Guide for Users
1.3. Integrator Guide
1.3.1 FAQ
1.3.2 The Guide for Integrators
1.4. Developer Guide
1.4.1 FAQ
1.4.2 The Guide for Developers

2. Klick and see
2.1. Online Tour
2.2. Demo Applications

3. Tutorials
3.1 the basics
3.1.1 static HTML Hello World (only Cocoon)
3.1.2 XML, XSLT Hello World (only Cocoon)
3.1.3 Structure in Wyona (files, directories et cetera)
3.1.4 Adding the Wyona Toolbar
3.1.5 Making the Hello World editable with Xopus and Bitflux
3.1.6 Making the Hello World publishable
3.1.7 Making the Hello World creatable (Hello Pluto, Hello Neptun, etc.)
3.1.8 Adding Access Controlling to the Hello World
3.2 the example (as proposed by Felix)
       - Simple layout
       - One simple document type
         (title, subtitles, paragraphs, images, maybe a list)
         which is editable through Xopus and Bitflux
        - A basic navigation
        - Possibility to upload images
        - Possibility to create new pages
        - Possibility to publish pages
        - Basic access controlling with
          one user/one role/one policy
3.2.1 play around with the example
         (just click and see)
3.2.2 the example explained
         (what happens in which part)
3.2.3 your own publication
         (copy the example 3.2)
3.2.4 change the layout
3.2.5 add new elements
3.2.6 add a new doctype
3.2.7 extend the access rights
3.2.8 more sophisticated navigation
3.2.9 more sophisticacted file upload
3.2.10 add the sheduler

I hope all this is not too much theory...

--mv

>2. Make your own publication: Copy the Hello world example and adopt 
>the URI space (sitemap).
>
>3. Change the layout: Make a few changes to the XSLT to see how easy 
>it is to adopt the layout.
>
>3. Add some elements to the existing doctype: Change the sample xml, 
>the schema, the xslt, the Xopus- and Bitflux-specific stuff
>
>4. Add a new doctype: sitemap, xml, xslt, editors, creator, 
>publisher, menus, ...
>
>5. Extend the access controlling: users, roles, policies
>
>6. Create a more sophisticated navigation
>
>7. Add a more sophisticated file upload
>
>8. Implement the scheduler
>
>
>--felix
>
>
>_______________________________________________
>WyonaCMS-users mailing list
>[email protected]
>http://mail.wyona.org/cgi-bin/mailman/listinfo/wyonacms-users


-- 
**************************************

Unglaublich, aber wahr: Dilbert lebt!

**************************************

_______________________________________________
WyonaCMS-dev mailing list
[email protected]
http://mail.wyona.org/cgi-bin/mailman/listinfo/wyonacms-dev