Re: [Fwd: Creating new pages with Wyona]
Markus Vaterlaus <[email protected]> Tue, 29 Oct 2002 22:25:56 +0100
| Newsgroups | gmane.comp.cms.wyona.user |
|---|---|
| Message-ID | <p05111b03b9e4164c66d2@[192.168.1.4]> |
Am 26.10.2002 19:08 Uhr -0700 uebermittelte Jason Wehmhoener folgende Zeilen: Hello Jason, hi all, >I think Markus's suggestion is the best plan yet, and I'd be happy >to help out in any way I can, though as a newbie I'm mostly looking >forward to reading it. > First of all, grazie dei fiori as the italians say. Second, by just comparing my structure with some recent posts on the list, I see that there is something missing: The Set-Up / Installation Part. I'll add it to the structure below. >I'm wondering if it might be beneficial to take some time to more >clearly define the Editor, Integrator and Developer roles, and >consider the needs of those roles throughout the tutorials? I feel >that in order to understand the current tutorials I need to wear all >three hats. > Yes, I agree with you, in the actual documentation you have to wear a lot of hats. However from my point of view, the tutorials have to be made for integrators (I consider the role "user" as someone creating/editing contents and a integrator as somebody setting up the system that the user will use) and perhaps developers too. The aim of these tutorials are easy to understand guides, enabling these people to quickly get first hand experience. For the user (an other roles like the manager, the goldkeeper et cetera) the online tour and the demo applications are more appropriate places becauase they require less resources and time to get an first impression about wyona. >I agree that you want to "set the hook" as quickly as possible by >allowing people to build their own customized sites with wyona in a >snap. Basically, I imagine that an Integrator should be able to >download Wyona, customize a pub written by a Developer that is part >of the Wyona team, and deploy it to their editors. I agree completly. In other words, the integrator should be able to adopt an existing publication and doesn't need the skills of a programmer. he will do fine with his Knowledge of XML/XSLT and HTML. Greetings Markus > Many many many non-profits and other small organizations have >access to people of Integrator-level technical skill, but no access >to Developers. > >Thanks, >Jason Wehmhoener > >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 1.5 Installation / Set-Up 1.5.1 Installing Tomcat 1.5.1.1 Windows 1.5.1.2 Mac OS X 1.5.1.3 Linux 1.5.1.4 Further References 1.5.1.5 Using another application server 1.5.2 Installing Wyona 1.5.2.1 Beginner Snapshot 1.5.2.2 Advanced Snapshot 1.5.2.3 Dev w/CVS 1.5.2.4 Further References 1.5.3 Advandced Set Up 1.5.3.1 Tricks with Cocoon 1.5.3.2 Integrating Cocoon with Apache >2. click 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 -- ************************************** Unglaublich, aber wahr: Dilbert lebt! **************************************