systematric use of the doAnchor class

logback-site/src/site/pages/manual/appenders.html

@@ -42,8 +42,7 @@ <h1>Chapter 4: Appenders</h1>
     <script src="../templates/creative.js" type="text/javascript"></script>
     <script src="../templates/setup.js" type="text/javascript"></script>
 
-    <h2><a name="whatIsAnAppender" href="#whatIsAnAppender"><span
-    class="anchor"/></a>What is an Appender?</h2>
+    <h2 class=class="doAnchor" name="whatIsAnAppender">What is an Appender?</h2>
 
 		<p>Logback delegates the task of writing a logging event to
 		components called appenders.  Appenders must implement the <a
@@ -2719,9 +2718,7 @@ <h4 class="doAnchor" name="marker_GEventEvaluator">Marker-based
     </p>
 
 
-
-    <h3><a name="smtpAuthentication" href="#smtpAuthentication"><span
-    class="anchor"/></a>Authentication/STARTTLS/SSL</h3>
+    <h3 class="doAnchor" name="smtpAuthentication">Authentication/STARTTLS/SSL</h3>
 
     <p><code>SMTPAppender</code> supports authentication via plain
     user passwords as well as both the STARTTLS and SSL

logback-site/src/site/pages/manual/architecture.html

@@ -82,8 +82,7 @@ <h2>Logger, Appenders and Layouts</h2>
 		loggers.
 		</p>
 
-    <h3><a name="LoggerContext" href="#LoggerContext"><span
-    class="anchor"/></a>Logger context</h3>
+    <h3 class="doAnchor" name="LoggerContext">Logger context</h3>
 
 		<p>The first and foremost advantage of any logging API over plain
 		<code>System.out.println</code> resides in its ability to disable
@@ -149,9 +148,8 @@ <h3><a name="LoggerContext" href="#LoggerContext"><span
 
 
 
-    <h3><a name="effectiveLevel" href="#effectiveLevel"><span
-    class="anchor"/></a>Effective Level aka Level Inheritance
-    </h3>
+    <h3 class="doAnchor" name="effectiveLevel">Effective Level aka
+    Level Inheritance </h3>
 
 		<p>Loggers may be assigned levels. The set of possible levels
 		(TRACE, DEBUG, INFO, WARN and ERROR) are defined in the
@@ -330,9 +328,8 @@ <h3><a name="effectiveLevel" href="#effectiveLevel"><span
 		parent <code>X</code>, which has an assigned level.
 		</p>
 
-    <h3><a name="basic_selection" href="#basic_selection"><span
-    class="anchor"/></a>Printing methods and the basic selection
-    rule</h3>
+    <h3 class="doAnchor" name="basic_selection">Printing methods and
+    the basic selection rule</h3>
 
 		<p>By definition, the printing method determines the level of a
 		logging request. For example, if <code>L</code> is a logger
@@ -662,8 +659,8 @@ <h4 class="deftitle"><a name="additivity"
 		</p>
 
 
-		<h3><a name="parametrized" href="#parametrized"><span
-		class="anchor"/></a>Parameterized logging</h3>
+		<h3 class="doAnchor" name="parametrized">Parameterized
+		logging</h3>
 
 		<p>Given that loggers in logback-classic implement the <a
 		href="http://www.slf4j.org/api/org/slf4j/Logger.html">SLF4J's
@@ -841,8 +838,7 @@ <h4>6. Sending out the <code>LoggingEvent</code></h4>
   </a>
 
 
-  <h3><a name="performance" href="#performance"><span
-  class="anchor"/></a>Performance</h3>
+  <h3 class="doAnchor" name="performance">Performance</h3>
 
   <p>One of the often-cited arguments against logging is its
   computational cost.  This is a legitimate concern as even