I've got the following so far:

• Primer (just an intro with syntax)
• Selectors (Type, Class, and ID)
• Selectors (Descendant, Child, Universal, Adjacent Sibling)
• Attribute Selectors
• Pseudo-classes/elements
• Declarations
• Making a Theme in Wikidot
• Font
• Background
• Lists and Tables
• Element Blocks
• Positioning
• Wikidot's page structure
• Theme Engineering
• Header
• Side bar
• Top bar
• Wikidot Tags
• Forum
• Content Blocks
• Multiple Wikidot Themes
• Media Types
• Browser Compatibility
• @import
• Colors

Are there any others, or are some of these redundant?

I'm watching the site, and the volume and quality of changes are outstanding.

Thanks, Timothy!

-Ed

don't forget that there is also the possibility to edit your theme via the admin in the top:nav for iron giant themes… And in my optinion is it likely that that will become the way to change your theme in the future…

It would be simple if wikidot replaced the ** with <b> but it doesn't. It's beeing changed to <strong>. Wich is also good according to W3C HTML5 standard. They could also have chozen <em> or <b>.

So I thought lets make a list where this conversion is explained. In doing so I came across some strange things like underlined text. This is beeing parsed as <span style="text-decoration: underline;">

So there are two things I am concerned about:

1. this is not HTML5 compliant
2. how can someone adress this selector to change the look? There is no class name.

I know this is CSS in detail but… It causes illogical ways of working, and that's not what wikidot is about I think.

#navi-bar .action-buttons a{color:#000;border:1px solid #666;background:#aaa;}

If you want to have fun with the div around the buttons :

#navi-bar .action-buttions{background:#ff0ff;}

—hartnell

#navi-bar-shadow{background:#777;height:100px;border:2px solid #000;}

— hartnell

I'm wrestling with the best way to present the information.

My first thought (which is the approach I started at cssreference.wikidot.com) was to list each selector in the base.css file and show how it's used in base.css, then include some sample custom css to demonstrate how you might tweak the styles and show a screen shot of the result.

But then I was thinking that if you're documenting something like h1 that appears in various selector blocks like:

h1,h2,h3,h4,h5,h6{ ... } h1{ ... } h1 a{ ... } #header h1{ ... } a.weditor-h1{ ... }

My final thought would be to break down the entire file from top to bottom, listing each selector block as it's own page and documenting it. The problem there is that there are a couple of things like #top-bar li ul that are listed twice as selector blocks (in this example they are 40 lines apart). Obviously, we wouldn't want two different pages for that. Then there's the issue of multiple selectors listed in one block like h1,h2,h3,h4,h5,h6 { … }.

My final, final thought would be to do something like Hartnell is doing with class:body and show where the selector is used in base.css. I really like this approach, especially if we can incorporate some specific examples and screenshots (or links to working examples).

Thoughts?

-Ed

http://cssprojectchat.wikidot.com/

http://css.wikidot.com/class:body

As you can see, it completely breaks the site format.

How do we squeeze it in?

— hartnell

It's mission is simple and can be described in one statement.

That single statement is like the Sword in the Stone.

• Many people tried to pull the gleaming Excalibur from the stone, but only one did. From the second it was free, it became a guiding light for the Knights of the Round Table.

• Each of us will take many tries at trying to speak the statement that defines the mission of The CSS Zone, but only one of us will get it right. When one of us does get it right, it will be a guide to keep us on course.

Sorry, no King Arthur. :)

Excalibur changed the world. Without Excalibur, the world would have been a different place.

So too, The CSS Zone will change the world.

How will The CSS Zone change the world for the better?

How will the world be worse off it never existed?

Answering these questions will give us the true mission of The CSS Zone. Do not respond to each other's post, except to say "I like that one." You can post as many statements as you want in this thread.

How will The CSS Zone change the world for the better?

How will the world be worse off it never existed?

Start Posting Your Answers Now!

Das Questions

• How do I format text in a table? (read, probably means create headers, adjust padding / margins / etc.)
• How do I make invisible tags? (or anything 'invisible'? answer display:none;
• How do I align text (center, left, four corners of the earth) in a div or table?
• How do I make an image smaller? (not necessarily need be a theme issue, but why not. :) )
• (challenging one) How to style a tooltip? (i can't nail that freek down in firebug!)
• How to create an infobox? (very common question)
• How do I float a table? (either with a div, or using a custom table and inline styles, or a class and custom table

That's enough for now. :)

— hartnell

— hartnell

IMO we should have clear, as short as possible titles. Beeing creative is one, but finding info fast and easy is another. So I don't think CSS primer is a good title… but hey that's only my opinion…. I find it very creative, but not clear… sorry

Already in good use:

• _solved —> Answered How-Do-I Question
• _unsolved —> Posted not adressed How-Do-I Question

What css.wikidot.com is trying to do is:

Inform people

Service to people

What am I doing as admin in a site about CSS? I doubt I can cotribute the 50th part of what each can, everyone knows that I discovered what CSS is only some months ago. So, my question is: what is expected from me in a site like this?

Thank you!
B.

PS:Not even Phil and Helmuti are here, and I am… I really don't get this, guys…. :P

For example, my "pet" project that I have been wanting to do for a long time is to fully document the base.css file that Wikidot uses. What's the best way to incorporate that into this site?

Timothy, your work on the IDs and Classes section is great, but a lot of what you're listing so far is clashing with my idea.

rhombus P and Steven have laid out a nice Q/A section, but there is a different category used for the included pages. I think we should all try to use the same set of tools where we can.

I guess what I'm trying to say is that I'd like to see us slow down and try to outline this project now to save a lot of re-working of pages and reorganizing content later. Maybe we could create our own version of the Hammer Pattern Pieter talked about in his blog.

Does this make sense or am I way off base? Maybe we could try to arrange a meeting in the chatroom and start laying things out on a design strategy page.

-Ed