cibgraphics

The artwork may be yours because he hasn't paid, but think of it as this, perhaps a competing brand saw the logo, decided to steal yours instead, and then your client puts your out after, and then your client gets sued because of transmark infringment. Your client has every right to be pissed. When the logo is being worked on, keep it private. Its only common business etiquette. You want to flash it around facebook, do so only after the client has paid for it and it has gone public. Your client needs to come first.

I'm not sure he is talking about building a CMS, but rather generic information about them and perhaps set up an already established one.
 
Can you clarify TC.

Only a little condensending that image is. Let's not forget that this is just a tool. You should find out what works for you best and the rest is gravy. Arguing on if mac or PC is better is like girls arguing who is prettier, or guys arguing whose car is the coolest looking. It's stupid. Just stop it.
 
Even MS uses macs (Steven Balmers computer at a presentation)...

 
And im sure Steve Jobs and Tim Cook have used a PC at one point or another.
 
Just stop the squabbling.

Just a shameless plug. I created an Air app just for this purpose as well as calculating ems. You can get it at http://cibgraphics.com/projects/responsive-calculator
 
It's free by the way

Why are you asking with help and review of a template?

Did you code the theme yourself or just you buy and apply?
 
To be quite honest... I wouldn't buy because there isn't much info given on the products themselves. On design, the footer is nice, but the masthead needs a lot of help. The logo needs to be redone to something a lot more professional. The search/cart/navigation need to be integrated together more. You nav is so low on the page it gives it a real amature feel to it (and thats never good in an online shop). It makes the site feel untrustworthy. The nav also needs a new design. That whole section is really plain and doesn't do anything to get me excited about the product.
 
The contact and support link should be on the footer IMO, You never really see ecommercial sites have their support on their main header. You don't want to make users feel like its something they are going to need a lot (because of a bad product). Not sure about the blog either. I don't go to stores to read a blog. Thats your own choice, but I wouldn't expect a lot of traffic there so it may be wasted energy trying to keep that up.
 
Your 3 products on the home page makes me think that that is all you have, It wasn't until I clicked the products page (something I wouldn't normally do because of my previous comment) I noticed that you had more product.
 
Overall other than the footer, the layout needs to have some thought put into it. It needs some color as visually its boring.

