Main Page: Difference between revisions

From Microformats Wiki
Jump to navigation Jump to search
m (Reverted edit of KorvinAmber, changed back to last version by Ant)
(→‎Exploratory discussions: - Content Rating)
Line 69: Line 69:
* citation [[citation|effort]], [[citation-examples|examples]], [[citation-formats|formats]], [[citation-brainstorming|brainstorming]], and [[citation-faq|FAQ]]
* citation [[citation|effort]], [[citation-examples|examples]], [[citation-formats|formats]], [[citation-brainstorming|brainstorming]], and [[citation-faq|FAQ]]
* comment [[comment-problem|problem]], [[comment-examples|examples]], and [[comments-formats|formats]] (Some stuff needs to be extracted from [[comments-formats]])
* comment [[comment-problem|problem]], [[comment-examples|examples]], and [[comments-formats|formats]] (Some stuff needs to be extracted from [[comments-formats]])
* content rating [[content-rating-examples|examples]]
* currency [[currency-examples|examples and brainstorming]] {{NewMarker}}
* currency [[currency-examples|examples and brainstorming]] {{NewMarker}}
* directions [[directions-examples|examples]] {{NewMarker}}
* directions [[directions-examples|examples]] {{NewMarker}}

Revision as of 12:39, 27 July 2006

Microformats Wiki

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

Please read process before proposing any new microformats.

Introduction

What are microformats? And what can you do with them? See the about page for an overview, and the introduction page for more info. Recent press, presentations, podcasts, and screencasts are also a good place for some background reading/listening. Frequently asked questions are answered in the faq. Want something or want to contribute? Help with things to-do. Want to learn more in person? Check out microformats events.

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

Specifications

Microformats open standards specifications (see also: implementations)

Drafts

Design Patterns

Design patterns give microformat authors a vocabulary for expressing their ideas consistently with what has already been done. If you're tempted to try your hand at writing a microformat read this first!

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