About Craig Webb

User Experience

Re-Birth of WordPress

A new version of WordPress has come out and it provided an impetus to clean off the cobwebs and update. The old version was not secure. I have a long list of assholes who have registered on my blog for no good reason. I will find an appropriate use for that list.

Re-install was not so hard once I got into it. The hardest part was backing up my files via my web hosting service provider Powweb.

Now my Webblog is the same in the front end but better in the backend. I am excited to get into new stuff.

The first thing to fix is the pages on Webblog. The theme used here has not module for pages. That needs to be fixed. The pages are now just hovering over the header. Looks bad.

If you have valid advise how to fix that I’d like to hear from you. Also, I would like some tips on how to bling up my WordPress.

Re-doing my presentation layer (again)

I spoke to another developer last week about his work. I learned that he uses templates to design his web pages. He said something about “why bother trying to reinvent the wheel”.

Something about the conversation struck me. As a designer, I think that it is important for me to know the code. So I embarked on re-working on the website. I’m glad that I did.

My intention was to create some new content. Instead, I got involved with attempting to manage my most recent slew of bookmarks, and I started re-reading material about Blueprint.

I found a page that has an AJAX tool that allows people to re-program their blueprint code. I played with the tool, punched numbers on a calculator, and came up with something that I like. The new iteration of my website (the front end) is built with it.

Setup Tool for Blueprint set to 888
Setup Tool for Blueprint set to 888

Not many people still measure in picas but I sure do. My history reaches back to line-o-type and hand paste-up. I like a design that can divide, as easily into thirds as in half, so I like my numbers to count in twelve’s, sixes, threes and twos.

The page layout that I came up with 888px wide, 30 18px columns and 12px wide gutters. One thing about picas over inches is picas are smaller units and therefore more accurate. 18px wide columns give me much more flexibility than Blueprint’s default 30px. I like my 12px gutters as well. They provide a little more white space.

I spent a day and a half on building the first page. I did 12 more today and posted them. The content is the same as before – I am re-arraigning the chairs on the Titanic – but it is necessary to have the structure flat. There is a lot of “fudging” going on right now. I don’t believe in having “the site is down for reconstruction,” signs go up on my site.

Now, I can work on content development with clarity of the parameters of the site.

Re-working my website presentation layer

Just like most designers, I rarely get time (make time) to work on my own website. This past Thanksgiving I holed up in my cave and worked on a major revision of my style sheet.

It has been a year since I last made a major effort at redesign and I have been chomping at the bit for months to do it – writing little notes to myself about what I want to do.

I find my inspiration from working on my client’s projects, and from my seemingly endless search for a job. Most of my recent job search has been conducted on LinkedIn.com, and as I go I Google terms and phrases which I don’t know or somehow hook me.

This is an inexpensive way to get an education and I’m learning quite a lot. I know way more than is indicated by my work and credentials.

One example of a “find” occurred when applying for a Presentation Layer Architect position at Avenue A | Razorfish (no they never called). Well, what is a Presentation Layer Architect?

With more Googling I figured out that a Presentation Layer Architect designs websites at the code level, and that this design structure is critical for desirable traits such incorporating flexibility, expandability, Progressive enhancement, usability, graceful degradation, search optimization, semantic design and so forth. The list of programming code that Razorfish required was massive. *I hope they call me anyway*. I want to work for a company that thinks about things like this. I want to BE a company who thinks about things like this.

I heard somewhere that the difference between Google and Microsoft is that the leadership of Google is all engineers, while the leadership of Microsoft is MBAs. I want to be a Creative that is informed. I want to know the code.

What I am doing to my code in this go-round is restructuring the CSS design to direct its energy toward standard HTML elements. In my previous CSS version, I created code that targeted classes. So the intent of this redesign is that if I isolate the HTML page from the CSS, the page will still work. It may be butt-ugly, but it will work.

Theoretically, the flip-side benefit will be that my website will be easier to expand or update or restyle. It will also be simple and user-friendly and handicapped accessible.

There are other considerations that I have in mind as I perform this redesign. Cross-browser compatibility ought also be a benefit of this redesign. Somewhere I stumbled across the phrase “browser reset” while trying to hack code for MicroSuck.

My redesign started by integrating reset style sheets from five or more sources, including the CSS of my Xeiro blog template. My resources are the Base style sheet from RichInStyle.com, the Base style sheet from nealgrosskopf.com, Base style sheet suggestions from tantek.com, and of course the Base style sheet from meyerweb.com/eric/tools/css/reset/ .

This witches-brew of reset was picked through to create my own Swiss-army knife of all things reset – my MO is to use all of the crayons. I will test it out with use and eliminate stuff later. Right now, EVERY element seems to be at least listed in my CSS.

Along my job-search way, I discovered Blueprint Google code. I added bits of their reset and implemented the Blueprint structure, which I have tested and decided to modify. Already, I have been creating bits of classes, which I modify within one tag. CSS code .ml20, .tleft, and .tinytext becomes XHTML

[Note that the p tag element is the focus of the styling].

.tinytext = font structure and color
.ml20 = margin left 20px;
tleft = text-align:left;

Cool, I think. The thing is, old printer that I am, I like to design in twelve’s [divisible by either two or three] and Blueprint’s code is 30px columns +10px margins x number of columns – last 10px – and that does not divide by both two and three – so I’m fudging the column widths and using classes like .w201 instead. Other than that I recommend it OK.

What else? I suppose that I ought to speak of intent. My website started as a portfolio of my graphic design. The portfolio will continue to persist, but it is about to drop into the background of my website.

The entire “I want a job” mentality of the website will be superseded by and new focus on content. I want to be more like ivillage.com (yes I applied there too – call me, OK?) – more like a news magazine. I want to be a PR site. a Brand.

Recruiters are always asking me “what [one single thing] do you really want to be?” I distrust that question. It is a stupid question. I want to use all of the crayons. That is my MO.

This CSS code redesign is preparing the way for integration of all that new programming stuff – Drupal, JQuery, Smarty Php MVC Frameworks, MooTools, Script.aculo.us, ajax CRUD and Google code!



Concept, design and creative development.

Build a core identity and message tailored to your target audience.

Craig Webb Art provides all aspects of New Business Communications Development including project management, creative development, copywriting and graphic design.