Have you encountered this problem, you know, when you have no choice but to use an img tag instead of a block type tag with a css background-image in an html page, and these images which not serve style are found indexed?
I found many times in this situation during creating and integrating branding site, and I have to include resizing percentage.
These are the images that construct the page graphically universe but in no way serve the SEO content have no particular meaning with it. However, the image search pages on the search engines find themselves “polluted” by them, rather than proposing relevant content.
Img tag possess two characteristics that the background-image has not :
Automatic detection of dimensions by the browser
Scalability of the image by percentages
I am aware that the first characteristics could be remedied using CSS3 and background-size (cover/contain values) property in particular (but not the second one). However, in a commercial context, the importance is to reach a maximum of Internet users, we limit the application of new and favors standarts and cross-browser compatibility.
The background-image have another quality
They are not indexed by robots
Although it is possible to add a rule entries in the robots.txt file with such a pattern on image names, I do not find it very suitable.
Example of an image is calling “character-noindex.jpg” in “images” folder:
I would find it more appropriate to add to img tags, an attribute noindex = “noindex” like robots meta tag. This would check the flow of indexed images.
< img src = “./ images / character.jpg” noindex = “noindex” alt = “A character used for the style but uninteresting from an SEO point of view” />
I have a question. On a website that I’m building every page has a content block with share buttons and a content block with email subscription placed below the real text.
What HTML elements should I use for this? It is now automatically inserted between the <main> elements, and I really wonder if it should be IN the main element, since those blocks of content are duplicate among all pages. But if it doesn’t belong IN the main element, what should I use in that case?
Specifically, I’m looking for browser versions that first gave basic support to HTML elements, in IE, Firefox, Opera, Chrome, and Safari.
The Mozilla Developer Network is a good resource; however, basic browser support of many elements in this resource are listed as ‘yes’ instead of the first known compatible browser versions. Example: The bottom ‘Browser compatibility’ table of the summary for the (Bold) element.
My name is Willem-Siebe and I hope I found the right place here to have some good discussions about the correct use of HTML5. I’m not sure if I should use one of the three mailinglists or write a post like I do now, please tell me for the next time ;-).
My problem: a typical website design can have a right-sidebar area. Can I use the <aside> element for this?
This example has two sidebars, one sidebar is wrapped in an <aside> element, with this explenation:
you may have noticed that we used an <aside> element to markup the 2nd sidebar: the one containing latest gigs and contact details. This is perfectly appropriate, as <aside> is for marking up pieces of information that are related to the main flow, but don’t fit in to it directly. And the main content in this case is all about the band!
Other good choices for an <aside> would be information about the author of the blog post(s), a band biography, or a band discography with links to buy their albums.
However, for the left-sidebar, they don’t use a <aside> element, with this explenation:
“sidebar1” contains various useful links that will persist on every page of the site, such as “subscribe to RSS” and “Buy music from store”.
In the first explenation they explain: the main content in this case is all about the band!
Can anybody explain me why a RSS (about the band) and Buy Music link (from the band) are not related to the main content (all about the band!).
And when they talk about ‘main’ content, do I think of that on site-level (what is the site about) or really specific on page-level (what is the page about).
In my opinion it is normal use of a sidebar that is has elements, like navigation and advertisements, that will always be there. But when I have to take the above example serious, I can have a problem, because they explain not to use a <aside> element because: that will persist on every page..
Hope somebody would like to contribute to this problem.
I did a project on numeracy for my IT degree in 2010. There are two directionality attributes for text fields in HTML, left to right (ltr) and right to left (rtl). Mathematical sums are processed from right to left. It was my interpretation/understanding at the time that the rtl directional attribute behaved in the opposite way to that of ltr. In the development of my project, I found that with the rtl directional attribute, the cursor had a default right alignment, but remained to the right of the last character entered. This was as I subsequently learned was to preserve the way characters were read in the English language, from left to right. This did not help me in any way with my project. When multiplying long numbers, after multiplying each column, I had to manually move the cursor to the left of the last (numerical) character entered.
It would have been useful at the time, and I still think it would be useful, to create a directionality attribute for mathematical processing. With this attribute (call it ‘maths’ for example), the cursor in a text field would default aligned right, but move one character space to the left of the previously entered character.
When multiplying two numbers like 12345 and 77, as on paper, it would be useful to be able to create a vertical stack of text boxes, right aligned directly under each other. This would I feel greatly enhance web-based learning of basic mathematics.
In many data-driven websites like blogs, social networking sites or any other site with lot’s of content, pagination had become an important part. And there isn’t yet an tag for it. My proposal is a <pagination> tag, which makes it more semantic.
HTML has evolved beyond the original 22 tags; and so has evolved the web and the supporting infrastructure around consuming HTML. Things are getting even more interesting with content being published (and micro-published) and then embedded (videos, widgets, scripts) as content within content. The content within the content (or micro-content) is (a) infrastructure driven, like embedding of scriptlets for web tracking (b) consumption driven, like widgets for news, weather, jobs (c) interaction driven, like videos, slideshows, micro-documents, spreadsheet snapshots and (d) submissions like search forms, data-capture fields, etc.