jheg

Well I just had a look at the Adaptive Images site and it looks pretty great. Thanks again.

Basically what most said above me. If your target audience is beginners, then you should explain how PHP operates in the grand scheme of things.
 
Here are some questions you may want to consider answering before diving into programming basics and PHP language constructs:
"What is server side scripting?"
"What is PHP?"
"What do I need in order to code in php?"
"How can I run PHP code?"
"Why can't I view PHP source code in the browser?"

Furthermore, I know what you've shown us is incomplete, but what I've read so far is not beginner friendly. Here are just a list of some things I noticed...
"Variables in programming are containers that “you” the programmer would pass a value to such as a object,string,array or boolean." What is an object, string, boolean, or array? Perhaps you don't want to explain the various data types in depth just yet, but at least conveying that there are 6 various PHP data types and 2 special types could prove useful. By doing so, the reader can understand exactly what can be stored in a variable. You can then expand on some of the more advanced non scalar types later on in your book.
A beginner may not understand the concept of "hard coding" despite the fact that you attempt to explain it, so it's usage can be intimidating and confusing. It may be better to not mention it at all.
The globals section doesn't have a proper explanation of what a "global" actually is. Instead, you continue to mention the "global" keyword and how it relates to functions. What is a function? How do I know if my variable is global or not? As "Scope" can be a pretty difficult topic for learners to grasp, you may want to avoid tackling some of it's major concepts in the very beginning.
In my opinion, superglobals needs a more thorough explanation. In fact, I'd suggest you don't discuss them so early in your book (while you're still in the process of explaining the basic variable) as it could lead to major confusion.

Perhaps it would be better to explain some core concepts of programming instead of jumping into PHP so quickly. The reader needs to understand the concept of a "statement" before anything else.
 
Kind Regards.
 
PS: There's nothing wrong with directing readers to XAMPP as it seems the purpose of your book is to teach readers how to program in PHP as opposed to how to configure it. With that being said, consider providing links to resources where the reader can learn more about tweaking their server.

it's picking up this
content: " (" attr(href) ")"; from your print.css

You need to change the meta description in the head section buddy.
 
Place this in your head section.
 

<meta name="description" content="YOUR DESCRIPTION GOES HERE " />

Simple. If they post on your Wall asking for something but will happily deal with anyone who jumps on them, they're not the sort of client you want to have or keep. Work with clients who want to work with you specifically.

I have just come across this artice
 
Back To The Future: Google Announces A Meta Keywords Tag Just For News Articles
 
http://searchengineland.com/google-announces-news-keywords-metatag-133759

Future upgrades will include closing the gap between the pedestal and the left hand edge of the desk and removing my socks.
 

Future upgrades will include closing the gap between the pedestal and the left hand edge of the desk and removing my socks.
 

Right. Sorry about the ignorance thing, been a long day and I was a tad on the cranky side. To address your points:
I identified three shades of grey (#888888, #7D7D7D and #A6A6A6) which you've used for body text on a #FFFFFF background. You may not be able to see any difference (with your eyes, on your screen etc etc) between #888888 and #767676 - all that demonstrates is that you can change the #888888 and #7D7D7D to #767676 and it would be no skin off your nose but would be a tiny incremental improvement to the experience for everybody and would make the difference between legible and illegible (but still not comfortable) for edge cases. And what about the #A6A6A6 for your secondary navigation?
 
At no point have I said that #767676 is perfect, it's just the extreme cut-off point of what the WCAG considers to be acceptable contrast. It doesn't magically become legible to all partially sighted users at that point. If they made the minimum recommendation #666666 you'd be pulling the same complaint about #777777. They don't say "make it #767676 and everything will be ok", they're saying "use #767676 on white as a reference point - the darker than this, the better".
 
Screens differ widely in quality. Quality in TN panels (the vast majority of low-end to midrange screens) tends to suffer at either the black or the white end of the grey scale.
 
Monitor backlights dim with age. Without a second monitor to compare against, most people don't notice their whites becoming light grey.
 
The vast majority of non-professional users don't calibrate their screens, so the quality of their settings depends on factory defaults (which also vary wildly in quality) and a cursory fiddle with brightness and contrast settings, which will (ironically) improve their perception of black against white at the cost of light greys vs white and dark greys vs black.
 
The designers and developers you've consulted about this are statistically more likely to be using a calibrated, high-quality screen than the average user.
 
Visually impaired users are more likely than normally-sighted users to have the calibration problem I mentioned, as most calibration is done by eye and they're less likely to be aware of subtle differences in luminance.
 
Separate but equally important point: what is possible to read is not the same thing as what is comfortable to read. I, as a user with a high-quality, calibrated monitor would find that your text induces eyestrain sooner than higher-contrast text - just as I can read text with a measure longer than 85 characters (like this forum), or a leading/line-height of less than 1.2ems, but find it easier at 85 characters or less and a line-height of 1.3-1.6ems (best figure depending on context, text size, boldness, choice of typeface and foreground and background colours). By introducing more eyestrain and/or cognitive load, you're making it more difficult for people to do what you want them to (ie, use the site).

If you have an answer to all 8 of my points, go right ahead. If you can't answer all of them, it means there's something you've failed to take into account, and you've been more interested in arguing the toss over it than correcting it.

http://contrastrebellion.com/

I wonder how many meetings it took to come up with that when in reality I could have popped into the office, shouted sans-serif and popped out again.

http://db.tt/7ns74Xvt
 
Here's how it looks ba!

Come into thread to look at very interesting debate.
 
Something about Jesus.
 
Immediately leave.

If it's meant to be Tip Top, swap the Tip and Top on that last one. People will read from top to bottom before left to right, so it looks like Top Tip

Or something very modern and minimalistic to get away from the 'stuffy' persona?

Good progressions so far.
 
Still missing something memorable i feel. I missed the part where the bird was needed?
 
Just messed around quick for some food for thought.
 

 
Nothing special, just different directions you can go in.

Ugh fine I'll say it then. DreamSynk, You're an arsehole for making it personal.

I'm going to ignore your ad hominem attack, but I will still try to help you:.
 
 
I've been a full-time freelancer for the past 2 years, and I'm still in business. You won't be in business for very long if you do creative spec work before you've signed a contract and taken a deposit. Spec work is damaging to the design profession as a whole, because it's hastily thrown together and ill-informed - how are you going to do the research necessary to create a thoughtful, well-informed design if you're doing it in the hope of landing the project?
If you do all the research and discovery before you're under contract, you're committing a substantial portion of your time to something without any guarantee of payment.
If you don't do the research and discovery, you're trying to land the project on the basis of visuals that may well need to be thrown out and replaced with something adequately-researched once the project actually kicks off.

Either way you're wasting your most finite resource: your time. Your client should already have enough confidence in you based on your initial approach, your own site and your portfolio of past work to sign on the dotted line and commit to a professional relationship.
 
Here are some resources that might be useful to you:
 
Design is a Job by Mike Monteiro, available from A Book Apart
Design Professionalism by Andy Rutledge

Apparently not

Apparently not

It's design, everything is personal taste and I was hardly going to give you constructive criticism before I knew what I was criticising.
 
Web Design (or more generally digital design) tends to embody certain aspects of the digital world, because it's meant for here. There are certain things that hint towards certain types of industry and although they aren't hard and fast rules they are very difficult to overcome if what you are designing isn't for the industry it implies it is.
 
The digital world tends to be sharp edged, smooth, uniform and vibrant. It's a square 2D universe powered by light so when you try to mould in bevelled edges and soft colours you are going against environment and that tends to imply that whatever is being advertised is outside that environment.
 
Serif fonts are the easiest example. We use them when we want to harken back to the old world. Newspapers, Banks, Lawyers. They imply institution, trust, class, wealth, luxury etc.
 
Pair that with the soft purple colouring you have used, the bevelled edge and the scattered word placement it immediately brings to mind soft furnishings. You've created something in a bright uniform world that's neither bright nor uniform and like I said above, that implies something outside the environment.
 
That's not to say I think you should start from scratch. I actually like the purple colour and the word placement but I think you would be much better served by a sans-serif font and dropping the background.

Mortgage is one of those words that every internet asshole and their gran is crawling all over. It's prime real estate for those oh so useful parking pages, so you might have trouble getting any nice domains that aren't very personal.
 
HouseBuyGuru.com is available though if you want to break the mould.

Will have my camera ready!

ol { counter-reset: item; } li.heading{ margin-bottom:20px; } ol li{ font-weight:bold; text-transform:uppercase; list-style-position:outside; } ol li:before{ content: counters(item,".") ". "; counter-increment: item; display:marker; } ol li ol li{ font-weight:normal; text-transform:none; } ol li ol li ol li{ margin-left:2.5em; list-style-type:lower-alpha; } ol li ol li ol li:before{ content:none; } ol li ol li ol li ol li{ list-style-type:lower-roman; }
 
Is this what you want?
 
Should work - http://jsfiddle.net/...nHegarty/VNSK5/
 
Its not without problems though. If you have a lot of text in those sub li's so that it spans two lines or more the text on the second line will align underneath the higher level li.
 
Source: http://webmasters.st...with-subclauses