MrBrightside

There's no such thing really, even Web 2.0 is too diverse to properly define. If someone told you they want a Web 3.0 site then they're probably having you on.

To add to this "discussion":

As for Elgg, I asked a guy at work about it and he said it's an absolute nightmare to work with, and even more of one to get to grips with. It has it's own API kind of programming so that you can customise it, similar to Wordpress plugins but with a bigger learning curve. It's also supposed to be very slow unless you have a powerful server running it. The site he build using it is now powered by ModX, does pretty much the same thing it was doing with Elgg, runs a lot faster, and is a lot more customisable because he wrote snippets for the various functions. From what he said, I'd stay well clear of Elgg though what you use instead is entirely up to you...

To select the parent items only: you can use the "has" selector to select <li> items that "have" a <ul> within them. E.g: $("#subnav > li:has(ul)").toggle(function() {

You're right there, even universities don't give out mark schemes to their own past papers! For the accessibility try this: http://www.w3.org/TR/WCAG10/. It pretty much answers that part of the question, I'm certain you can find as much information about the other topics if you look properly.

Really? Nothing?

Sounds quite straight forward. Bear in mind I've never used SourceForge before, but this applies to pretty much all SVN repositories anyway. 1) You need a working copy of the repository on SourceForge. You should have an SVN URL and username/password on SourceForge. To create working copy: on your PC, right-click where you want to checkout the working copy to (a subfolder in your htdocs dir?) and select "SVN Checkout". 2) Enter the URL, and enter your login details where prompted. 3) You'll end with a working copy of your project from SourceForge 4) Now copy in the files you want to upload to this working copy folder 5) Right-click in the working copy select "SVN Commit" 6) Enter a log message to describe the changes you've made and then submit Your files should now be in your SourceForge repository Basically, your username/password are the same as your SourceForge.net login. If someone doesn't have login credentials then [depending or your settings] they'll either be refused access, or they'll be able to checkout a read-only version

Yeah, the white box that was in the original CSS you posted earlier - you could add that in again for the white background, there's never only one solution . I just posted a modified version of your current CSS that repeats the background, and makes the footer sticky.

Not "instead". It will load in the main one AND then the IE6 one if the visitor is on IE6. In your IE stylesheet you only need styles for the borken elements - not the full stylesheet again

I use XAMPP (free and cross-platform). It runs on your computer and you access it by going to http://localhost You get the full PHP and MySQL with PHPMyAdmin support just like you would on a web server

When I tried yesterday it worked perfect. Looks like you've made other changes to the page including removing the white background image. Try this: * { margin:0; padding:0; } html, body { height:100%; } body:before { content:""; float:left; height:100%; margin-top:-32767px; width:0; } #sticky_footer_wrap { background-color:#FFFFFF; background-image:url("../images/jellybeans.jpg"); background-position:center top; background-repeat:repeat-y; min-height:100%; } #main_content { padding-bottom:43px; margin:auto; width:960px; } #footer { background-color:#000000; border-top:3px solid #FF9900; clear:both; height:40px; margin-top:-43px; position:relative; } #top_links { float:right; margin:10px; } #bottom_links { float:right; margin:10px; } #header { background-color:#000000; border-bottom:3px solid #FF9900; border-color:#FF9900; border-width:0 0 3px; height:61px; margin:0; } #content_wrapper { padding-bottom:10px; padding-top:10px; width:1000px; } .superking_logo { background-color:#000000; float:left; } Just add the white background to the white box again.

Well, bearing in mind your wrapper goes all the way down because you're using the sticky footer (the wrapper is 100%, then the footer is below it right?), why not apply the background image to the wrapper instead of the pedal_content_background. E.g: #sticky_footer_wrap {background:url('../images/jellybeans.jpg') center top repeat-y #fff;} I'm assuming you know what that means but in case you don't, it's a shorthand way of writing: #sticky_footer_wrap { background-image:url('../images/jellybeans.jpg'); background-position:center top; background-repeat:repeat-y; background-color:#fff; }

Glad that helped. How is your navigation generated - PHP, HTML or something else? Basically what you need is to add a class to the current item such as <li><a class="active">About</a></li> And then do this in your CSS: #navbar #about:hover, #navbar #about.active {background-position: -110px -40px;} Notice the ., not a : for the active state because we're using a classname, not a pseudo selector. The "active" pseudo class is actually the pressed down state - so that style is applied whilst the user has their mouse down on the link That way the style is applied to the hover state, and to the link if it has the active class.

Judging from that screenshot, I'm guessing you've hidden the text on the nav items using CSS, and when clicking an item you're shown the outline of the link which is stretching out to the left to go around the hidden text. Try adding this in your CSS (replace the selector to work with your nav link items): #nav a {overflow:hidden;}

A couple of ways to do this: 1) Mobile Stylesheet. Create a stylesheet specifically for mobile devices. It uses the same content on the page, but you can hide anything unneccessary. <link rel="stylesheet" href="mobilestylesheet.css" media="handheld"/> 2) Mobile Site. Create a dedicated site (subfolder/subdomain) for mobiles and redirect users to that site if they're using a mobile browser.

If you want to address IE6 specifically, and you only need to make a few tweaks then another stylesheet isn't necessary. You can add "* html" before any selector, and that will be picked up by IE6 because it thinks there's some super-star element around the html element. E.g.: a {color:#fff;} /* links are white on all browsers */ * html a {color:#000;} /* links are black on IE6 */

Consistency If done properly then your site should look the same in modern browsers, and at least similar in IE6 - except for the few known bugs. Transparent PNGs IE6 doesn't support 24-bit transparent PNGs. You can use supersleight, frankensleight or any of the other available png fixes to work that. Alternatively, you can create gif versions of those images, with a fixed background matte and apply them to IE6 only. Box Model Bug IE6 only again. This can normally be fixed by adding display:inline-block or display:inline to elements with double padding/margin. IE7 Hacks You shouldn't really need any. IE7 is pretty well behaved with CSS2. Anything that appears broken in IE7 you can normally fix in your normal stylesheet and will still work across all browsers. There's exceptions of course but that depends on your CSS. From looking at your site, the biggest issue I can imagine you having is with the transparent png images. I normally use supersleight which does the job if you're not using sprites.

Do people actually DO that? I always thought it was one of those things you ignore until asked about it, and then you reverse engineer

Submit your own question, and the ability for users to post their decisions A rating system for each question (like the +1) and sorting questions based on ranking

1) Add this to your CSS: a img {border:none;} 2) The line is part of this background image: http://www.bbhosts.co.uk/sitecss/images/wrap.gif

No worries. \n is a new line

Because you've got the variable names inside the double quotes which actually shows the value of the variable, instead of literally outputting the name of the variable. Try escaping the dollar signs with \$

<script type="text/javascript" src="js/localscroll.js"></script> That file isn't available on the server

Why don't you just ask your employer? I asked my boss and he said yes straight away. On my portfolio I have written "created at My Company" so it's obvious that I did it at work, rather than freelance

Leech it directly from Google, it'll save your bandwidth. As many sites do this, your visitor may even have the Google file cached on their machine from a previously visited site so it'll shorten page loading time too. You can get the latest from here For the current latest version in your page put this in your HTML: <script type="text/javascript" src="http://ajax.googleapis.com/ajax/libs/jquery/1.4.2/jquery.min.js"></script> EDIT: It says you solved it, but hopefully this will still help! Also, try to put your Javascript at the BOTTOM of your HTML, just before the </body> tag. Loading Javascript in the page <head> will slow down page rendering as it tries to load up your javascript files before the rest of the content is loaded. This works really well if you use unobtrusive Javascript.