- Corrected a bunch of broken links

-	Put bullets back on sitemap
-	In TOC, made it so that sub-headings work when an ID is declared, as well as when it isn't
-	Adjusted site so that non-.huge pages are a more reasonable size
-	Made it cope better with changing widths

Author: wayland

Programming-Productivity.xml

@@ -4,7 +4,7 @@
 <filename>Backend-to-Frontend-Design.xml</filename>
 <sitedir>RAD</sitedir>
 <content>
-<p>As per <a href="Programming-Productivity.html#UI-churn">Introduction to 
+<p>As per <a href="/#UI-churn">Introduction to 
 Programming Productivity</a>, the database experts should be in control of the 
 architecture.  </p>
 

RAD/Backend-to-Frontend-Design.xml

@@ -154,9 +154,9 @@ can best express this by making a bullet list of the things that I think should
 be implemented in an IDE that fully supports Programming Productivity:</p>
 
 <ul>
-	<li><b><a href="RAD/Database-Design-Editor.html">Database Design 
+	<li><b><a href="RAD/Database-Design-Editor.xml">Database Design 
 		Editor</a></b>: Lets you visually edit the design of your database</li>
-	<li><b><a href="RAD/Code-Editors.html">Code Editors</a></b></li>
+	<li><b><a href="RAD/Program-Editors.xml">Code Editors</a></b></li>
 	<ul>
 		<li><b>Regular Code Editor:</b> These are standard; no explanation 
 			needed</li>
@@ -170,9 +170,9 @@ be implemented in an IDE that fully supports Programming Productivity:</p>
 			the diagram have code inside them.  We should be able to edit it.  
 			</li> 
 	</ul>
-	<li><b><a href="RAD/GUI-Editor.html">GUI Editor</a>:</b> Something that allows editing the GUI in a visual, 
+	<li><b><a href="RAD/UI-Editors.xml#GUI-Editor">GUI Editor</a>:</b> Something that allows editing the GUI in a visual, 
 		drag-and-drop manner (Forms)</li>
-	<li><b><a href="RAD/Document-Editor.html">Document Editor</a>:</b> This allows people to edit a document that could 
+	<li><b><a href="RAD/UI-Editors.xml#Document-Editor">Document Editor</a>:</b> This allows people to edit a document that could 
 		be made into a report.  This would be influenced by word processors, 
 		and by the Notebook model (cf. Jupyter)</li>
 </ul>

RAD/Introduction.xml

@@ -146,7 +146,7 @@ where that's useful.  </p>
 control panels like those at <a href="https://www.bluecataudio.com/Products/Product_PlugNScript/">
 Blue Cat's Plug'n Script</a>.  </p>
 
-<h1>Document Editor (Reports)</h1>
+<h1 id="Document-Editor">Document Editor (Reports)</h1>
 
 <h2>Overview</h2>
 

RAD/UI-Editors.xml

@@ -53,6 +53,6 @@
 }
 
 .left-column ul {
-	list-style-type: none;	
+/*	list-style-type: none;	 */
 	padding: 5pt;
 }

TOP-toc.css

@@ -75,7 +75,7 @@ aspect of OOP.
 </div>
 
 <p>Note that the quote above observes that OOP doesn't go in for the features 
-mentioned in <a href="Collection-Convergence/Database-Engine-Neutrality.html">
+mentioned in <a href="TOP/Collection-Convergence/Database-Engine-Neutrality.xml">
 Database Engine Neutrality</a>.  </p>
 
 <div class="blockquote">
@@ -95,7 +95,7 @@ and troubleshooting.</p>
 </div>
 
 <p>For a partial explanation of why they're a snap, see 
-<a href="RAD/UI-Editors.html#GUI-Editor">GUI Editors</a>.</p>
+<a href="RAD/UI-Editors.xml#GUI-Editor">GUI Editors</a>.</p>
 
 <h2>File-Based Tables</h2>
 

TOP/Collection-Convergence/Database-Engine-Neutrality.xml

@@ -6,21 +6,21 @@
 <content>
 <h2>Overview</h2>
 
-<div class="blockquote" style="margin-left: 25%; margin-right: 25%">
+<div class="blockquote" style="margin-left: 20%; margin-right: 20%">
 
 <div style="float:right; margin-left: 6pt; margin-bottom: 6pt">
 <img src="TOP/Collection-Convergence/Introduction/converge.gif" 
 	border="0" alt="convergence diagram"/>
 </div>
-<p>There is a pattern to many of the recommendations (ie. <a 
-href="Concepts/Database-Engine-Neutrality.html">Database Engine Neutrality</a> 
-and <a href="Concepts/Data-Dictionaries.html">Data Dictionaries</a>): 
+<p>There is a pattern to many of the recommendations [ie. <a 
+href="TOP/Collection-Convergence/Database-Engine-Neutrality.xml">Database Engine Neutrality</a> 
+and <a href="TOP/Collection-Convergence/Data-Dictionaries.xml">Data Dictionaries</a>]: 
 Collection Convergence.</p>
 
 <p>...</p>
 
 <p>Besides morphability and scalability [described in the refactoring section of 
-<a href="file:///home/wayland/src/TOP/TOP-doco/generated/Introduction/Why.html"> 
+<a href="TOP/Introduction/Why.xml"> 
 Why Table-Oriented Programming</a>], another benefit is <b>easier training</b>. 
 Instead of learning four or more <b>different</b> collection management systems, 
 one should only have to learn a single protocol. Fine adjustments and 

TOP/Collection-Convergence/Introduction/index.xml

@@ -20,7 +20,7 @@ work.</p>
 <p>Here it also becomes clear that TOP also requires UI support.  Raku again 
 doesn't support this out-of-the-box.  Various UIs have been added, but these UIs 
 don't have consistent interfaces (eg. a curses-based form can't be turned into a 
-HTML form with minimal effort).  See <a href="RAD/UI-Editors.html">UI 
+HTML form with minimal effort).  See <a href="RAD/UI-Editors.xml">UI 
 editors</a> for the plan.</p>
 
 <p>This would require another set of language features -- forms and reports.</p>