Index: openacs-4/packages/acs-core-docs/www/eng-standards-filenaming.html =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/eng-standards-filenaming.html,v diff -u -r1.47.2.1 -r1.47.2.2 --- openacs-4/packages/acs-core-docs/www/eng-standards-filenaming.html 21 Aug 2013 10:19:21 -0000 1.47.2.1 +++ openacs-4/packages/acs-core-docs/www/eng-standards-filenaming.html 24 Oct 2014 14:33:53 -0000 1.47.2.2 @@ -178,7 +178,7 @@

For example: 

-set page_content "[ad_header "Page Title"]
+set page_content "Page Title]
 
 <h2>Page Title</h2>
 
@@ -216,15 +216,6 @@
 Local procedures (i.e., procedures defined and used only within one
 page) should be prefixed with "module_" and
 should be used rarely, only when they are exceedingly useful.
-

-All files that prepare HTML to display should end with [ad_footer] or
-[module_footer].  If your module requires its own footer,
-this footer should call ad_footer within it.  Why?  Because when we
-adapt the ACS to a new site, it is often the case that the client will
-want a much fancier display than the ACS standard.  We like to be able to
-edit ad_header (which quite possibly can start a <table>) and
-ad_footer (which may need to end the table started in ad_footer) to
-customize the look and feel of the entire site.
 
Tcl Library Files

 Further standards for Tcl library files are under discussion; we plan to 
 include naming conventions for procs.