nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

As we transition to the new Hyland Community, some post links may be temporarily disrupted as we finalize redirects. We apologize for the inconvenience and are working to resolve this as quickly as possible. Details.

Publishing contents

ahhang

Once contents reach the end of the workflow, how do I publish them to web server?

Find more posts tagged with

Comments

mckeanj

Once contents reach the end of the workflow, how do I publish them to web server?

My question exactly! :evil:

ddupmul

Hi,

I'm very new to Alfresco, but this question took me by surprise. I thought that files maintained in Alfresco are on the web. Why would you need to publish them? Or are you publishing to a separate server??

David

rdanner

Hi,

I'm very new to Alfresco, but this question took me by surprise. I thought that files maintained in Alfresco are on the web. Why would you need to publish them? Or are you publishing to a separate server??

David

That really depends on how you are using alfresco. In the pre WCM releases and with the DM/CM components the files are on the server but they are located in the alfresco file store. If you dig around in there you will find this folder to make a poor doc root for a web server. All of versions etc are stored there etc.

Take a look at the WCM roadmap if you are interested in understanding the deployment models.

WCM will provide the ability to manage a website within the repository and provided the infrastructure to support the solution as seen in the preview. Through this mechansim files can be promoted through workflow right to the web because in this case tomcat is your web server.

There are plans to support both models (managed and unmanaged sites).

ddupmul

Thanks rdanner, for the explanation.

It looks like I've got a lot more learning to do!

David

rdanner

Thanks rdanner, for the explanation.

It looks like I've got a lot more learning to do!

David

Me too

Actually I was not sure if you were referring to WCM or the other parts of the web client. They don't use the same repository yet.

kvc

Thanks rdanner, for the explanation.

It looks like I've got a lot more learning to do!

David

Me too Actually I was not sure if you were referring to WCM or the other parts of the web client. They don't use the same repository yet.

With our WCM release, we support the following:

* Publishing of documents from an Alfresco space to a website
* Deployment of approved website content from an Alfresco
    content contribution server (behind the firewall accessible to your
    business users) to one or multiple front-end web servers outside
    your firewall running off an Alfresco repository or served statically
    from the file-system

In an Alfresco space a content rule or workflow can automate the
transformation of a business document into a web-ready format (PDF)
and put that PDF in one or multiple websites. Workflow specific to
that site can be initiated to enable a Content Manager or Content Publisher to (a) review and accept the submission and (b) append
additional metadata on the generated asset needed for that particular
website (launch date, expiration date, target audience, navigation
linking, etc.).

Content approved within Alfresco can take advantage of our upcoming
deployment utility to push changes as static files to a remote file server
for direct serving via a webserver or to a run-time Alfresco repository
for dynamic content delivery.

Please let me know if any additional questions.

Kevin