throzen

This is true, but when it comes to the jobs market distinctions between front and back end are often out the door. I couldn't count how many "front-end" developer jobs I applied for which required candidates to know PHP. We're not talking mere exposure to it or basic knowledge - they must have heavy, professional experience using it, when PHP is purely server side scripting. Same for JavaScript, I see a lot of back-end job descriptions asking only for candidates with JS experience. It's a funky world, really. How much time you got? How fast do you learn? Only you can answer that question and you'd have a hard time answering it yourself. I would define an "intermediate" level as knowing a wide range of JavaScript functions, not having to look up how to handwrite it as well as not copying old code and changing it. Crack open a web tutorial of JavaScript and see where it takes you.

Absolutely. JavaScript is ancient, old school developers have had plenty of time to master it. There are endless possibilities yes, but you have to think of JavaScript like lego - there are only so many blocks to use, but you can create anything with them by piecing different ones together. It's not that there are hundreds-of-thousands functions in JS, it's just that you can create thousands of things with any combination. There are new innovative features and systems being made with JS even today. It's a case of thinking what you want to make, however big or small, and thinking how to go about making it using various JS functions. I would say ignore that Junior Web Developer role you were looking at. Different employers have different demands for their respective roles. I work for a company and my JS is sketchy, at best intermediate, and I'm still learning and probably will be for years. As long as you have a good understanding of it, not basic and not terrifically advanced, then you should be good to go. Also, there's no shame in looking things up. Employers would rather have something done correctly with some help from the web than doing it all yourself and possibly producing a buggy version. One of my friends, who is adept with most scripting languages, said their employer had a certain philosophy behind JavaScript-powered features: if it already exists and it's free, why make your own? It's a fair point but rather bad practise, but at the end of the day the goal is to make a website for a client using whatever means works best. (I wouldn't recommend hiding behind this philosophy though, it's probably not hugely popular, knowledge of JS is still necessary!)

I don't have your original code, so fill in the blanks where necessary: $(document).ready(function(){ $("more-information-click").click(function(){ $("terms-and-conditions-div").hide(); $("more-information-div").slideToggle(300); }); }); The T&C div will stay hidden while clicking the More Information toggle even if already hidden; it will display when you click the T&C toggle (as already live on your website).

Howdy doody, welcome aboard.

How much time have you spent learning both Photoshop and the key coding languages respectively? There's nothing wrong with covering all the bases, the trap you've probably fallen into is starting to learn something, and then stopping midway through, to start learning something else. If you want my advice, absolutely learn HTML5 and CSS3 first. Photoshop nowadays is not only unnecessary to web development but borderline redundant given the advances in CSS3. Photoshop is great for mock up layouts, logo design, icons, buttons etc... but that's about it, and skilled developers can replicate these just with HTML and CSS. I'll provide some comments on your current site however, to see if I can spark some ideas and improve your learning: - The main logo is pretty shocking, not in a great way. I agree with dap, but also disagree - it is certainly dated, but it does look retro to me; something you'd expect to see lined with lights blinking away outside a club. - Content is everything these days and there is a lack of it with your site. The home page just features three boxes (all of which are misaligned). Try exploring text-driven content, with some imagery to complement it. - The 'BankGothic' font used with the nav text is, well, BankGothic - it's pretty bland. You've tried to stay simple which is great, but go even simpler - a tidy Arial/Tahoma/Calibri font would suffice nicely. Also, not sure why the bottom links are multicoloured? Seems juvenile, no offence. - In some areas of your code you've used classes when IDs are usable. Generally you've used them correctly, but in some places (e.g. <div class="contact">) IDs are applicable. - The background really should be bigger, it's not large enough to cover any reasonable screen size. Plus you can see it repeating, just to the left of the centred content. Generally the site could use some touching up, but let's see what you come up with as time goes by.

There's nothing to view in your post, Vincent. Link us up.

Is this what you mean? Added IDs to the inputs, a CSS display property and a jQuery toggle: http://jsfiddle.net/fYtWj/1/

According to sources, IE9 only supports 2D transforms. Is yours a 3D one?

Precisely, thanks for clarifying D4Y0. Any script/system used by yourself but not written by yourself is recognised as third-party, as I pointed out earlier when mentioning free commenting systems. Clearly I spend too much of my free time trying to help people on here voluntarily since my advice is "****e".

This entire conversation suggests you're expecting things to be handed to you on a plate, getting pissy and acting disrespectful, especially saying to me "i'm not sure what so hard to understand i did say i didn't want an third party code". So, yeah, good luck.

Link me to your site, I'll see what you've done to the image.

It has nothing to do with the website itself, it's solely the PNG image. The image would naturally appear odd in the Facebook preview because the preview isn't sharing the styling attributes on your site that would support the image - Facebook just shows the image in its raw state. If you want it look normal you would have to make it opaque in your design program (Photoshop and whatnot).

Good to know. What CMS do you provide your clients with?

You make a good point sir. A small company is unlikely to face the task of designing sites by the bucketload each and every day. I imagine, as you said, it'll be a case of some days are hectic in the development of a new site, and other days rather mellow post-production of said website. Thanks for your story vincentweb, it helped indeed.

It's a very simple jQuery animate function by the looks of it. On hover, a div containing the info will drop down having previously been hidden. Search for jQuery animate plugin on Google, or just jQuery animate if you wish to try it yourself, it's very easy.

Welcome aboard Justin. Your avatar will cause me to wet the bed tonight.

Wheeyyy, good ole <table> days! I was randomly scanning the code of one of my websites and discovered there was a table being used to hold content, rather than a div, which I'd forgot to convert years ago. I genuinely slapped myself upon discovery. Welcome aboard, hope your own rediscovery goes well.

Still don't really understand, any free commenting system will ask you to install a code. Additionally, if you wanted to store comments, rather than just have users write to the page, then you'd need to integrate a database into whatever you choose. Good luck finding one, I can't help you.

What do you mean by "look after the code"? It's a one-off use of code, you'd only need to log onto the Disqus site to moderate comments should you wish to.

Disqus is arguably the most popular way, it's very simple to install and free - https://disqus.com/.

Welcome aboard.

*Downloads* ...I'm so glad my C.V. inspired you this much.

Hi... Bill... welcome.

'z-index' is a simple, albeit crude, stacking function. If you give one <div> a z-index value of 100, and a second <div> a z-index value of 200, then the second <div> will layer over the first <div> because its number is greater. It's useful if you want an easy way to place one <div> over another (with the right position conditions). You can also use minus numbers (e.g. 'z-index: -1') if you want a particular <div> to appear beneath every other element.

Change your #menu styling to: #menu { position: absolute; right: 00px; font-size: 00%; background: #ff0; margin-right: 1031px; background-attachment:fixed; z-index: 10000; } This includes the 'z-index' property, which basically places the #menu <div> above everything else on the page (including everything in the 'header_in' <div>). Should be fine now.