'Publishing' content

[jpavel]

Hi Everyone,

Alfresco is content management system… So, I've managed my content… but how will I provide this content to the end user? Say I want to manage content for my web-site. Is there a solution for alfresco repository (or JSR-170 in general) that can provide (publish) that content to the world (in form of "static" web-site, portlets, etc.)

Thanks.

Pavel

[paulhh]

Hmmmm.  Can't say much today, for reasons that will become clear.  Look out for announcements soon.  In the meantime, you can use the content templates features to generate custom html views (take a look in the developer wiki for the developer documentation for the web client).

Cheers
Paul.

[kevinr]

As Paul says an announcement in this area will be coming soon. However, as well as templates you can utilise the fact that all content in Alfresco is URL addressable, and with the new Guest access support, it is easy to formulate URLs that non-alfresco users can view.

Thanks,

Kevin

[ssozonoff]

Is there a solution for alfresco repository (or JSR-170 in general) that can provide (publish) that content to the world (in form of "static" web-site, portlets, etc.)
Pavel

Hi,

What about pluging Magnolia into Alfresco using the JCR api for the time being?

Serge

[steve]

Hi,

Have you read this: http://www.alfresco.org/forums/viewtopic.php?t=947

Steve

[kvc]

Hi,

Have you read this: http://www.alfresco.org/forums/viewtopic.php?t=947

Steve

A bit more on that article:

Our goal is to provide document (unstructured content) and XML publishing (structured content) services atop the Alfresco server.  That includes preview , staging, transformation, and snapshotting capabilities (for rollback).  We also plan to support pushing content via an rsync-like mechanism to (1) a flat file-system if deploying generated HTML pages or (2) a run-time JCR or multiple run-time JCR (An Alfresco JCR or any other).   On that run-time system, you can use whatever content delivery framework you want that can either (1) source from flat HTML or (2) query and render content from a JCR.  Alfresco will also provide (though this is not a requirement for use) its own content delivery framework based on JSF (where we will have pre-built web parts used as part of page templates to retrieve and render content from a JCR, RSS newsfeed, external database, file-system, remote web service, etc.).

So, will we support publishing static HTML?  Yes.  Will we support plugging Alfresco into to another content delivery framework?  Yes (and we actually do that today).  Will we also give you everything you need for a full-fledged WCM system.  Gosh, I sure hope so!  Otherwise, I might wonder why we're working so hard 😉

[pmarreddy]

hi,

when we are talking about publishing , can i expect DITA support in the near future.

thanks prasanth

[kvc]

hi,

when we are talking about publishing , can i expect DITA support in the near future.

thanks prasanth

We plan on providing support for capturing XML according to any DTD or schema.  And so yes, we would expect to provide support for DITA.

[pmarreddy]

capturing XML according to any DTD or schema

does this mean u r going to support topic maps, RDF, etc

and can u give us an approximate time frame for surpporting DITA.

thanks prasanth

[kvc]

capturing XML according to any DTD or schema

does this mean u r going to support topic maps, RDF, etc

and can u give us an approximate time frame for surpporting DITA.

thanks prasanth

There are two parts to our web content management efforts that should assist here:

1.  Enhanced metadata capture
2.  New content deployment capabilities

For the first item, we plan on leveraging our browser-based XForms implementation not only for content creation, but also metadata capture and assignment.  Thus, any arbitrary metadata based on any arbitrary set of rules can be captured on any resource within the Alfresco repository.  For the second item, we intend to build a general purpose replication mechanism to deploy assets between any two JCRs (specifically, between any two Alfresco repositories) or from a JCR to some external system.  This latter case will be handled by exporting assets to a file-system or on a custom basis by building your own unique adapter to import content from our replication service to your own non-JCR legacy repository.  This replication mechanism should also allow you to apply arbitrary transformations on the data prior to distribution using a pluggable transformation services (Freemarker or XSLT).  With this, you should be able to take the retrieve the metadata on assets being deployed and transform into either an RDF or topic map schema.

It would be a good sample for us to provide out of the box, and we'll look into this (no promises at this point). 

For the DITA, we will be releasing support for XML document creation (DITA being an implementation of our new XForms capability) with our preview release sometime this summer.  We look to have more detailed timelines by beginning of April.