cocoon-docs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From d...@cocoon.apache.org
Subject [Cocoon Wiki] Updated: GT2004Jeremy
Date Thu, 14 Oct 2004 11:05:26 GMT
   Date: 2004-10-14T04:05:25
   Editor: JeremyQuinn <jeremy@apache.org>
   Wiki: Cocoon Wiki
   Page: GT2004Jeremy
   URL: http://wiki.apache.org/cocoon/GT2004Jeremy

   no comment

Change Log:

------------------------------------------------------------------------------
@@ -49,11 +49,14 @@
 == Bugzilla ==
 Bugs can be seen as a rude word to a developer, don't take it personally. You can even subscribe
your client to the bug e-mails. Warn your developers if you do this!
 
-==Going live==
+== Going live ==
 Learn how to use the logging control files. Turn of debug messages and reduce output to a
minimum. Disable dangerous features. Don't run cocoon in a publicly visible way. Get apache
to provide error messages and static assets. Technical errors should still be available to
developers. Automate production environment with an ant task
 
-==Be a good citizen==
+== Be a good citizen ==
 Read the manual, search the wiki and mail list. No one answers a question where the answer
is readily available. If you figure it out by yourself, fix the documentation, either in the
wiki or by providing a patch for the cocoon site.
 
-==Last Words==
+== Last Words ==
 Accept liberal, produce strictly. Put input through tidy etc. Slight mistakes in URLs should
still produce sensible results. Missing request parameters should fall back on defaults. Produce
validated HTML, WAI standards. Don't fight the separation of concerns. Even a sole developer
should separate ruthlessly, you may have to share work or come back to your work after a while.

+
+== Please Contribute ==
+The Slides and notes for the talk can be seen here: CocoonBestPractices. Please contribute
to the suggestions there.

Mime
View raw message