About Microformats
Microformats are - simply put - a way in which developers can add semantic markup or in other words: meaning to content, so that it is possible for machines to extract this meaningful information from the content.
Support for microformats dramatically improved in 2011 when Bing, Google and Yahoo announced their plans for collaboration known as schema.org. It is an effort to support and create a standard set of microformats for a structured markup so that they are understood identically by each of the major search engines.
So how can this help you? Microformats help search engines to not only see your content, but to understand it as well. By using microformats, you can enrich various kinds of content such as book or movie reviews, restaurants, recipes, etc. This way, the search engine knows that you are describing a specific movie or writing a recipe. Once the search engine can do this it can process content in a much different way than if it were just in plain text.
 |
| Google recipe search |
Google uses microformats to understand various recipes. This allows you to search for a recipe made from specific ingredients, cooking time or even calories. Searches such as these could not be possible if the recipes weren’t marked up using rich snippets or microformats.
What’s the catch?
The major problem with microformats is that they are not particularly easy to implement into content publishing systems. Microformats require rather complicated markup and therefore it is not easy to use them on pages that are edited using WYSIWYG. WYSIWYG editors in general don’t support microformats well and their support is very constrained. Therefore microformats appear mostly on pages that have fixed structure (product description, movie review, recipe, etc.). It is because pages like these are edited via forms not WYSIWYG.
How Bee enables microformats?
In Bee, all content is created using components. These components can be re-used so that you don’t need to repeatedly input your content over and over again.
Components’ markup is fully in the hands of the developer and what’s great is that apart from other systems, they don’t have to be created using schemas. Instead the schema can be created from them.
It means that when you want to create a component that produces a recipe, for example, all you have to do is write the final markup. Add a couple more attributes for Bee to properly recognize the code and Bee will then take care of everything else. It will create the schema and form with full data validation and proper formatting. This allows developers to easily add rich markup to the code.
You can then publish properly marked content anywhere on your site.