<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Prospective user question in Alfresco Archive</title>
    <link>https://connect.hyland.com/t5/alfresco-archive/prospective-user-question/m-p/143787#M100591</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;G'day Garey,&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Yes you can do exactly what you describe with Alfresco.&amp;nbsp; In fact I think this is a great first step for bringing an existing static site under management in Alfresco - simply grab the content in it's current state, copy it into Alfresco via CIFS, then configure Alfresco to deploy it to a static docroot.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Once you've got that up and running you can start introducing more advanced features as appropriate - workflow, Web Forms, dynamic runtimes etc.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Cheers,&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Peter&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 23 Oct 2007 03:45:11 GMT</pubDate>
    <dc:creator>pmonks</dc:creator>
    <dc:date>2007-10-23T03:45:11Z</dc:date>
    <item>
      <title>Prospective user question</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/prospective-user-question/m-p/143786#M100590</link>
      <description>I apologize in advance if this has been asked before. I am trying to evaluate Alfresco for use in our organization. We have an established web site with a number of ways to get pages into it. We are satisfied with our presentation, so all we really want is a content repository that has versioning, a</description>
      <pubDate>Mon, 22 Oct 2007 23:07:29 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/prospective-user-question/m-p/143786#M100590</guid>
      <dc:creator>gareymills</dc:creator>
      <dc:date>2007-10-22T23:07:29Z</dc:date>
    </item>
    <item>
      <title>Re: Prospective user question</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/prospective-user-question/m-p/143787#M100591</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;G'day Garey,&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Yes you can do exactly what you describe with Alfresco.&amp;nbsp; In fact I think this is a great first step for bringing an existing static site under management in Alfresco - simply grab the content in it's current state, copy it into Alfresco via CIFS, then configure Alfresco to deploy it to a static docroot.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Once you've got that up and running you can start introducing more advanced features as appropriate - workflow, Web Forms, dynamic runtimes etc.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Cheers,&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Peter&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 23 Oct 2007 03:45:11 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/prospective-user-question/m-p/143787#M100591</guid>
      <dc:creator>pmonks</dc:creator>
      <dc:date>2007-10-23T03:45:11Z</dc:date>
    </item>
    <item>
      <title>Re: Prospective user question</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/prospective-user-question/m-p/143788#M100592</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Do not forget the WCM framework to handle your web site. Might be overkill, though..&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 27 Oct 2007 15:09:57 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/prospective-user-question/m-p/143788#M100592</guid>
      <dc:creator>ronnyt</dc:creator>
      <dc:date>2007-10-27T15:09:57Z</dc:date>
    </item>
  </channel>
</rss>

