Author: mmcallis Date: 2008-05-10 01:55:48 -0400 (Sat, 10 May 2008) New Revision: 10770 Modified: docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/urls.xml Log: 7.4. Accessing CMS Content - revising content Modified: docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/urls.xml =================================================================== --- docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/urls.xml 2008-05-10 04:22:52 UTC (rev 10769) +++ docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/urls.xml 2008-05-10 05:55:48 UTC (rev 10770) @@ -67,19 +67,12 @@ </sect1> <sect1> <title>Accessing CMS Content</title> - <para>The CMSPortlet delivers content transparently, without modifying the url displayed. - However, if you wish to deliver binary content (gif, jpeg, pdf, zip, etc...), it is - desirable to display this content outside of the confines of the portal. - <itemizedlist> - <listitem> - <literal>"/content/default/images/jboss_logo.gif"</literal> will display the - <literal>jboss_logo.gif</literal> outside of the portal. This is accomplished as - the portal interprets any path beginning with <literal>/content</literal> as a - request for CMS content. As long as the mime-type is not <literal>text/html</literal> - or <literal>text/text</literal>, it will be rendered independently of the portal. - </listitem> - </itemizedlist> - </para> + <para> + The <emphasis>CMSPortlet</emphasis> delivers content transparently, without modifying the displayed URL. It is desirable to display binary content, such as GIF, JPEG, PDF, ZIP, and so, outside of the confines of a portal. For example, <computeroutput>/content/default/images/jboss_logo.gif</computeroutput> displays the <computeroutput>jboss_logo.gif</computeroutput> file outside of the portal. + </para> + <para> + To display content outside of the portal, the portal interprets any path beginning with <computeroutput>/content</computeroutput> as a request for CMS content. As long as the <computeroutput>&lt;mime-type&gt;</computeroutput> is not <computeroutput>text/html</computeroutput>, or <computeroutput>text/text</computeroutput>, and the path to the content begins with <computeroutput>/content</computeroutput>, the content will be rendered independently outside of the portal. + </para> </sect1> <!-- <sect1>