> 1. What would an appropriate style block look like? My understanding
> is that simply modifying the style of the body may not do what I'd
> like.
>
> 2. How should it be put into the site_css.cs file? Is it OK to embed
> it, or should I link to a separate .css file?
The site_css.cs file should contain CSS only directives.
You are using a HTML directive (<style>) to embed CSS rules.
In other words, replace
<?cs
##################################################################
# Site CSS - Place custom CSS, including overriding styles here.
<style type="text/css">
body {
background: green;
color: blue;
}
</style>
?>
simply with
<?cs
body {
background: green;
color: blue;
}
?>
You can also use the site_css.cs file to simply add a link to an
external CSS file, such as
<?cs
@import url(/web/path/to/style.css);
?>
A note about "/web/path/to/style.css" : a valid path means that when you type
http://server/web/path/to/style.css
you should be able to read the content of the css file (as a text
file), where <server> here is the name of your actual server; if not
(404 error or the like), your path is wrong. This is the first step to
check if you can get CSS working.
Here is a real-world exemple of style.css that I use to change the
color theme - very simple, as CSS is powerful enough to change the
position of each item if you want it to...
Disclaimer: there are probably some lines that could be removed or
tweaked here, I have not cleaned it up since 0.9...
:link, :visited { color: #a70; }
input[type=button]:hover, input[type=submit]:hover, input[type=reset]:hover {
background: #cba;
}
input[type=text]:focus, textarea:focus { border: 1px solid #688 }
#ctxtnav li li :link:hover, #ctxtnav li li :visited:hover { background: #ba0; }
#prefs { background: #f7f6f0; border: 1px outset #899; }
a.missing:link, a.missing:visited, span.missing {
background: #fafaf0; color: #986;
}
table.listing thead { background: #f7f6f0; }
table.listing tbody tr:hover { background: #edd !important }
#content.error .message, div.system-message { background: #fdc; color: #500; }
#preview { background: #fffcf4; url(../draft.png); }
tt { color: #6f6f6f; }
.wiki-toc { border: 1px outset #cdd; background: #def; }
.wiki-toc .active { background: #ce9; position: relative; }
table.wiki { margin-top: 1em; margin-bottom: 1.5em; }
/* comment edition */
.addcomment { background: #ffe0dd; }
/* ReStructured text */
table.table { margin-top: 1em; }
div.restructured { margin-top: 1em; }
.restructured h1 { font-size: 17px; }
.restructured .section h1 { font-size: 16px; }
.restructured h2 { font-size: 15px; }
.restructured h3 { font-size: 14px; }
.restructured h4 { font-size: 13px; }
h1, h2 {
margin-top: 1.5em;
margin-right: 1em;
background-color: #fffcf0;
}
h1 {
border-top: 1px solid #840;
border-bottom: 1px solid #840;
}
div.wiki h2 {
border-top: 1px dashed #840;
border-bottom: 1px dashed #840;
}
h1, h2, h3, h3, h4 {
padding-left: 0.5ex;
color: #840;
}
dt em {
color: #840;
}
div.ticket h1 {
margin-right: 0;
}
div.ticket h2 {
background: none;
border: none;
}
#ticket {
background: #fec;
border: 1px outset #986;
}
#ticket .date { color: #c70; }
#ticket table.properties {
border-bottom: 1px solid #db9;
border-top: 1px solid #db9;
}
#ticket table.properties .description {
border-top: 1px solid #db9
}
#changelog { border: 1px outset #986; padding: 1em; }
table.progress td.closed { background: #e0baab; }
.milestone .info h2 em { color: #840; font-style: normal }
#info {
background: #f7f6f0;
}
@media print {
div.wiki-toc {
visibility: hidden;
}
}
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Trac
Users" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/trac-users
-~----------~----~----~----~------~----~------~--~---
