evu

First up, I'm not a recruiter, nor an employer. I'm a front end developer that's just left a great agency and I'm trying to find someone to replace me. I don't get any commission or anything like that, I'm just trying to help a mate out. I'm a long time member of these boards and figured it's a great opportunity to put out there, and give something back. It's a well known digital/branding agency in Manchester and they're struggling to find a decent front end/WordPress developer. If anyone's interested send me a pm, with examples of your code. I'm not looking at experience, just as long as you front end well. Essential: WordPress themes from scratch Html/CSS JavaScript/jQuery It's vital to send over live code, whether compete wp sites (not just theme modifications) or a codepen/github account. It's crazy how many Dev job applications I've seen where no code was sent over. I figured it's okay to post in general as it's not a job posting per say, my old employer doesn't know and I'll be personally vetting before i send anything over. Cheers.

What the hell! Never seen that before, looks terrible. I'm a fan of BEM, oocss, etc but that looks far from maintainable. Will have too have a look see.

Indeed. Media Queries could fix it. Far from the best route, but possible in CSS. Depending on content, I didn't notice the content in OP.

woocommerce can do virtual products, don't see why you couldn't use that. They also do a premium plugin for ticket sales: http://www.woothemes.com/products/tickets-woocommerce/ ed: ah.. one month ago...

No idea about Bootstrap but you can do this with just CSS: https://jsfiddle.net/78rbpfwp/ You just need to know how much padding-top to use. (Height / Width) * 100 = % (450 / 960) * 100 = 46.875%

Well the plan is to make the changes and have Beanstalk deploy the changes to the live site once it's tested so shouldn't need to touch the ftp. In response to your question, that's the trouble I'm having understanding. At the moment the set up is this: Test/Development Server (internal access only) Live/Production Server (public facing) When a change is requested, I connect to the dev server via ftp, download the files to change, work on them and upload back to dev server. And so on until I've done whatever I was asked to do. Then that server is checked and if everything is okay, I tell someone what files changed, they take them from the dev server and upload to the live server. We only have access to the front end (templates, js, css, etc). All heavy backend stuff is managed by a third party and isn't accessible nor is it possible to have a local (my machine) version because it's managed by a third party. So, how am I supposed to work on the dev server if git is in the way and everything needs to be pushed to the dev server again and again? This is why I think I may have a misunderstanding on the process. I work for a company as big as Argos, New Look, etc. I am sure they have version control though. What I had hoped to have set up is this: *(insert bit I don't get, lets pretend I do have a local version)* I make the changes as requested, those are then pushed to the dev server. Once it's tested and signed off, those changes are pushed and merged with the live server code and Beanstalk takes care of deployment to the live server. So that bit in *(...)* is where, as I understand it, is where a local version should be. But as this is not possible, how do other companies do it? I should mention the third party that handles the back-end of the site also manages other well known big brand sites too, at least some of them must have version control set up... It's getting very annoying and I can't find answers anywhere Thanks.

I'm not "using" anything with git atm per se, and when I have used git for personal stuff that's how I did it though, I dunno, maybe because it's still quite new to me and I'm not fond of CL work.. Yeah, I have considered that thanks That's the problem though with this situ @@rbrtsmith, we can't have local servers, we don't have full access to the entire codebase (back-end stuff, think magento go stylee) but we do have access to the template files/css/js/etc. So I just don't see how it can be done easily when you have to push everything to the dev server. A typical case is when you keep adjusting and doing minor changes in css/js over the course of a few hours, this would mean lots and lots of minor pushes which is a hell of a lot of hassle compared to just dragging and dropping a file in an ftp client. Maybe I'm misunderstanding how it works entirely..? Cheers.

Hi, I've had a little experience with Git on a personal level, mainly to get to grips with it. In this case I had a local WP installation set up on ampps, I'd make changes and when I was happy I'd push the changes to Bitbucket and FTPloy would deploy them to my live server. No problem, simple enough. Now, the question is, how does this work for a large ecommerce site? At work we have a dev server and the live server. At the momement, we simply use FTP to try things on the Dev server and when it's signed off, it just gets manually FTP'd to the live server. What I'm confused about is how do you try things if I don't have a local server set up? I had planned on getting it set up so that things are pushed to the dev server, once it's signed off it gets merged with the live server code base and pushed to the live server. I don't understand how this works though, do I have to push/commit everything I want to try whilst developing to the dev server? That's a lot of hassle... How do you manage such a use case?

