You are viewing a plain text version of this content. The canonical link for it is here.
Posted to svn@forrest.apache.org by cr...@apache.org on 2007/05/09 08:06:28 UTC
svn commit: r536434 -
/forrest/trunk/site-author/content/xdocs/docs_0_90/glossary.xml
Author: crossley
Date: Tue May 8 23:06:28 2007
New Revision: 536434
URL: http://svn.apache.org/viewvc?view=rev&rev=536434
Log:
Add the Plugins (#plugins) entry.
Modified:
forrest/trunk/site-author/content/xdocs/docs_0_90/glossary.xml
Modified: forrest/trunk/site-author/content/xdocs/docs_0_90/glossary.xml
URL: http://svn.apache.org/viewvc/forrest/trunk/site-author/content/xdocs/docs_0_90/glossary.xml?view=diff&rev=536434&r1=536433&r2=536434
==============================================================================
--- forrest/trunk/site-author/content/xdocs/docs_0_90/glossary.xml (original)
+++ forrest/trunk/site-author/content/xdocs/docs_0_90/glossary.xml Tue May 8 23:06:28 2007
@@ -100,11 +100,28 @@
<item id="plugins">
<term>Plugins</term>
<definitions>
- <definition></definition>
+ <definition>
+ A Forrest Plugin is a set of resources and configuration files that extend the functionality of Forrest.
+ Plugins are a way of extending Forrest to satisfy site-specific needs.
+ The core of Forrest handles certain processing via the
+ <link href="#sitemap">sitemaps</link> in main/webapp/*.xmap files.
+ The main sitemap mounts a plugin sitemap from each declared plugin.
+ For example an input plugin might handle projectInfo source documents
+ to convert them into the <link href="internal-xml">internal document format</link>
+ for further processing, while an output plugin would concern itself
+ with generating output PDF documents. Nice <link href="#SoC">Separation of Concerns</link>.
+ If no plugin is found to handle a certain document type, then processing falls back to the core.
+ </definition>
</definitions>
<notes>
<item-note>
<link href="site:plugins/index">Plugins index</link>
+ </item-note>
+ <item-note>
+ <link href="site:plugins/using">Extending Forrest with Plugins</link>
+ </item-note>
+ <item-note>
+ <link href="site:plugins/infrastructure">Plugin infrastructure</link>
</item-note>
</notes>
</item>