In your code, the svg is content, and should be included that way (if you really do need to include a svg like that. The others are more of a concern for organization. There are better ways to optimize your code for speed than dirting your code.
 
As http2 becomes more adopted and browsers that don't support it die out, http requests will go away as a major concern.
 
Or am I not getting your post.

% is self explanitory, 50% of something is half right?
 
em and rem are based on font size, but the difference is that rem is based on the root font size while em is based on the parent's font size.
 
I wrote a pretty bad article about this. http://cibgraphics.com/blog/working-with-rem-and-viewport-sized-typography
 
I actually prefer to use rem over em because it is easier to work with. I also wrote a scss mixin to make it easier.
$font-size: 14px; // What ever you want but this variable is required. @function strip-unit($num) { @return $num / ($num * 0 + 1); } @mixin rem-size($value, $property: font-size) { $pxValue: strip-unit($value); $baseValue: strip-unit($font-size); $remValue: ($pxValue / $baseValue); #{$property}: $value; #{$property}: $remValue + rem; } You use it like: (include is lowercase, the forum is messing it up)
@[member="Include"] rem-size(14px);

% is self explanitory, 50% of something is half right?
 
em and rem are based on font size, but the difference is that rem is based on the root font size while em is based on the parent's font size.
 
I wrote a pretty bad article about this. http://cibgraphics.com/blog/working-with-rem-and-viewport-sized-typography
 
I actually prefer to use rem over em because it is easier to work with. I also wrote a scss mixin to make it easier.
$font-size: 14px; // What ever you want but this variable is required. @function strip-unit($num) { @return $num / ($num * 0 + 1); } @mixin rem-size($value, $property: font-size) { $pxValue: strip-unit($value); $baseValue: strip-unit($font-size); $remValue: ($pxValue / $baseValue); #{$property}: $value; #{$property}: $remValue + rem; } You use it like: (include is lowercase, the forum is messing it up)
@[member="Include"] rem-size(14px);

I am actually against designing in the browser because it is much harder to account for UX issues on the fly. My process is wireframes first, then conversion to mockups in Illustrator (desktop and mobile versions [tablet as well if the design needs it]) and then conversion to HTML/CSS. When designing in the browser I see far too many have the "good enough" syndrome where they don't push the design and UX because it is already coded and they want to move on to other things in the code. Yes it is harder to design for user interaction but those should be fleshed out in it's basic form in the wirefram stage and if needs be created in an isolated envirement (say codepen) and shown to the client for approval or have a design created for stages and then animated using the many tools out there to animate graphics without coding (https://facebook.github.io/origami/). Too many things get lost/forgotten/uncared for when designing in the browser.

This seems overly complicated. Can you show an example of how this menu works? I am 100% positive we can condense this code into something more manageable and easier to understand and in the process solve your issue.

you using:
<meta name="viewport" content="width=device-width, minimum-scale=1, maximum-scale=1" /> ?
 
Also can we see your site so we can see your code? Kinda hard to see the whole picture to track down what is going on.

You need to explain to the client that there is no magic button to press that make the changes appear for him. It will have to take some know how and some work to make the changes they need past simple text edits and images that are expected when they don't want to get into code. It gets easier when there are rich text editors but it can quicky mess up the style of any website. They have to expect a happy medium between the two.

I use statamic for my site right now and it is perfect from both a developer perspective and a client perspective. You can deploy it with git if you want because it uses YAML for its data instead of a database. The only downside to it that I have found is two fold, it has no comment system in it so you are forced to used Discus or something simular for your blog. The other is that you are forced to buy their form plugin (which is honestly super powerful and kicks EE's form handleing out of the water), but it is an extra $50. So for a typical site, it is $150. But I love the heck out of Statamic. Let me know if you have any questions about it if you dont want to purchase it.

There are a few places you can learn.

https://www.codeschool.com/
http://www.codecademy.com/
http://www.lynda.com/
https://www.udemy.com
 
 
I use Code Academy and Udemy

Teach them that pixel perfect is a stupid concept.

What exactly in the PSD do you need the exact measurment that the info panel can't get you?

If you want to learn grunt, which I highly suggest. I wrote a tutorial about getting started
 
 
http://cibgraphics.com/blog/grunt-js-basics-part-1
 
Also a good alternative to Sass\Scss is Less.

+1 for Grunt. Love me some Grunt.

If you're using grunt or gulp then you can run autoprefixer as a task then you quite literally never have to worry about vendor prefixes again. NPM keeps things upto date.

Glad I could help

Just started using this on a project 2 weeks ago. I think I like it better than owl slider, and it has an angular version which is super nice. Also easier to control break points for responsive than owl as well. I think its my new favorite. Has some work left to do like how they style their bullets but its easy to change. Might even make a pull request for them to fix it.
 
Such a nice slider.

The best carousel plugin I can recommend is http://kenwheeler.github.io/slick/
This plugin has everything you might ever need!

This x1000. I love Grunt and wouldn't dream of doing a site without it.

If you use a combination of sublime with a task runner such as grunt it negates any of the benefits of automation that DW accomplishes and grunt is almost infinitley customisable. Sublime also has a boat-load of keyboard shortcuts and a large array of plugins for things such as Emmet to really speed up the coding process.
 
I see no reason to use DW especially when it cannot even handle media querys.
 
 
Yes using something like grunt has a learning curve but that's the nature of this industry you have to learn and adapt or you get left behind. Command line task runners like grunt and version control etc are here to stay, and I see more things heading down this path in the future. We should all be learning the command line and getting used to using programmable tools (grunt uses js). My rate of production would plummet if I didn't have grunt, git or ssh server access.

Set your doctype for html5
<!DOCTYPE html> There is almost no reason all of your pages should have this going forward. The attr data-bvalidator is valid under html5. That being said, if it still doesn't validate because of that, then the validator is wrong and you should just ignore that.