* viewvc.org/url-reference.html
Make the stylesheet more like that of the template authoring guide. * viewvc.org/template-authoring-guide.html Collapse some style definitions, and add a little intro paragraph. * viewvc.org/contributing.html Hook the template authoring guide and URL reference into this document. git-svn-id: http://viewvc.tigris.org/svn/viewvc/trunk@1295 8cb11bc2-c004-0410-86c3-e597b4017df7remotes/tags/1.0.0-rc1
parent
f586a5ebed
commit
5d0109e325
|
@ -110,7 +110,7 @@
|
|||
— Jamie Zawinski
|
||||
</blockquote>
|
||||
|
||||
<p>Of course, an symphony of insanity can be composed in any language,
|
||||
<p>Of course, a symphony of insanity can be composed in any language,
|
||||
so we do try to stick to some basic guiding principles. Maintain
|
||||
whatever style is present in the code being modified. New code can
|
||||
use anything sane (which generally means <a
|
||||
|
@ -170,6 +170,16 @@
|
|||
<code>cgi/viewvc.conf.dist</code> file and the library module
|
||||
<code>lib/config.py</code> in sync.</p>
|
||||
|
||||
<p>Because ViewVC is a Web-based application, people will have ViewVC
|
||||
URLs hyperlinked from other sites, embedded in emails, bookmarked
|
||||
in their browsers, etc. It is very important to ensure that those
|
||||
URLs continue to retrieve the information they were intended to
|
||||
retrieve even if ViewVC is upgraded on the hosting server. In
|
||||
other words, as new features require modifications to the <a
|
||||
href="./url-reference.html">ViewVC URL schema</a>, make sure those
|
||||
modifications preserve the existing functionality of all ViewVC
|
||||
URLs.</p>
|
||||
|
||||
<p>The library subdirectory contains a module <code>debug.py</code>,
|
||||
which you may find useful for performance testing.</p>
|
||||
|
||||
|
@ -184,7 +194,9 @@
|
|||
<p>The library module <code>ezt.py</code> contains a module docstring
|
||||
which describes the directives used in the HTML templates used by
|
||||
ViewVC. The templates themselves can be found in the
|
||||
<code>templates</code> subdirectory.</p>
|
||||
<code>templates</code> subdirectory. We're currently developing a
|
||||
how-to guide for <a href="./template-authoring-guide.html">ViewVC
|
||||
template customization</a>.</p>
|
||||
|
||||
</div>
|
||||
<div class="section">
|
||||
|
|
|
@ -9,9 +9,13 @@ body {
|
|||
}
|
||||
table { margin-left: 1em; }
|
||||
td, th { padding: 0 0.5em; }
|
||||
th { vertical-align: bottom; }
|
||||
td { vertical-align: top; }
|
||||
th { background: rgb(60%,70%,90%); }
|
||||
th {
|
||||
vertical-align: bottom;
|
||||
background: rgb(60%,70%,90%);
|
||||
}
|
||||
td {
|
||||
vertical-align: top;
|
||||
}
|
||||
.h2, .h3 {
|
||||
padding: 0.5em 1em;
|
||||
border-color: black;
|
||||
|
@ -39,7 +43,9 @@ th { background: rgb(60%,70%,90%); }
|
|||
<div class="h2">
|
||||
<h2 id="introduction">Introduction</h2>
|
||||
|
||||
<p>### TODO ###</p>
|
||||
<p>This document represents an (unfinished) attempt at providing
|
||||
documentation for how to customize ViewVC 1.0-dev's HTML output via
|
||||
modification of its templates.</p>
|
||||
|
||||
</div>
|
||||
|
||||
|
|
|
@ -2,50 +2,29 @@
|
|||
<head>
|
||||
<title>ViewVC 1.0 URL Reference</title>
|
||||
<style>
|
||||
|
||||
body {
|
||||
background-color: rgb(180,193,205);
|
||||
color: black;
|
||||
font-family: sans-serif;
|
||||
}
|
||||
|
||||
table { margin-left: 1em; vertical-align: top; }
|
||||
|
||||
code { font-size: 130% }
|
||||
|
||||
table { margin-left: 1em; }
|
||||
td, th { padding: 0 0.5em; }
|
||||
th {
|
||||
color: #ffffff;
|
||||
background: #7a5ada;
|
||||
font-size: 0.8em;
|
||||
font-weight: bold;
|
||||
text-align: left;
|
||||
padding-left: 0.5em;
|
||||
padding-right: 0.5em;
|
||||
padding-bottom: 0em;
|
||||
padding-top: 0em;
|
||||
vertical-align: bottom;
|
||||
background: rgb(60%,70%,90%);
|
||||
}
|
||||
|
||||
td {
|
||||
background: #ddddff;
|
||||
font-size: 0.8em;
|
||||
font-weight: bold;
|
||||
vertical-align: top;
|
||||
padding-bottom: 0.1em;
|
||||
padding-top: 0.1em;
|
||||
padding-left: 1em;
|
||||
padding-right: 1em;
|
||||
background: rgb(65%,85%,65%);
|
||||
}
|
||||
|
||||
.h2, .h3 {
|
||||
.h2 {
|
||||
padding: 0.5em 1em;
|
||||
border-color: black;
|
||||
border-style: solid;
|
||||
margin-bottom: 1em;
|
||||
background: white;
|
||||
border-width: 1px 2px 2px 1px;
|
||||
}
|
||||
|
||||
.h2 { border-width: 1px 2px 2px 1px; }
|
||||
.h3 { border-width: 1px 0 0 0; }
|
||||
.toc-list { font-size: 90%; }
|
||||
|
||||
</style>
|
||||
|
|
Loading…
Reference in New Issue