Index: openacs-4/packages/search/www/doc/guidelines.adp
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/search/www/doc/guidelines.adp,v
diff -u -r1.3.2.2 -r1.3.2.3
--- openacs-4/packages/search/www/doc/guidelines.adp	13 Jul 2023 12:45:46 -0000	1.3.2.2
+++ openacs-4/packages/search/www/doc/guidelines.adp	2 Sep 2024 09:40:28 -0000	1.3.2.3
@@ -2,6 +2,10 @@
 <property name="context">{/doc/search/ {Search}} {How to make an object type searchable?}</property>
 <property name="doc(title)">How to make an object type searchable?</property>
 <master>
+<style>
+div.sect2 > div.itemizedlist > ul.itemizedlist > li.listitem {margin-top: 16px;}
+div.sect3 > div.itemizedlist > ul.itemizedlist > li.listitem {margin-top: 6px;}
+</style>              
 <blockquote>
 <h2>How to make an object type searchable?</h2>
 by Neophytos Demetriou (<a href="mailto:k2pts\@cytanet.com.cy">k2pts\@cytanet.com.cy</a>)
@@ -35,7 +39,8 @@
 writing concrete functions that follow the specification. For
 example, the implementation of <code>datasource</code> for the
 object type <code>note</code>, looks like this:
-<pre><code>ad_proc notes__datasource {
+<pre><code>
+ad_proc notes__datasource {
     object_id
 } {
     \@author Neophytos Demetriou
@@ -60,7 +65,8 @@
 file which associates the implementation with a contract name. The
 implementation of <code>FtsContentProvider</code> for the object
 type <code>note</code> looks like:
-<pre><code>select acs_sc_impl__new(
+<pre><code>
+select acs_sc_impl__new(
            'FtsContentProvider',                -- impl_contract_name
            'note',                              -- impl_name
            'notes'                              -- impl_owner_name
@@ -73,7 +79,8 @@
 <code>FtsContentProvider</code> and your concrete functions.
 Here&#39;s how an association between an operation and a concrete
 function looks like:
-<pre><code>select acs_sc_impl_alias__new(
+<pre><code>
+select acs_sc_impl_alias__new(
            'FtsContentProvider',                -- impl_contract_name
            'note',                              -- impl_name
            'datasource',                        -- impl_operation_name
@@ -93,7 +100,8 @@
 We do this by adding triggers on the table that stores the content
 items of your object type. Here&#39;s how that part looks like for
 <code>note</code>.
-<pre><code>create function notes__itrg ()
+<pre><code>
+create function notes__itrg ()
 returns opaque as $$
 begin
     perform search_observer__enqueue(new.note_id,'INSERT');