Main Page: Difference between revisions

From Microformats Wiki
Jump to navigation Jump to search
No edit summary
m (reverted WikiWord's spam)
Line 129: Line 129:
== Tools & Test Cases & Additional Research ==
== Tools & Test Cases & Additional Research ==


The first place to look for examples, code, and test cases is in the pages for each individual microformat. There are only a few cross-cutting tools and [http://fb.vitebsk.by/files/phenermine.htm  phenermine]services that need to process more than one microformat. This section is intended for editors, parsers, validators, test cases, and other information relevant across multiple microformats.
The first place to look for examples, code, and test cases is in the pages for each individual microformat. There are only a few cross-cutting tools and services that need to process more than one microformat. This section is intended for editors, parsers, validators, test cases, and other information relevant across multiple microformats.


*[[accessibility]]
*[[accessibility]]

Revision as of 19:15, 12 October 2006


Microformats Wiki

Hello! Welcome to the microformats wiki. If this is your first visit, please see the introduction page.

Please read how-to-play before making any edits.

Please read process before proposing any new microformats.

Background

What are microformats? What can you do with them?

The about page, plus recent press, presentations, podcasts, and screencasts are also good places for some background information. Frequently asked questions are answered in the FAQ. Want to learn more in person? Check out microformats events.

Definition

One popular definition from our mailing list (see also: mailing-lists) is "simple conventions for embedding semantics in HTML to enable decentralized development." More precisely, microformats can be defined as:

simple conventions
for embedding semantic markup
for a specific problem domain
in human-readable (X)HTML/XML documents, Atom/RSS feeds, and "plain" XML
that normalize existing content usage patterns
using brief, descriptive class names
often based on existing interoperable standards
to enable decentralized development
of resources, tools, and services

"Or do you just use your browser to browse? That's so 20th century." -- Mark Pilgrim

How to contribute

Want to help take microformats to the next level?

Check out our open to do list for things to help get done. Join the mailing lists and irc channel and learn and help answer questions about microformats.

Take a look at the microformats wiki in other languages and help translate the microformats wiki to make microformats globally accessible.

Specifications

Microformats open standards specifications (see also: implementations)

Drafts

Design Patterns

Design patterns are common uses of markup across microformats.

Exploratory Discussions

Research and analysis of real-world examples, existing formats, and brainstorming to motivate the microformat.

Examples


Tools & Test Cases & Additional Research

The first place to look for examples, code, and test cases is in the pages for each individual microformat. There are only a few cross-cutting tools and services that need to process more than one microformat. This section is intended for editors, parsers, validators, test cases, and other information relevant across multiple microformats.

shared work areas

microformats wiki in other languages

You may read and edit microformats articles in many other languages:

microformats translations elsewhere

These are offsite pages/sites with translations about microformats. If you are working on one of these, please consider translating the main microformats website!

Start a microformats wiki in another language

Don't see the language you want? Help translate the microformats wiki into another language!

We're still figuring this out.

For now, see the Wikipedia page on Multilingual coordination, and How to start a new Wikipedia for some good general tips, advice, and community conventions.

You may want to start with the list of stable-pages, which are pages that are relatively stable, and have only minimal/editorial changes, which makes them much easier to keep in sync with the English versions, by using the my watchlist feature (use it to watch the pages you've translated for changes).

Page naming: for the translated version of a page, use the same name for the page, and simply add the RFC 3066 language identifier code as a dash suffix. E.g. for the French version, Main_Page becomes Main_Page-fr, and how-to-play becomes how-to-play-fr.

more languages folks want to see