+<div class="h2 app" style="border-left: 0px" id="customcontent">
+
+<h2 id="guidelines">Guidelines for a Useful Bug Report</h2>
+
+<p>
+Your bug will be much more likely to get diagnosed and fixed
+if you supply all the necessary information to make it easy to do so.
+</p>
+
+<ul>
+<li>
+<strong>
+Please
+<a href="http://www.tigris.org/servlets/Login">log in</a>
+to your tigris.org account before submitting a bug report
+</strong>
+<p>
+If you do not already have a tigris.org account,
+please register for one at
+<a href="http://www.tigris.org/servlets/Join">http://www.tigris.org/servlets/Join</a>.
+</p>
+<p>
+We do accept anonymous bug reports,
+but it may be impossible to diagnose or fix the bug
+if we need more information and have no
+idea who submitted the bug or how to contact you.
+If you choose not to create a tigris.org account,
+at least put some identifying contact information
+in the bug description.
+</p>
+</li>
+<li>
+<strong>Specify the version of SCons in which you observed the problem</strong>
+</strong>
+<p>
+This helps avoid wasted time trying to pinpoint the version,
+and also allows us to confirm if a later released version
+has already fixed your problem.
+</p>
+</li>
+<li>
+<strong>Provide SConscript files or other configuration that reproduce the problem</strong>
+<p>
+If you can, simplify the configuration to just the
+minimal subset that demonstrates the problem.
+It's much harder to diagnose a problem
+if the incorrect behavor is due to
+one particular item out of a thousand
+in a large configuration.
+</p>
+<p>
+That said, it's most convenient if you can provide
+an actual configuration (set of SConscript files
+and/or other input files)
+that can be downloaded and run to demonstrate the bug.
+The easiest way is to attach a .tar.gz or .zip file
+to the bug report.
+Note that the tigris.org Issue Tracker
+doesn't let you attach a file like this
+when you initially submit the report.
+You must first create the bug report,
+and then attach a file to it as a separate step.
+See below for the detailed steps.
+</p>
+<p>
+If your problem is evident from a few specific
+SConscript files lines,
+it's perfectly acceptable just to
+paste the lines into the Description field of the bug report.
+</p>
+</li>
+<li>
+<strong>Describe specifically the incorrect behavor you observed</strong>
+<p>
+It's best if you can cut and paste the output from SCons,
+especially any error messages.
+Otherwise,
+Vague descriptions like,
+"SCons errors out," or "Product XYZ doesn't compile"
+are extremely difficult to diagnose,
+because the different installed tools on someone else's system
+may cause SCons to behave differently
+and not demonstrate your bug.
+</p>
+</li>
+<li>
+<strong>Describe what you expected to happen</strong>
+<p>
+This isn't always obvious, especially if the
+bug does not involve an SCons failure or error message.
+Describing the behavior you expected
+helps speed up the diagnosis.
+</p>
+</li>
+</ul>
+
+<h2 id="steps">>Steps for Submitting a Bug Report</h2>
+