   meta name vs meta http-equiv?
  I am trying to build my game's internal website. I see that the name and http-equiv attributes for the <meta> tag conflict with one another in the sense that one "cannot be set if the other already is" (according to W3 Schools).(1) Why the conflict?(2) What is in keeping with best practices? A long list of name="x" content="y" metas or the http-eqvuiv="ContentType" etc.? And why?   
  You've misunderstood the wording on that page slightly.  What it's saying is that when you define either one of those attributes, you cannot define the other one in that current meta tag.Here's an example:<meta name="keywords" content="gamedev, software, 3D" />In the above meta tag, you could not define the http-equiv attribute, because name has already been defined.  Conversely:<meta http-equiv="Content-Type" content="text/html;charset=ISO-8859-1" />Same thing applies: you can't now add a name attribute to that meta tag, but that doesn't mean you can't specify the name attribute in another meta tag.  Here's a perfect example, right from the source of this very site:<meta name="Keywords" content="game development, game programming, game jobs, video game jobs, games jobs, graphics programming, OpenGL, DirectX, Direct3D, AI, artificial intelligence, game design, game, gamedev, development, programming, c++, games, program, create, design, gouraud, shading, tutorial, art, gdnet"><meta name="Description" content="Gamedev.net is the leading resource for game developers, featuring daily news updates, over 1500 featured articles and tutorials, and the most active game development forums anywhere!"> <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1"/>It's just explaining that they are mutually exclusive to the current meta tag, so the following is illegal:<meta name="keywords" http-equiv="Content-Type" ...etc... />Does that help?   ;  Yes! Thankyou!   