text colour

Tons,
Have you altered the wp-layout.css file? If the wp-layout.css file is being imported, then you have competition between your styling in the index.php file and the CSS file which will cause you massive headaches.
BTW…<font> tags are EVIL! ??
Craig.

Hi Craig thanks for such quick help.
I have NOT altered wp-layout.css and I have NOT placed a call for a style sheet in my index.php page. This is because I’m not knowledgeable about css ?? and just wanted to build the site in plain html.
I though the same thing that tags like <?php get_archives(‘monthly’); ?> might somehow still be getting their style, colour etc commands from the wp-layout.css file so I deleted the wp-layout.css file but that didn’t fix the problem. I then put the css file back and looked through it for a place where I could set the font colour for the archives, categories lists and link list fonts to yellow but I could’nt find anything.
Where do i go to make the text for the archives, categories and links list yellow?
Thanks for your help.

Those categories are already covered by the css.
#menu ul ul li a {
color: #000;
text-decoration: none;
}
#menu ul ul li a:hover {
border-bottom: 1px solid #809080;
}
an active tag will be black, (#000) and when hovered, will have a solid underline and turn the colour #809080.
Change them, and you should be fine.
(I think that’s right …)

Oh…and do use the CSS.
When I first started writing pages, I too did not use CSS. Now, I would not be without it at all.
It makes life hugely simpler, even though at first there is a bit of a learning curve.
Go look at the CSS pages…
https://www.alexking.org/index.php?content=software/wordpress/styles.php

If he’s not importing the CSS file then how could the stylesheet be affecting the way the page is displayed? Osmosis?
There’s not much point trying to make or edit a template if you don’t know anything about CSS. Either do a crash course in it or go download one of the styles from the link above.

He says last in his post that he had put the css back – hence my indicating the correct point to look at.
I agree though, either adopt a style or take a crash course.

Thanks podz for the info and link to CSS – it is really helpful.

Tons,
The wp-layout.css file is explained here. You may find it somewhat helpful.
Craig.

Also, when making changes like that, it is a good idea to clear the cache in between. Otherwise the browser will just use what it has….
TG

Tons the best place to *go* is w3c css and read all about it.

He, he…opintions are like (you know the rest). And I, like many others, have an opinion.
For learning CSS I would check out some CSS tutorials (perhaps at w3schools.com, htmlhelp.com, westciv.com, alistapart.com, and many others). I would also suggest some good books such as Eric Meyer on CSS, and Designing with Web Standards.
I wouldn’t suggest a beginner go to W3C.org. Although that’s the standards body that publishes the specs, the specifications are difficult for newbies to read, let alone comprehend. Plus, they don’t discuss difficulties with the way different browsers handle certain tags, etc. The specifications are more for those building applications (like the Moz/Firefox team, for example) to ensure their products work as the specifications say they should…not for beginners to learn CSS.
That’s my 2-cents, anyway.
-Tony

Well tcervo maybe some folks are just more technically minded ?? Sure it is horses for courses and your references are fine. Newbie or no I would never want to discourage a person from going and getting the spec though. They have a lot of examples as well. Plus a lot of interesting stuff to read. It is also by definition, clearly explained and authoriative. A lot of tutorials do not necessarily make clear the origins of issues like the div height rule for example. Nor do they make clear CSS 1/2/3 differences. For a lot of folks they can’t do better than reading the source material. There is also the possibility of someone inadvertently being pointed towards a site, which may itself not be either technically sound, or well explained. Plus never lets forget W3C supplies a mighty fine browser.