After putting in more time than I will admit without coercion, I feel close to being able to fine-tune an Atahualpa-themed site using Google Chrome Developer Tools (GCDT). But there is/are a hump or two I just can't get over. The URL is:

http://www.abcaudiology.com/

And the task that eludes me is to get a "handle" on the text in the sidebar to make it smaller. GCDT shows:

" <div id="text-3" class="widget widget_text"> <div class="textwidget"><img class="size-full wp-image-163 alignleft" title="Hearing aid is small and powerful" src="http://www.abcaudiology.com/wp-content/uploads/2011/01/handaidtype160.jpg" alt="Hand holds hearing aid" width="160" height="160" />
<h4>Those who decide to try a hearing aid at ABC enjoy multiple safeguards…</h4>
<p>1. The first 30 days are a risk-free trial. Return it if you don't like it.</p>
<p>2. The hearing aid...."

I'm using a child theme that seems to be working except that only some of what I add to it has any effect. I tried redefining "text-3" and "textwidget" without any change. I tried writing a new class for "widget widget_text" and nothing changed.

A secondary but related matter is that I suspect my size declarations are "confused." I thought I could set the basic text specs for the page in "body" but while the body settings have an effect, they seem influenced by something else.

Third and last, I haven't found the place to edit the overall specs for the <h1> through <h6> heads.

Feel free to poke around the site as you like. Feel free to speak candidly about what I need to learn.

Chuck M

Atahualpa is not designed for child themes. Typically to size the text in a widget you would determine the selector as you did and then put the necessary CSS in ATO>Add HTML/CSS Inserts>CSS Inserts.

As an example to change the text size to 12px in your left sidebar I would add something like the following in CSS Inserts.

#text-3 .textwidget {
    font-size: 12px;
}

The H!-H6 tags are similarly handled by putting something like the following in CSS Inserts and adding whatever styling you want.

H1 {
font-size: 30px;
}

I am very grateful to receive your reply. I know of the area you mention to place the code - and will be happy to use it.

Don't believe I searched for a child theme thread. Perhaps that might have simplified my labors. WordPress users were strong in recommending child themes, and I made the assumption that a current and "good" theme like Atahualpa would adopt a child willingly. Thanks for shooting down another flawed assumption.

Your H1 code uses pixels. I've been reading about ems being preferable for viewer flexibility. Matter of choice, likely. No need for a reply unless there's a reason Atahualpa should be fed pixels as the type measurement.

In dashing off to a shower, I realized I had brought up the question of Atahualpa sizing type in pixels, and wondered if it needs to be that way, or if ems would be fine. Brought it up without looking first in this site for the answer.

So I just searched the Atahualpa section (I think) for "sizing type" and "type in pixels". Was surprised again to get no results for the first and no germane threads for the second. (Designers *always* fuss with type size; I guess bloggers don't.)

So the question remains on the table; perhaps warranting an answer, perhaps not. And now I dash off to a meeting at my church.

I usually use pixels (px) so I know what size text I will have but em is OK too. A Google search on px vs em should get you completely confused.

Atahualpa uses pixels. You use pixels. For the time being, that's good enough for me.

Chuck M

Just to be clear Atahualpa doesn't "use pixels". It's just a measurement. You can use either when creating your CSS in Atahualpa.

That's a half-interesting malaprop on my part: "use" pixels. As if a different theme might build the page image with lines or stars or smiley faces or something. I just meant that in a CSS capitulation window (don't know the real name yet) I noticed that Atahualpa specified font-sizes and headline sizes in pixels. Rather than % or ems.

For me this thread is SOLVED. (Probably should know how to mark it as such.)

For the record, I was referred here by participants on the Wise Women discussion list, easily my favorite list for talking about webwork. lmilesw's words are now famous there, since I quoted them in describing the solution to this problem. (Didn't mention your name though; don't know if I coulda/shoulda.)

Gender conscious folks unfamiliar with that list might puzzle with the facts that I am neither wise nor women. I assure all that that makes no difference to the good people on the list. Subscription and list info: http://www.wise-women.org/about/join/