svn commit: r379919 - in /incubator/graffito/trunk/site/xdocs: tech-overview.xml usecases.xml

[cl...@apache.org]

Author: clombart
Date: Wed Feb 22 13:33:17 2006
New Revision: 379919

URL: http://svn.apache.org/viewcvs?rev=379919&view=rev
Log:
Still working on the documentation

Modified:
    incubator/graffito/trunk/site/xdocs/tech-overview.xml
    incubator/graffito/trunk/site/xdocs/usecases.xml

Modified: incubator/graffito/trunk/site/xdocs/tech-overview.xml
URL: http://svn.apache.org/viewcvs/incubator/graffito/trunk/site/xdocs/tech-overview.xml?rev=379919&r1=379918&r2=379919&view=diff
==============================================================================
--- incubator/graffito/trunk/site/xdocs/tech-overview.xml (original)
+++ incubator/graffito/trunk/site/xdocs/tech-overview.xml Wed Feb 22 13:33:17 2006
@@ -32,11 +32,13 @@
 			  	</ol>
 				</p>
 			</subsection>
-			<subsection name="Component Design">
-				<p>Graffito is, in fact, a flexible set of components, services and portlets which can transparently support different CMS engines.
-				Graffito is packaged with a default cms repository implementation based on OJB but it also supporting a plugin design. You can write your own plugin in order to access to a propriatary CMS repository. When our JCR mapping tools will be ready, the default OJB implementation will be replaced by a full JCR implementation. </p>
+			<subsection name="Component and repository plugins">
+				<p>Graffito is, in fact, a flexible set of components, services and portlets which can transparently support different CMS repositories.
+					
+				<p>The Content Management resolution is performed in a pluggable fashion; consequently, J2EE applications are independent of underlying CMS technologies. New or updated technologies can be substituted without requiring modifications to the application itself. Thanks to the Graffito plugin design, an implementation for a particular CMS technology is determined at run-time (see the architecture detail to get more information).</p>
+					
+				Graffito is packaged with a default cms repository implementation based on a OJB plugin.You can write your own plugin in order to access to a propriatary CMS repository. When our JCR mapping tools will be ready, the default OJB implementation will be replaced by a full JCR plugin implementation. </p>
 		   	
-				<p>The Content Management resolution is performed in a pluggable fashion; consequently, J2EE applications are independent of underlying CMS technologies. New or updated technologies can be substituted without requiring modifications to the application itself. An implementation for a particular CMS technology is determined at run-time (see the architecture detail to get more information).</p>
 			
 				<p>The Graffito components are building with on the <a href="http://www.springframework.org/">Spring</a> framework. Spring is the default service framework for Jetspeed 2 but Graffito can be used in other portal applications or in other kind of Java platform as well.</p>
 			</subsection>

Modified: incubator/graffito/trunk/site/xdocs/usecases.xml
URL: http://svn.apache.org/viewcvs/incubator/graffito/trunk/site/xdocs/usecases.xml?rev=379919&r1=379918&r2=379919&view=diff
==============================================================================
--- incubator/graffito/trunk/site/xdocs/usecases.xml (original)
+++ incubator/graffito/trunk/site/xdocs/usecases.xml Wed Feb 22 13:33:17 2006
@@ -25,12 +25,12 @@
 			<subsection name="The Content Platform">			
 				<p>There is a huge amount of applications that can use Graffito. Some good examples are : </p>
 				<ul>
-					<li>Content catalog like Yahoo style portal : you can classify your content in a virtual content tree which group together different content repositories.</li>
-					<li>On-line content management : web site content is updated directly by the end-users. They can update news, HTML pages and all information which have to be stored into CMS repositories.</li>
+					<li>Content catalog like Yahoo style portal : you can classify your content in a virtual content tree which group together different repositories.</li>
+					<li>On-line content management : web site content is updated directly by the end-users. They can update news, HTML pages, binaries or any kind of content which have to be stored into a CMS repository.</li>
 					<li>Document management : different teams can share documents required for their job in a secure fashion. Following a customized authoriting workflow, they can receive notifications when documents have been updated; takes some actions on the existing documents; and at the end, publish the final publications in different formats (PDF, HTML, Word, ...)</li>
 					<li> Forums, blogs and news management can be also build with the Graffito framework.</li>
 				</ul>	
-				<p>Anyway, you are not limited to those application examples. Depending on your needs, you are free to create your own Graffito applications.</p>
+				<p>You are not limited to those application examples. Depending on your needs, you are free to create your own Graffito applications.</p>
 			</subsection>				
 		
 			<subsection name="Portal Integration">