A document has been updated:

http://cocoon.zones.apache.org/daisy/cocooninaction/677.html

Document ID: 677
Branch: main
Language: default
Name: The first pages (unchanged)
Document Type: Simple Document (unchanged)
Updated on: 8/18/05 2:49:43 PM
Updated by: Helma van der Linden

A new version has been created, state: draft

Parts
=====
Content
-------
This part has been updated.
Mime type: text/xml (unchanged)
File name:  (unchanged)
Size: 9139 bytes (previous version: 6935 bytes)
Content diff:
(137 equal lines skipped)
    
    <h3>Output</h3>
    
--- <p>We want the final output to be valid XHTML 1.0 Transitional. All CSS used
--- should be valid as well.</p>
+++ <p>We want the final output to be valid XHTML 1.0 Transitional. Layout is 
done
+++ through CSS in separate CSS files, inline styles are only used for 
occasional
+++ exceptions. All CSS used should be valid as well.</p>
    
    <h3>Directory structure vs URL structure</h3>
    
(7 equal lines skipped)
    flat structure with all pages at the same level. If we add the language to 
the
    URL, it is flexible enough to directly point to the appropriate page.</p>
    
+++ <p>Cocoon's sitemap allows you to map any directory structure to any URL
+++ structure, which gives you the opportunity to create a directory structure 
that
+++ is more geared towards the developer. This is a structure that works for 
me:</p>
+++ 
+++ <pre>/webapproot             -- the toplevel of your webapp
+++    /content             -- holds all files that contain the actual content 
(in text)
+++       /images           -- holds context-related images, e.g. a photo 
gallery of a special event
+++ 
+++    /resources           -- holds all resources, such as images, css files, 
clientside javascripts
+++       /img              -- holds "static" images such as logo, layout 
supporting images etc.
+++       /css              -- holds the necessary CSS files
+++       /js               -- clientside scripts
+++ 
+++    /system              -- system files, i.e. files necessary to Cocoon to 
render the proper output
+++       /scripts          -- serverside (flow) scripts (if necessary)
+++       /forms            -- Cocoon forms (if necessary)
+++       /xsl              -- XSLT files that transform your content into 
XHTML pages</pre>
+++ 
    <h2>Let's get to work</h2>
    
--- <p>Now that decisions are made,</p>
+++ <p>Now that decisions are made, it is time to put it all to work. First, 
fire up
+++ Eclipse, open your <em>HealthyCocoon </em>project and create the directory
+++ structure as outlined above under <em>/src/cocoon/webapp/healthycocoon</em> 
of
+++ your project. Note that <em>healthycocoon </em>is the "root" directory under
+++ <em>webapp</em> and thus <em>webapproot </em>in the description above. This
+++ makes your project a subproject of the Cocoon webapp. This way, the project
+++ sitemap can remain small. The "root" sitemap (i.e. the default sitemap 
installed
+++ during the installation of Cocoon) remains untouched and provides a default
+++ setup for most definitions and URLs.</p>
    
+++ <p>[TODO:<br/>
+++ - create home page<br/>
+++ - create contact page<br/>
+++ - create xsl files that transform the xml<br/>
+++ - explain about pipelines (enough to understand why there are different xsl
+++ files)<br/>
+++ - create a minor sitemap.xmap<br/>
+++ - run cocoon -&gt; test (only 2 pages, no menu, no language switch, only 
through
+++ URL modification)<br/>
+++ ]</p>
+++ 
    </body>
    </html>


Fields
======
no changes

Links
=====
no changes

Custom Fields
=============
no changes

Collections
===========
no changes

Reply via email to