twiki - Revision history

Aaronpk: Replace with {{DISPLAYTITLE:}}

2020-07-18T16:33:24Z

Replace <entry-title> with {{DISPLAYTITLE:}}

← Older revision		Revision as of 16:33, 18 July 2020
Line 1:		Line 1:
	~~<entry-title>~~TWiki~~</entry-title>~~		{{DISPLAYTITLE:TWiki}}

	[http://twiki.org TWiki] is an enterprise-grade open-source Wiki platform, used internally by companies like BT, Disney and Yahoo.		[http://twiki.org TWiki] is an enterprise-grade open-source Wiki platform, used internally by companies like BT, Disney and Yahoo.

Tantek: also hCalendar support in the plugin

2011-11-24T01:51:21Z

also hCalendar support in the plugin

← Older revision		Revision as of 01:51, 24 November 2011
Line 11:		Line 11:
	== MicroformatsPlugin ==		== MicroformatsPlugin ==

	The TWiki [http://twiki.org/cgi-bin/view/Plugins/MicroformatsPlugin MicroformatsPlugin] supports [[hCard]] with a little [[xfn]]:		Supports [[hCalendar]], [[hCard]], and [[XFN]].
	* ~~usage:~~ =%HCARD{"WikiName"}% - uses the UserForm data on a user's Topic to create a hCard.
			The TWiki [http://twiki.org/cgi-bin/view/Plugins/MicroformatsPlugin MicroformatsPlugin] supports hCard with a little xfn, and also hCalendar. usage:
			* =%HCARD{"WikiName"}% - uses the UserForm data on a user's Topic to create a hCard.
			* =%HEVENT{start="" end="" url="" location="" summary="" description=""}% - e.g. %HEVENT{start="2011-11-20" url="http://twiki.org/" location="Cupertino Community Center" summary="TWiki helps the enterprise to be agile" description="TWiki Enterprise Collaboration Platform"}%

	For more info see: http://twiki.org/cgi-bin/view/Plugins/MicroformatsPlugin		For more info see: http://twiki.org/cgi-bin/view/Plugins/MicroformatsPlugin

Tantek: see also, move mediawiki specific text to mediawiki page, add section / link to twiki microformats plugin

2011-11-24T01:47:19Z

see also, move mediawiki specific text to mediawiki page, add section / link to twiki microformats plugin

@@ Line 9: / Line 9: @@
 __TOC__
-==Mark up articles with [[hAtom]]==
+== MicroformatsPlugin ==
-The microformats wiki—which runs MediaWiki with a custom skin—uses microformats in the mark-up of the page. Namely, each wiki page (article) is marked up using hAtom, providing common structure for titles, authors, content and so forth.
+The TWiki [http://twiki.org/cgi-bin/view/Plugins/MicroformatsPlugin MicroformatsPlugin] supports [[hCard]] with a little [[xfn]]:
-==Provide ability to insert microformats into pages==
+For more info see: http://twiki.org/cgi-bin/view/Plugins/MicroformatsPlugin
 ==Automatically mark-up recurring data patterns in pages with microformats==
@@ Line 40: / Line 25: @@
 These are directions for development that come to mind straight away, I'm happy to help spec more specific implementation details.

BenWard: /* Mark up articles with hAtom */ Couple of email->wiki corrections/rephrasings

2009-08-15T08:22:00Z

Mark up articles with hAtom: Couple of email->wiki corrections/rephrasings

← Older revision		Revision as of 08:22, 15 August 2009
Line 11:		Line 11:
	==Mark up articles with [[hAtom]]==		==Mark up articles with [[hAtom]]==

	The microformats ~~wiki (http://microformats.org/wiki)—which~~ runs MediaWiki with a custom ~~skin that I developed—uses~~ microformats in the mark-up of the page. Namely, each wiki page (article) is marked up using hAtom, providing common structure for titles, authors, content and so forth.		The microformats wiki—which runs MediaWiki with a custom skin—uses microformats in the mark-up of the page. Namely, each wiki page (article) is marked up using hAtom, providing common structure for titles, authors, content and so forth.

	==Provide ability to insert microformats into pages==		==Provide ability to insert microformats into pages==

BenWard: Created TWiki implementation brainstorming page.

2009-08-15T08:21:14Z

Created TWiki implementation brainstorming page.

New page

<entry-title>TWiki</entry-title>

[http://twiki.org TWiki] is an enterprise-grade open-source Wiki platform, used internally by companies like BT, Disney and Yahoo.

They have a small amount of developer documentation from 2008 concerning support for microformats in TWiki, see [http://twiki.org/cgi-bin/view/Codev/MicroFormat].

This page documents ways TWiki can be enhanced using microformats:

__TOC__

==Mark up articles with [[hAtom]]==

The microformats wiki (http://microformats.org/wiki)—which runs MediaWiki with a custom skin that I developed—uses microformats in the mark-up of the page. Namely, each wiki page (article) is marked up using hAtom, providing common structure for titles, authors, content and so forth.

==Provide ability to insert microformats into pages==

That is, to mark-up an event, person, business and so forth as part of an article, is super-cumbersome. This is something no-one has solved yet, and requires an update to the wiki shorthand mark-up mechanism to allow people to add `class`, `rel` and `rev` attributes. Some attempts have made toward this: The Link Attributes extension for MediaWiki augments the link syntax to allow class, rel and rev. http://www.mediawiki.org/wiki/Extension:Link_Attributes

I've also been working on a possible Markdown extension for the same purpose, that might look something like this, using braces for attributes:

<source lang=text>[Ben Ward](http://benward.me){fn url, rel=me}</source>

To produce:

<source lang=html4strict><a class="fn url" rel="me"></source>

TWiki could actually evolve in a similar way:

<source lang=text>[[http://benward.me][Ben Ward][fn url, rel=me]]</source>

It would also be necessary to allow adding class attributes to arbitrary blocks (p, div, spans etc.)

==Automatically mark-up recurring data patterns in pages with microformats==

You could go further with some common types of data. Mentions of and links to other TWiki users could be fully marked up as hCards.

==Mark up TWiki user profile pages with hCard==

TWiki profile pages, which already generate a certain amount of structured data for URLs, organizations, locations and so forth, should be marked up with hCard.

These are directions for development that come to mind straight away, I'm happy to help spec more specific implementation details.