Index: openacs-4/packages/acs-core-docs/www/packages.adp
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/packages.adp,v
diff -u -r1.7 -r1.7.2.1
--- openacs-4/packages/acs-core-docs/www/packages.adp	25 Apr 2018 08:38:28 -0000	1.7
+++ openacs-4/packages/acs-core-docs/www/packages.adp	2 Mar 2019 19:30:05 -0000	1.7.2.1
@@ -1,5 +1,5 @@
 
-<property name="context">{/doc/acs-core-docs {ACS Core Documentation}} {OpenACS Packages}</property>
+<property name="context">{/doc/acs-core-docs/ {ACS Core Documentation}} {OpenACS Packages}</property>
 <property name="doc(title)">OpenACS Packages</property>
 <master>
 <include src="/packages/acs-core-docs/lib/navheader"
@@ -9,7 +9,10 @@
 			rightLink="objects" rightLabel="Next">
 		    <div class="sect1">
 <div class="titlepage"><div><div><h2 class="title" style="clear: both">
-<a name="packages" id="packages"></a>OpenACS Packages</h2></div></div></div><span style="color: red">&lt;authorblurb&gt;</span><p><span style="color: red">By Pete Su and Bryan Quinn</span></p><span style="color: red">&lt;/authorblurb&gt;</span><div class="sect2">
+<a name="packages" id="packages"></a>OpenACS Packages</h2></div></div></div><div class="authorblurb">
+<p>By Pete Su and Bryan Quinn</p>
+OpenACS docs are written by the named authors, and may be edited by
+OpenACS documentation staff.</div><div class="sect2">
 <div class="titlepage"><div><div><h3 class="title">
 <a name="packages-overview" id="packages-overview"></a>Overview</h3></div></div></div><p>This document is a guide on how to write a software package for
 OpenACS. OpenACS packages are installed and maintained with the
@@ -22,7 +25,7 @@
 <div class="titlepage"><div><div><h3 class="title">
 <a name="server-file-layout" id="server-file-layout"></a>Server file layout</h3></div></div></div><p>Here is how an OpenACS 5 server is laid out starting from the
 Server root (ROOT):</p><div class="figure">
-<a name="idp140682185326152" id="idp140682185326152"></a><p class="title"><strong>Figure 11.1. Server file layout
+<a name="idp140560455798632" id="idp140560455798632"></a><p class="title"><strong>Figure 11.1. Server file layout
 diagram</strong></p><div class="figure-contents"><pre class="programlisting">
 ROOT/
     bin/
@@ -61,7 +64,7 @@
 <a class="indexterm" name="baby" id="baby"></a> To illustrate
 the general structure of a package, let&#39;s see what the package
 for the "notes" application should look like.</p><div class="figure">
-<a name="idp140682185307736" id="idp140682185307736"></a><p class="title"><strong>Figure 11.2. Package file layout
+<a name="idp140560468311672" id="idp140560468311672"></a><p class="title"><strong>Figure 11.2. Package file layout
 diagram</strong></p><div class="figure-contents"><pre class="programlisting">
 ROOT/
   +-- packages/    APM Root
@@ -124,14 +127,14 @@
 this case is <code class="computeroutput">ROOT/packages/notes</code>. The following table
 describes in detail what each of the files up in the diagram
 contain.</p><p>A special note on the <code class="computeroutput">
-<em class="replaceable"><code>PACKAGE-KEY</code></em>/www/resources</code>
-directory. Files in this directory are available at <code class="computeroutput">http://<em class="replaceable"><code>yourserver</code></em>/resources/<em class="replaceable"><code>PACKAGE-KEY</code></em>/...</code> and are
-returned without any permissions checking or even checks that the
-package is installed or mounted. Files are returned directly, so
-.tcl or .adp files are not sourced in these directories. This makes
-it suitable for storing icons, css files, javascript, and other
-static content which can be treated this way.</p><div class="table">
-<a name="idp140682185313912" id="idp140682185313912"></a><p class="title"><strong>Table 11.1. Package
+<span class="replaceable"><span class="replaceable">PACKAGE-KEY</span></span>/www/resources</code>
+directory. Files in this directory are available at <code class="computeroutput">http://<span class="replaceable"><span class="replaceable">yourserver</span></span>/resources/<span class="replaceable"><span class="replaceable">PACKAGE-KEY</span></span>/...</code> and are returned
+without any permissions checking or even checks that the package is
+installed or mounted. Files are returned directly, so .tcl or .adp
+files are not sourced in these directories. This makes it suitable
+for storing icons, css files, javascript, and other static content
+which can be treated this way.</p><div class="table">
+<a name="idp140560468316776" id="idp140560468316776"></a><p class="title"><strong>Table 11.1. Package
 files</strong></p><div class="table-contents"><table class="table" summary="Package files" cellspacing="0" border="1">
 <colgroup>
 <col><col><col>
@@ -370,7 +373,7 @@
 to add a new sub-folder called <code class="computeroutput">notes</code> to the root of the site, then click
 "new application" to mount a new instance of the
 <code class="computeroutput">notes</code> application to the site.
-Name the new instance <code class="computeroutput">notes-1</code>.</p><p>Then type this URL into your browser: <code class="computeroutput">http://<em class="replaceable"><code>yourserver</code></em>/notes/hello.html</code>
+Name the new instance <code class="computeroutput">notes-1</code>.</p><p>Then type this URL into your browser: <code class="computeroutput">http://<span class="replaceable"><span class="replaceable">yourserver</span></span>/notes/hello.html</code>
 </p><p>Now you should see the contents of the page that you added. What
 has happened is that all URLs that start with <code class="computeroutput">/notes</code> have been mapped in such a way as to
 serve content from the directory <code class="computeroutput">ROOT/packages/notes/www</code>. At this point, you
@@ -394,8 +397,8 @@
 <a name="packages-add-reading" id="packages-add-reading"></a>Additional Reading</h3></div></div></div><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc;">
 <li class="listitem"><p><a class="xref" href="apm-design" title="Package Manager Design">Package Manager Design</a></p></li><li class="listitem"><p><a class="xref" href="apm-requirements" title="Package Manager Requirements">Package Manager Requirements</a></p></li><li class="listitem"><p><a class="link" href="tutorial-newpackage" title="Creating an Application Package">package development
 tutorial</a></p></li>
-</ul></div><p><span class="cvstag">($&zwnj;Id: packages.xml,v 1.13 2018/04/22
-19:24:37 gustafn Exp $)</span></p>
+</ul></div><div class="cvstag">($&zwnj;Id: packages.xml,v 1.13 2018/04/22 19:24:37
+gustafn Exp $)</div>
 </div>
 </div>
 <include src="/packages/acs-core-docs/lib/navfooter"