seen from United States

seen from Brazil
seen from China
seen from China
seen from Netherlands
seen from United States
seen from Netherlands

seen from India
seen from United States

seen from India
seen from Germany

seen from United States

seen from Singapore

seen from United States
seen from United States
seen from United States

seen from Poland
seen from United States

seen from China
seen from Netherlands
Sometimes you just need a home base. We can do that for you. Check out talented musician Jade Michael’s one-page website for a simple design that meets all your needs. @Jade_michael_⠀ ⠀ ⠀ #jademichael #onepage #sitetransition #webdesign #webdesigner #cms #webdevelopment #HTML5 #CSS3 #PHP #Modernizr #canva #inspiration #design #branding
Set custom CSS class prefix for gulp-modernizr
I’ve been trying to figure out how to set the custom CSS class prefix to the Modernizr output using gulp-modernizr (aka Customizr) and it’s quite annoying how undocumented the feature is!
I get a lot of CSS class conflicts using the bog-standard Modernizr CSS classes appended to the html element (.emoji on a WordPress site is probably the biggest one) so being able to change the CSS class prefix is a quick and efficient workaround to enable the CSS class detection method for adapting sites to use CSS-based workarounds for certain features.
After some digging I found the classPrefix option and set it accordingly. Viola! Seems the documentation for Customizr configuration is missing the classPrefix entry, but I see a pull request on the github is still pending from November 2015 with it being added to the README, so there ya go.
Here's my gulp-modernizr task in all its glory:
// Modernizr gulp.task( 'modernizr', function () { return gulp.src( ['./css/**/*.css', './js/**/*.js', './js/lib/**/*.js', // Don't reference dev files '!./js/**/*.dev.js', // Don't reference itself (or minified self) '!./js/lib/modernizr/modernizr.js', '!./js/lib/modernizr/modernizr.min.js'] ) .pipe( modernizr({ classPrefix: 'has-', options: ['setClasses', 'addTest', 'html5printshiv', 'testProp', 'fnBind'] }) ) .pipe( gulp.dest('./js/lib/modernizr') ); });
Update!
There's a gotcha: Modernizr's customizr repo hasn't been updated in a while and lacks the classPrefix thingamajig.
To get it working you need to install the modernizr/customizr with the develop branch selected as a dev dependency in your package.json:
$ npm i --save-dev modernizr/customizr#develop
I Heart Modernizr
I know, I know. Modernizr has been around for a while… and I’ve known about it’s existence for quite a while too! But I didn’t really get it until I picked up a book at our local library called “HTML5: The Missing Manual” and gave it a read. When the author explained the practicality of the tool it’s value because so obvious to me and it truly became a holy shite experience… a lot like when I finally wrapped my head around the whole idea of Javascript objects and their usefulness.
For those of you who still haven’t decided to give it a test drive I’d like to outline what I found to be so awesome about it! CSS3 is all kinds of awesome but that awesomeness doesn’t always translate across the different browsers like you would hope it would. One of my favorite CSS3 properties is background-size:cover. The simplest way to explain what that does is that It takes an image and stretches it to fit the size of it’s container. But the background-size property isn’t supported in popular browsers like windows 7 and 8… so if you don’t do anything to correct that problem, an ugly blank space appears where you were hoping to show off the snazzy awesomeness of your well considered image.
To solve this problem you can load Moderizr into the head of your HTML document following your JQuery CDN and Modernizr’s javascript will add classes to the HTML tag in your document so that you can target specific CSS3 (and other, if you so desired) properties. So if you went to Internet Explorer 7 and you used your web developer inspector to look at your source code you would see a bunch of classes added to the HTML tag and one of of those classes would be called no-backgroundsize. Modernizr add’s a slew of classes by the CSS3 property names that you want to target for each different browser with a “no” attached to the property name if the browser your viewing your page on doesn’t support it. So all you would have to do is use that property in your CSS file to provide an alternative solution/fallback for how Internet Explorer 7 handle that particular page element and voila! Problem solved.
The discovery of Modernizr’s usefulness has made me so happy and has helped me to become a much better developer and so I wanted to do my best to explain it to the next guy that decides to read my post. I hope you all found this info useful. Thanks for reading and keep pushing the web forward my friends!!
Detectizr extends Modernizr for gathering Visitor Tech Info
The Modernizr detection library is a popular way of pulling which features can run properly for which users. This allows developers to serve up webpages that offer the highest level of capability to individuals. Since Modernizr is open source it does invite developers to create their own additions. One such extension is called Detectizr which collects technical info like browser version, device screen size, operating system, and more. The project’s GitHub page actually lists all possible features which include: * device * device model * screen size * operating system + OS version * browser type + browser version * browser engine * browser plugins Many developers hand this task off to backend languages such as PHP or Ruby. But a frontend scripting lang like JavaScript can easily handle the task – and with Detectizr it’s even easier! The project was created by Baris Aydinoglu and released for free on GitHub. If you’re a big fan of Modernizr then check out this JS extension and see if you can put it to good use. The minified version is ~8kb with options to enable/disable certain unused features at your whim. For setup info & code snippets check out the GitHub repo for everything you need to know about Detectizr. Read More at Detectizr extends Modernizr for gathering Visitor Tech Info http://dlvr.it/CMqYqr www.regulardomainname.com
Modernizr 3: A new release and website After what appears an eternity to us and the wider development community we are ecstatic to announce the release of Modernizr 3.0! This is a massive release and from our last release almost 2.5 years have passed - an unacceptable timeline. We plan to fix this and have faster releases where it makes sense.
How to: HTML5shiv vs Dean Edwards IE7-js vs Modernizr - which to choose?
How to: HTML5shiv vs Dean Edwards IE7-js vs Modernizr – which to choose?
HTML5shiv vs Dean Edwards IE7-js vs Modernizr – which to choose?
I’m looking to build my first HTML5 site and have been looking at working with IE.
There is html5shiv, Dean Edwards ie7-js and then Modernizr. Are these all largely the same? I’m confused about which route to go.
Answer: HTML5shiv vs Dean Edwards IE7-js vs Modernizr – which to choose?
Easiest way to start a new HTML5 project is…
View On WordPress
Fixed What is the purpose of the HTML "no-js" class? #dev #it #asnwer
Fixed What is the purpose of the HTML "no-js" class? #dev #it #asnwer
What is the purpose of the HTML "no-js" class?
I notice that in a lot of template engines, in the HTML5 Boilerplate, in various frameworks and in plain php sites there is the no-js class added onto the <HTML> tag.
Why is this done? Is there some sort of default browser behavior that reacts to this class? Why include it always? Does that not render the class itself obsolete, if there is no…
View On WordPress