r21932 - htdocs/branches/beta - Bug#660212: change headings for section's titles.

Cristian Marchi cmarchi at code.gnucash.org
Fri Feb 3 12:08:15 EST 2012


Author: cmarchi
Date: 2012-02-03 12:08:14 -0500 (Fri, 03 Feb 2012)
New Revision: 21932
Trac: http://svn.gnucash.org/trac/changeset/21932

Modified:
   htdocs/branches/beta/develdocs.phtml
Log:
Bug#660212: change headings for section's titles.

Modified: htdocs/branches/beta/develdocs.phtml
===================================================================
--- htdocs/branches/beta/develdocs.phtml	2012-02-03 13:49:15 UTC (rev 21931)
+++ htdocs/branches/beta/develdocs.phtml	2012-02-03 17:08:14 UTC (rev 21932)
@@ -20,10 +20,8 @@
 
 <div class="featurecontainer">
 <div class="featureborder">
-<h2 class="featuretitle"><a id="docsdevel"><?php echo T_("Documentation Development");?></a></h2>
+<h2 class="featuretitle"><?php echo T_("Introduction");?></h2>
 </div>
-
-<h3><?php echo T_("Introduction");?></h3>
 <p class="justify"><?php echo T_("The <span class=\"gnucash\">GnuCash</span> documentation is stored in <b>xml</b> files. More precisely, it uses the <b>GNOME2 XML docbook system</b>. This is a relatively flexible system that takes xml files as input and can generate documentation in several different output formats (html, pdf,...).");?></p>
 <p class="justify"><?php echo T_("If you wish to review or write <span class=\"gnucash\">GnuCash</span> documentation, you will need to know xml. Some basic knowledge of the docbook system may be useful as well");?></p>
 <p class="justify"><?php echo T_("The following links are for further sites that can help with the documentation and review process.");?></p>
@@ -35,20 +33,32 @@
 <li><a href='http://wiki.gnucash.org/wiki/Documentation_Update_Instructions'> Documentation_Update_Instructions</a>: <?php echo T_("A detailed guide on how to work with documentation (update and maintenance).");?></li>
 </ul>
 <p class="justify"><?php echo T_("We suggest also subscribing to");?> <a href='mailto:gnucash-devel at lists.gnucash.org'>gnucash-devel</a>.</p>
+</div>
 
-<h3><?php echo T_("Gnome Documentation guidelines");?></h3>
+<div class="featurecontainer">
+<div class="featureborder">
+<h2 class="featuretitle"><?php echo T_("Gnome Documentation guidelines");?></h2>
+</div>
 <p class="justify"><?php echo T_("As stated earlier, the new docs are based on the GNOME2 XML docbook system. Everyone wishing to help please follow these guides where possible when reviewing and/or writing docs.");?></p>
 <ul>
 <li><a href='http://library.gnome.org/devel/gdp-handbook/stable/'>The GNOME Handbook of Writing Software Documentation</a></li>
 <li><a href='http://library.gnome.org/devel/gdp-style-guide/stable/'>The GNOME Documentation Style Guide</a></li>
 </ul>
+</div>
 
-<h3><?php echo T_("Where to get the documentation source");?></h3>
+<div class="featurecontainer">
+<div class="featureborder">
+<h2 class="featuretitle"><?php echo T_("Where to get the documentation source");?></h2>
+</div>
 <p class="justify"><?php echo T_("You will need a recent copy of the documentation source. For this you can check out the documentation module from the <span class=\"gnucash\">GnuCash</span> svn. Reviewers could also start from the <a href='http://sourceforge.net/projects/gnucash/files/gnucash-docs/'>current docs tarball</a>.");?></p>
 <p class="justify"><?php echo T_("For those not familiar with svn, the <span class=\"gnucash\">GnuCash</span> wiki has a <a href='http://wiki.gnucash.org/wiki/Subversion'>description</a> tailored to the <span class=\"gnucash\">GnuCash</span> code. To get the documentation source instead of the program source, replace 'gnucash' with 'gnucash-docs' in the mentioned svn commands, like this:");?></p>
 <pre class="command">svn checkout http://code.gnucash.org/repo/gnucash-docs/trunk gnucash-docs</pre>
+</div>
 
-<h3><?php echo T_("Writers");?></h3>
+<div class="featurecontainer">
+<div class="featureborder">
+<h2 class="featuretitle"><?php echo T_("Writers");?>/h2>
+</div>
 <p class="justify"><?php echo T_("Get a copy of the documentation source as described above and start making changes. When you are satisfied with your changes you can create a patch by running the following command in the base directory of the documentation (usually gnucash-docs, unless you renamed it):");?></p>
 <pre class="command">svn diff > my-patch-name.patch</pre>
 <p class="justify"><?php echo T_("Next attach your patch to a bug report against the documentation component for the <span class=\"gnucash\">GnuCash</span> project in <a href='http://bugzilla.gnome.org/'>Gnome's bugzilla database</a> and send an email to <a href='mailto:gnucash-devel at lists.gnucash.org'>gnucash-devel</a> mailing list to inform other developers on your work. See also <a href='http://wiki.gnucash.org/wiki/Bugzilla'>GnuCash' wiki page on bugzilla</a> for more details about patch submission.");?></p>
@@ -57,12 +67,17 @@
 <p class="justify"><?php echo T_("Please let other writers know which section you wish to tackle. Please forward this to <a href='mailto:gnucash-devel at lists.gnucash.org'>gnucash-devel</a> so that people can say 'hey I'm doing that already' or 'go ahead and do it'.");?></p>
 <p class="justify"><?php echo T_("You may also want to retain a local copy of the old documentation to refer to when writing. This still has a lot of useful information in it which hasn't been transferred to the new docs");?></p>
 </div>
-    
-<h3><?php echo T_("Reviewers");?></h3>
+</div>
+
+<div class="featurecontainer">
+<div class="featureborder">
+<h2 class="featuretitle"><?php echo T_("Reviewers");?>/h2>
+</div>   
 <p class="justify"><?php echo T_("Get a copy of the documentation source as described above and start commenting on it.");?></p>
 <p class="justify"><?php echo T_("The best way of retaining comments about docs in an easy to find way for everyone would be to use <a href='http://bugzilla.gnome.org/'>bugzilla.gnome.org</a> to file the bugs under documentation. This can also be done using bug-buddy.");?></p>
+</div>
 
 </div>
-</div>
+
 <?php include("externals/footer.phtml"); ?>
 



More information about the gnucash-changes mailing list