-
Notifications
You must be signed in to change notification settings - Fork 0
FAQs
- boilerplate ships with a default configuration for the apache web servers. It's documented in .htaccess. Configuration files for web.config, nginx.conf, node.js, and lighthttpd are available in our server-configs repo.
- Modernizr detects HTML5 and CSS3 features and adds classes to the html tag to let you style accordingly. http://modernizr.com/docs/
- the
?v=2thing in the asset URLs freak you out? read Version Control with Cachebusting (this technique was removed as of v1.1pre)
- Breathe in and out
- Join our mailing list
- Upload your code to JsFiddle
- Write a mail to the mailing list explaining what you expect to happen, and what actually happens. Do not forget the link to your fiddle from the previous step! Voilá!
- If that's the case, submit an issue ASAP! Even better if you know the solution, as that would make it faster to fix (everyone wins!)
- Read more about protocol-relative URLs
Can I integrate 960.gs with HTML5 Boilerplate?
If I don't want to support IE6 and I don't want my sites to be IE6 compatible so I can make them lighter, what parts should I remove?
- The conditional comments around the html tag and the conditional include of support for transparent pngs at the bottom should be sufficient in the HTML.
- In the CSS, just remove all selectors that start with .ie6.
- There are a few style properties that start with
_for the ie6 hack. You can kill those too, if you're feeling daring. - a
list-style-image:nonestyle that only is necessary for IE6 and IE7 is in thenav ulstyles. (issue #263) - If you've given up on IE6 users, you should prompt for chromeframe install so other people get the benefit of upgraded users.
Most probably, this is caused by the redirect script in .htaccess, read more about it at the following wiki page: proper usage of trailing slash redirects
The use of conditional comments on the HTML tag seem to trigger IE9 Beta to only render on IE9 Standards mode. If you want to use EmulateIE8 mode, use the conditional comments on the body tag. more in issue 125
- The advantage to placing it in the head is that you will track a users' pageview even if they leave the page before it has been fully loaded. Putting the code at the bottom keeps all the scripts together and reinforces that scripts at the bottom are the right move.
- There could be some cases where very customized analytics is in place and you want that level of control and visibility. But that is not the 80% case. If you are an analytics power user than I'm sure you can adjust the script as necessary.
Script.js should hold your primary application script. It might make sense to store it in an object literal and execute it based on body classes.
Plugins I use for jQuery plugins and other 3rd party scripts myself. I put the jQuery plugins inside of the (function($){ ... })(jQuery); closure to make sure they're in the jQuery namespace safety blanket, especially if they were written by more amateur developers. See also jQuery Plugin Authoring
Remove the two lines of jQuery stuff from the index.html and the little bit inside plugins.js. I think you can handle that. :)
These styles are used when the page is printed. In fact all browsers (IE6+) can support the @media print { syntax within a file. Boilerplate ships with a set of styles that reduce complexity and make the printed page more obvious.
Some of your users might have installed the Skype browser extension, which detects phone numbers and lets them automatically dial them with a click. Disabling change of style is documented here.
It is a known issue for IE8 and below. Try using either :active or pseudo-focus script to fix it.
We have been looking into it. You can keep your eyes peeled on this issue for updates.
Firebug and Chrome Dev tools offer profiling, but there is no easy way to profile IE6 and IE7. The YUI profiling script that is integrated can identify parts of your code that take an extra long time to run. If you're focused on providing the most responsive experience possible (you should be!) then profiling should be part of your development workflow.
Why don't we use "ajax.googleapis.com/ajax/libs/jquery/1/jquery.js" so the newest version is automatically loaded?
Because:
a. the latest version of jQuery may not be compatible with the existing plugins/code on the site, version update should be a conscious decision
b. the latest version has a very short max-age=3600 compares to the specific version of max-age=31536000
Nope. So far there have been no critical bugs within our code that we've fixed from version to version. There are some nice changes that reduce your stress, but updating your HTML or CSS to the new stuff is probably more effort than it's worth.
However, the .htaccess and Build Script you probably didn't edit and therefore can be dropped into your existing sites with little hassle and likely a significant reward. So feel free to update those, and also update your Modernizr and jQuery versions to the latest versions they have.
Why sure it is. The markup is a bit more friendly to validation in HTML4, but with enough tweaks you can make it validate fine in either. An important thing to point out is that the browser doesn't really care which doctype you have (just as long as you have one). It won't render a page differently just because you switch it from the html5 doctype to XHTML. So it's only for declaring your relationship with the validator.
Less.js is a superset of css, meaning there is no need for a special version. Here is what you do:
- rename the
styles.csstostyles.less - change the linking in your
index.htmlfromrel="stylesheet"torel="stylesheet/less" - link the less.js after the style-files.