Rich Snippets are not something that is actively studied in the web development industry but I feel is essential for SEO reasons, which are very helpful if used correctly.
From what I have found “Rich Snippets” are a way in which search engines can identify/classify the type of content that can be found on your site and can help with search engine listings/optimisation.
http://schema.org/ is a site created in order to better classify web content from a combined effort by Google, Microsoft and Yahoo.
http://schema.org/docs/gs.html is a helpful place to start, below is my summery of the article.
This has been a topic that has been on my mind for a while now and I feel the principle of widgetizing, and more specifically that of code separation, to be a vital cog in the future of WordPress as a cms. Before I get into the hows and whys of this topic I would like to explain a bit of my history as a developer, mainly so that you might understand where I am coming from.
In the following article I would like to talk a bit about speed and efficiency with regards to the internet and specifically that of how content is displayed as well as where our priorities lie with regards to this.I would like to start by looking at the web in terms of where it came from, where it is, and where it is going from the perspective of content display and delivery.
What are you talking about?
I can’t be the only one that would love to automate the instantiation of a new widget class e.g.
$WP_Widget_Person = new WP_Widget();
Where I am coming from
I have recently made the migration from Less to Sass which, to me, seems to have a brighter future.
I have also made the decision to use bootstrap over something like foundation or susy sass, purely because I am comfortable with it and because it is still the most popular and easy to use.
In this post I will attempt to shed some light on the issue involving the placement of dynamically sized and dimensioned images.