zen-garden

(Difference between revisions)

Jump to: navigation, search
(Interested parties)
Current revision (11:26, 22 September 2013) (view source)
m (Reverted edits by I MADE THOUSANDS OF ACCOUNTS IN MICROFORMATS WIKI GO TO CHECK OUT THE USER LIST ([[User talk:I MADE THOUSANDS OF ACCOUNTS IN MICROF)
 
(11 intermediate revisions not shown.)
Line 5: Line 5:
Developers of microformat-savvy tools would also benefit from common idioms for presenting and editing microformatted data (for example, consider the impact of Apple's Address Book person-layout/edit view on many other Mac applications).
Developers of microformat-savvy tools would also benefit from common idioms for presenting and editing microformatted data (for example, consider the impact of Apple's Address Book person-layout/edit view on many other Mac applications).
-
Unlike the original Zen Garden, Javascript may also prove essential to unlocking designers' flexibility: people have expressed interest in hooking hCards to maps, or [http://web.mit.edu/glasser/www/JSCalendar/ this example of a renderer for hCalendar] [http://web.mit.edu/glasser/www/JSCalendar/hcalendar.html grid views].
+
Unlike the original Zen Garden, Javascript may also prove essential to unlocking designers' flexibility: people have expressed interest in hooking hCards to maps, or [http://code.google.com/p/js-hcalendar/ this example of a renderer for hCalendar].
== Interested parties ==
== Interested parties ==
Line 42: Line 42:
** Will also be involved with any promotional or editorial aspects, if necessary.
** Will also be involved with any promotional or editorial aspects, if necessary.
-
* [[User:ShawnDrew|Shawn Drew]] (http://www.shaztronics.com)
+
* [[User:ShawnDrew|Shawn Drew]] (http://shaztronics.com)
** Designer/Developer
** Designer/Developer
** I agree to help by (co)developing PHP implementation
** I agree to help by (co)developing PHP implementation
 +
 +
* [[User:MichaelOwens|Michael Owens]] (http://michaelkowens.com)
 +
** Designer/Developer (PHP/MySQL, CSS/XHTML, and JS/AJAX)
 +
** I agree to help by (co)developing the PHP implementation
 +
** I will contribute to the front end JS/AJAX development
 +
** I have developed numerous microformat-enhanced sites that may already have usable code snippets
== Planning ==
== Planning ==
Line 65: Line 71:
*** +1 [[User:RobertBachmann|Robert Bachmann]]
*** +1 [[User:RobertBachmann|Robert Bachmann]]
*** +1 [[User:Phae|Frances Berriman]]
*** +1 [[User:Phae|Frances Berriman]]
 +
*** +1 [[User:MichaelOwens|Michael Owens]]
**** '''Microformats Playground''' is current project name. [[User:Phae|Frances Berriman]]
**** '''Microformats Playground''' is current project name. [[User:Phae|Frances Berriman]]
Line 72: Line 79:
* Demo: http://www.randomchaos.com/mfzen/
* Demo: http://www.randomchaos.com/mfzen/
* Source: http://www.randomchaos.com/source/
* Source: http://www.randomchaos.com/source/
 +
 +
=== Project Revival ===
 +
* Demo: http://uf.paulshen.name
 +
 +
This wiki page hasn't been updated in a while and I'm wondering if people are still interested in working on this. The link is to something that I have been working on, open to change. I have not worked on the front end design (that's why it's so plain).
 +
 +
The setup is designed so that most users can get what they want as quickly and easily as possible. Users can explore XHTML code and stylesheets, of which the code can be used for their own sites. Users can "vote" for an entry (XHTML or CSS), one time per IP address (so that users don't have to register). A concept behind the architecture is that visitors shouldn't have to register unless they want a profile which lists their contributions.
 +
 +
Visitors (registered or not) can contribute XHTML segments or CSS stylesheets corresponding to a XHTML segment. By default, the submitted entries are accessible but are not in the main directory until "approved" by an administrator. Some design decisions are how the entries (XHTML and CSS) should be identified. Currently, all XHTML entries are "tagged" with items such as "hcard" or "hcalendar" (could be multiple). However, a naming scheme needs to be developed to use the directory listings (whether we use just a "name" or a "description" taxonomy).
 +
 +
It'd be great if we got something running, because I know that at least I would find such a resource useful. Feedback would be appreciated.
 +
 +
[[User:PaulShen|Paul Shen]]
 +
 +
* +1 for revival [[User:ShawnDrew| Shawn Drew]]
 +
** I am also very interested in getting this project going again. Pauls description is similar to what I would like to see in the site.
 +
** http://shaztronics.com/sharedup/mfzen/ - Some of my thoughts
 +
** http://mfzen.com/ - Registered domain
 +
 +
* +1 for revival [[User:MichaelOwens| Michael Owens]]
 +
** I also am very interested in reviving this project. I'd love to get some of us on IRC together to discuss sometime soon. (during Sept 2008)

Current revision

Contents

Microformats Zen Garden

A CSS Zen Garden for microformats is essential for popular adoption. Getting something that "looks cool" for "free" should be a key attraction for convincing authors to "steal" microformatted data and cut'n'paste it into their own sites, and for that matter, to reuse style sheets for microformatted data as well.

Developers of microformat-savvy tools would also benefit from common idioms for presenting and editing microformatted data (for example, consider the impact of Apple's Address Book person-layout/edit view on many other Mac applications).

Unlike the original Zen Garden, Javascript may also prove essential to unlocking designers' flexibility: people have expressed interest in hooking hCards to maps, or this example of a renderer for hCalendar.

Interested parties

People who would be willing to spend time on the garden.

Planning

Open questions

Back end prototype

Coded by Scott Reynen

Project Revival

This wiki page hasn't been updated in a while and I'm wondering if people are still interested in working on this. The link is to something that I have been working on, open to change. I have not worked on the front end design (that's why it's so plain).

The setup is designed so that most users can get what they want as quickly and easily as possible. Users can explore XHTML code and stylesheets, of which the code can be used for their own sites. Users can "vote" for an entry (XHTML or CSS), one time per IP address (so that users don't have to register). A concept behind the architecture is that visitors shouldn't have to register unless they want a profile which lists their contributions.

Visitors (registered or not) can contribute XHTML segments or CSS stylesheets corresponding to a XHTML segment. By default, the submitted entries are accessible but are not in the main directory until "approved" by an administrator. Some design decisions are how the entries (XHTML and CSS) should be identified. Currently, all XHTML entries are "tagged" with items such as "hcard" or "hcalendar" (could be multiple). However, a naming scheme needs to be developed to use the directory listings (whether we use just a "name" or a "description" taxonomy).

It'd be great if we got something running, because I know that at least I would find such a resource useful. Feedback would be appreciated.

Paul Shen

zen-garden was last modified: Sunday, September 22nd, 2013

Views