MatrixAdapt | Logiciel de gestion d'Entreprise, Création et référencement des sites web

salam every one, this is a topic from google web master centrale blog: Webmaster level: All

Great code has many attributes. It’s effective, efficient, maintainable, elegant. When working on code with many developers and teams and maybe even companies, great code needs to also be consistent and easy to understand. For that purpose there are style guides. We use style guides for a lot of languages, and our newest public style guide is the Google HTML and CSS Style Guide.

Our HTML and CSS Style Guide, just like other Google style guides, deals with a lot of formatting-related matters. It also hints at best practices so to encourage developers to go beyond indentation. Many style guide authors know the underlying motivation from the question whether to describe the code they write—or to prescribe what code they want to write. Not surprisingly then, in our HTML and CSS style guide you’ll find both (as much as you’ll still find a lot of different development styles in our not entirely small code base).

At this time we only want to introduce you to this new style guide. We hope to share more about its design decisions and future updates with you. In the meantime please share your thoughts and experiences, and as with the other style guides, feel free to use our style guide for your own projects, as you see fit.

Written by Jens O. Meiert, Senior Web Architect, Google Webmaster Teamthis is a topic published in 2013... to get contents for your blog or your forum, just contact me at: devnasser@gmail.com

Seo Master present to you: By Dion Almaer, Google Developer Programs

Phew, I am still getting over Google I/O. It is interesting to be on the inside and see the build up to the event itself. We were getting excited to hold our largest event with the developer community to date. It didn't dissapoint, and I was very happy to see developers from all walk of lives and companies. I met programmers from Apple, Microsoft, Adobe, Yahoo!, MySpace, and I could keep on going.

You can check out the keynote below, and videos of the sessions are coming very soon, so check out the Google Developers YouTube channel.



The show started well for me as I got to see a project that I have been passionate about launch, the AJAX Libraries API which has us hosting popular open source Ajax libraries on the Google infrastructure. This release is the first step and we look forward to pushing forward with the goal of aggressively getting libraries that many developers use in browsers as fast as possible. If we are successful then we can start to think of these libraries as a standard library of sorts. The community has already started to build interesting tools around this new service. For example, you can now install a Wordpress plugin that rewrites your page to use your library of choice on Google's servers.

Gears was launched at last years Google Developer Day, and the coming out party for this years birthday was a debranding of "Google Gears" to "Gears" to reflect the community effort. Talks by the Gears engineers showed new APIs in the works, how we are working with HTML5 and standards, Gears for Mobile demonstrations, and the MySpace Messaging launch that uses Gears to enable a new search feature that offloads processing from their data centers and gives lightning fast results.

App Engine came out in the keynote sharing the fact that anyone can signup now, the expected pricing model (important to note that the starting point will ALWAYS be free), and new APIs that work with Email and Memcached.

The Geo world had another set of news. Google Earth can now be used in the browser thanks to a new plugin that allows you to add a quick line of JavaScript to your Maps API code to see it in action.

Ben Lisbakken wrote a piece on his application that uses App Engine, Local Search, and Maps to make static maps interactive.

Finally, in housekeeping news, the Maps API blog has been transformed to the new Geo Developer Blog, so update your feed readers.

What else?

• Google Web Toolkit 1.5 Release Candidate: The new release candidate is a big one, with big new features. The GWT sessions at I/O were all packed, and I heard a lot of people walking out talking about how the difficult nature of Ajax development means they will be giving GWT a try.
• Google Visualization API update: The "GViz" API was launched within Google Spreadsheets, but now it has been expanded to live elsewhere. This includes a new JavaScript API to create add-hoc data tables on the client.
• Google Contacts API update: The Contacts API now supports contact groups, photos, extended properties, and batch processing

Finally, to end with a bit of fun. Aaron Spangler created something very cool with his 20% time. Along with a colleague, he created Radish an indoor solar-powered calendar display that hooked into Google Calendar and once ever hour updates via epaper.

Check it out:

2013, By: Seo Master

Seo Master present to you: A very common effect in jQuery is the fade effect that hides or shows an element by fading it, and we can use it in many ways as for example in the blog's navigation. The following script does just that, by loading the page with a fading effect when we browse on internal links that are in the blog, such as post titles, labels links, archive, navigation links, etc..
You can see an example in this demo blog, click on the title of any post and see the fading effect when the page is loading.

How To Implement the Fade In Loading Effect

1) To put this fading effect on your blog, go to your Template > Edit HTML :


2) Click anywhere inside the code area and search for the </head> tag using CTRL + F keys:


3) Then, just above </head> add the following code:

<script src='http://ajax.googleapis.com/ajax/libs/jquery/1.8.2/jquery.min.js' type='text/javascript'/>
<script type='text/javascript'>
//<![CDATA[
$(document).ready(function() {
$("body").css("z-index", "-10");
$("body").fadeIn(0);

$("a").click(function(event){
event.preventDefault();
linkLocation = this.href;
$("body").fadeOut(500, redirectPage); });
function redirectPage() {
window.location = linkLocation;
}
});
//]]>
</script>
<style>
html {
background-color: #F2F2F2; /* Color fading */
}
</style>

4) Save the changes and that's it. In green you can see where to change the color that fades on a loading page.

The original script hides the body of the page while loading, I prefer to change that property with a negative z-index to avoid problems with the search engine robots that may effect the positioning.

Problems?

Consider that such effects could increase the blog loading time, so I recommend using it only when your blog loads fast and does not have too many scripts.

If you already use another version of jQuery remove the other, leaving only this which will be readed first.

If you are using Mootools or Scriptaculous, then you have to make some modifications to the code in order to be compatible.

If you have another script with a fade effect, then it could interfere with this and you might not see anything on the page except the color fading, in such cases it is better without this script.

You can also use this effect only on some links, for example, if you want to appear only when you click on the post titles in the navigation links (older posts and newer posts), and on the top tabs, then replace this line:

$("a").click(function(event){

With this:

$(".post-title a, .blog-pager-older-link, .blog-pager-newer-link, .tabs").click(function(event){

In some cases, the page can load for a second and then load with the fade effect, this may be "normal" because the browser is slow to read the script on page load.

Apart from these drawbacks, I think it's a very elegant way to load blog pages while browsing them, don't you think?2013, By: Seo Master