Showing posts with label HTML. Show all posts
Showing posts with label HTML. Show all posts

Wednesday, 3 April 2013

Just because you can: GUI icons with pure CSS



// Inspired by an elegant piece of CSS code by +Lea Verou, creating the WiFi code (see it here http://bit.ly/wificss), I searched for other examples of this and found this little gem: A demo of 84 icons created with just CSS by +Nicolas Gallagher.

Nicolas calls it's a "technical exercise" but given that this was done back in 2010 and support for the methods used is much wider now, the code should be working in all modern browsers. 

You can see it in action and dig into the code here http://bit.ly/css-gui-icons

Sunday, 24 March 2013

Improve links to your site on Twitter with Twitter Cards




// Announced since last July, Twitter Cards is Twitter's equivalent (or "answer" if you like tech drama) to the Open Graph. By defining a set of #meta #tags in your #HTML code you can provide instructions to #Twitterin order to display an "expanded" preview of your page, when your page's URL is included in a tweet.Twitter Cards come in 3 types:
- summary: The default card, which includes a title, description, thumbnail image, and Twitter account attribution.
- photo: A Tweet sized photo card.
- player: A Tweet sized video/audio/media player card.

Basically, you can use the first for article pages (think of blogs), the second for pages where the main content is a photo (e.g. Instagram) and the third one for pages of videos (e.g. YouTube).

The structure of the meta tags are similar to #OpenGraph and you can read about it in the official documentation (http://bit.ly/twittercards). While Twitter re-invented the concept of meta tags for describing a page for social media consumption, they acknowledged that having duplicate meta tags is kind of silly, so if you already have the OG tags of title, image, url and description in your code, they will be recognised for their twitter equivalents (you still need to add a couple of twitter tags though).

The feature is still in development, simply adding the tags on your site will not do anything yet. You need to submit a form (http://bit.ly/t-cards-form) asking to be included in the beta.  Twitter promisses to respond to you in "a few weeks". Until then, you can try out your page on the preview tool (http://bit.ly/t-cards-preview). If you have a WordPress blog, you can use the Twitter Cards plugin (http://bit.ly/wp-twitter-cards) which does (almost all of) the job for you.

If you have gone through the process and can share some feedback on how this worked for you, post in the comments :)


Sunday, 6 January 2013

Like a website's palette? Colorfy it!



// As it has been said a thousand times, great artists steal :) If you like the color palette used on a website, you can use Colorfy it to easily find out exactly what it is.

Given a URL it will analyze the source code of the #HTML and #CSS and provide you with a list of all colors used, their frequency and on which files they are mentioned. 

Try it out here http://bit.ly/Sd4mmV

And if you have any app ideas, Colorfy it also provides an open API without any usage limits. 

Friday, 13 April 2012

The future of the web: Instagram

I can haz filterz?

All joking aside, the future of #HTML and #CSS certainly includes advanced graphical capabilities. Some of them are described in a recent presentation given by Vincent Hardy of +Adobe and you can examples of them in the images below.

Of course, in terms of specifications, all of this is in draft at the moment and and most of them currently only supported in under development versions of browsers like the nightly version of Webkit (get it here http://bit.ly/HQb1HR) with an -webkit-filter attribute. And some of the effects are making my Mac mini go wild :)

See the full presentation here (some effects will only work on the nightly Wekbit) http://bit.ly/IsK5D0
Thanks to +Chris Coyier for the link


Google+: View post on Google+

Wednesday, 22 February 2012

Responsive menus: one code to rule them all


If you haven't joined the mobile web yet, you should really start thinking about it. 66% of 24-35 year olds already own web-hungry smartphones in the United States. +Webdesigntuts shows us how you can have one piece #HTML / #CSS code for your menus for both your mobile and "full size" visitors.
Check it out here http://bit.ly/wlFH3i

Saturday, 14 January 2012

Advancing the HTML experience


www.mycookingdiary.com by +Mike Matas is great example of what you can do (and how to do it properly) with #HTML and #CSS today:
- A continuous user experience using AJAX to keep the user engaged. However, each "slide" has it's own URL. This means you can bookmark it, share it, etc.
- Animation - but on user action: Yes, animations can liven up a site. But it should be controllable by the user otherwise they end up being irritating. The user needs to feel he is in control of his experience of your site
- Flexible layout: the site looks great at 800px as well as 1200px
- CSS effects to enhance the visual result: #CSS3 blur is here used to bring the attention to the main content area not as a gimmick
- Keyboard navigation: a small issue for some but shows attention to detail and professionalism

Do you have any more example sites along these lines?

Monday, 26 December 2011

Excellent #HTML5 work!


This really pushes the boundaries of what we consider can be done with HTML :)

Reshared post from +Marcin Wichary
We open sourced the code behind Stanisław Lem doodle and I wrote an article describing it. Hope you enjoy!

http://www.html5rocks.com/en/tutorials/doodles/lem/
http://code.google.com/p/stanislaw-lem-google-doodle/


Embedded Link





HTML5 Rocks - Case Study: Building the Stanisław Lem Google doodle

Tuesday, 13 December 2011

CSS "Magic" :)

CSS "Magic" :)


Embedded Link


Experiments with background-clip: text
Experiments with background-clip: text - Background Image for Text

Sunday, 20 November 2011

Another victory for #HTML5 and #CSS3

The next version of the Kindle books format will support HTML5 and CSS3, moving away from the Mobi format. Of course it continues to be a shame (and a non-starter for me) that Kindle doesn't support #EPUB ...


Embedded Link





Kindle Format 8 Overview
Kindle Format 8 Overview

Friday, 21 October 2011

Designers: drop Photoshop, do it in HTML!

Any designers who can understand HTML raise your hands :)


Embedded Link





Prototyping in code | Feature | .net magazine
Alex Morris, user experience director at Mark Boulton Design, walks us through some of the rationale, the tricks, the processes and techniques you can employ to build HTML prototyping into your workfl...

Friday, 2 September 2011

The HTML validation games continue


And they are not going to end one way or the other. Here is a recent example. Developer/journalist Tristan Louis did a small experiment the other day:

Louis then went on to examine the code of many top Web 2.0 companies to see how they compared. All of them are using UTF-8, and all of them had errors with the validator. Only five out of the 11 sites have made the transition to HTML5, with the rest using XHTML or HTML v4. As he says, "It looks like there is still much room for improve ment in the world of HTML validation."

Full article: The State of HTML5 Validation According to Tristan Louis - TNW.

Of course, HTML validation today is not an easy task, when some parts of the code are not even yours as TNW found

In places where we've embedded Facebook code on our home page, the Validator considers instructions that include the namespace declarer fb: to be erroneous. What's more, every part of those instructions generates a single error, so the entire instruction line may be deemed guilty of ten separate counts or more of infraction. The screenshot above shows one example of an attribute (among many in the same line) that the Validator claims doesn't exist, because the fb: namespace declaration doesn't exist in the specification. So when Facebook doesn't comply, we're guilty by association.

Full article Who's Validating the Validators? Reassessing HTML 'Compliance' - TNW

All in all, there will always be the need from big (private or public) organizations to ensure some level of quality (in the eyes of executives with no understanding of the medium). So HTML validation will continue to be another checkbox in a requirements list. At the same time, browsers will continue to evolve and add new features and major sites like Facebook will continue to do what suits them best (meaning that you will have non-validating code from Facebook on your site). It's a game you can't win but one we will continue to play...