Dunno how current it is now but http://www.w3fools.com/ Codecademy is win. And then theres codebabes...

I see this question so much... Don't have a list of things to learn one after the other. It's inefficient and doesn't work. Here's how you go about learning webdev and getting a job in the industry: Build Things. Build a small basic website. Then a fancy full screen photography site or something. Then a CMS(Wordpress) site. Then something your client can login to for whatever reason. Then a web app. Then an ecommerce site. Then an android/iphone app. etc. etc. The list goes on, just build things. The point is: you'll learn what you really need to learn to get the job done as you go along, and wont learn the things you'll never need. (I'm still yet to ever use a definition list for example). You'll figure out what code you like, and what you don't. Which will dictate your speciallity (You might prefer and enjoy building Wordpress sites, or android apps, for eg). You'll have plenty of nice things to go on a portfolio. Doesn't matter if they're fake/made up sites, trust me. And you will NOT get a job without a portfolio of work. There's too many pretenders in the industry, employers will want proof. I had a six hour interview on my first job, in which I built something. You practise everything. You'll only forget things if you don't practise. I learnt about XML when I first started, never used it, haven't got the foggiest now. Bonus tip: You'll develop your personal workflow. Speed is a big thing for employers. Bottom line, if you want a job, have a portfolio. Oh and btw: I'm in Manchester, plenty of jobs, small agencies and big brands. You want to get good enough to get into a small local agency. There's a lot of competition, but most of it is ****. My aforementioned employer went 8 months before recruiting me, they had 3 people in beforehand, all theme jockeys who winged the interviews but couldn't code in a decent timeframe for cookies.

Create a code example on codepen.io

How can someone have so much hate for Wordpress.... It boils down to functionality and budget. If it's a small client that just wishes to update their menu page, use something like cushy. Or if you can justify the time and have skill to make it better than cushy/other small cms, create your own (but it better not be ****, I've seen too many **** custom back ends for simple tasks). If it's an average client that wants to add new product pages, blog posts, etc. Wordpress is a very good option. Quick and easily customisable, and has a nice back-end (as long as you're not ****). In my experience, joomla and drupal are ****(read: sub-par and too complicated for clients when compared to wordpress). If it's a bigger client wanting complete custom CMS for complicated functions/pages, or they just want a really nice, simple back end, then a good bespoke choice would be better. Most of the time, smaller clients don't need to update their site. And instead of spending X amount on cms functionality which they'll never actually use, that money is better spent on a copywriter or photography, etc. Wordpress is not just a blogging platform, it's epic. There's a reason half the web is run on it. The only issue with Wordpress is it's bloated, the only thing it needs is a custom builder. If you have even a remotely decent server, the performance on the back-end is incredibly negligible, unless you have a ****-load of traffic. Don't get me wrong, I've seen some terrible Wordpress sites, usually a theme from theme forest thrown on with a multitude of plugins. That's a recipe for ****. But I've seen and created some very nice back-ends for Wordpress too, making it easy for even the dumbest of clients to update any aspect of their site. Legend: * = sh1t

The general best practise is to have everything in one stylesheet, unless your extra styles are heavy enough to warrant another http request. I don't know the numbers (when xkb becomes enough to warrant another request), but after gzipping, minifying, etc., the extra styles don't add up to much. So unless you have a large amount of code in your other stylesheets, better to just add them to the global. Also, the media queries only fire if needed, which you can test yourself by opening chrome network console and seeing the requests when you resize the page: http://codepen.io/jhealey5/debug/zcBAG . This is not the case with all browsers though I believe, some will download the extra stuff regardless of if conditions are met. iPhones may be one of the culprits, I can't remember. There was discussion from chris coyier on this if you can find it. See how much extra page weight the extra styles are and if it's small, don't worry about it. Speed issues should always be tackled with most return on investment. So unless your gzipping, minifying, concatenating, compressing images, efficient coding, etc, first then you can worry about the extra 5kb in your stylesheet, otherwise focus on the previous aspects. Most of the time an extra http request is the worse option, so I'm led to believe. eD: this may be of help to you http://browserdiet.com/

It won't work if you just copy and paste it. Learn how it works first. http://codepen.io/jhealey5/pen/fAukK/

You want to let text-align: center do the work for you. http://jsfiddle.net/wWVm6/