Real-time data and DataSift
Posts tagged as:
The following are short (less than 10 minutes) introductory videos to features of the Alfresco Web Quick Start. I plan to record several over the next few weeks covering topics such as installation, renditions, asset collections, user generated content, publishing etc.
{ 1 comment }
Comments now closed – please use the forum.
Documentation – Documentation is in progress and forming here: Web Quick Start Developer Guide , Web Quick Start Install and Config Guide, Web Quick Start User Guide.
UPDATE: Alfresco 3.4.a Community is now available including the Web Quick Start AMP files and web application. See alfresco-community-wcmqs-3.4.a.zip here or the QS is listed as an install option from the main Alfresco installers e.g. alfresco-community-3.4.a-installer-win-x32.exe.
We have just merged the Web Quick Start (QS) files to HEAD in preparation for the 3.4 Community release at the end of September. Once complete, the QS will have its own installers and documentation, however I thought I would provide a quick overview of some of the features that the QS provides for those who want to take an early look.
As with anything within the HEAD code line, it comes with a warning that this is work in progress, and is subject to regular change.
The Web Quick Start is a sample application built on the Alfresco platform. It provides an end-to-end WCM example including an authoring and publishing environment using Alfresco Share and a web application built using Spring MVC, Spring Surf and OpenCMIS. The web site is delivered dynamically using Alfresco as a CMIS runtime.
The primary design goals of the QS are to illustrate the power of the Alfresco platform in an easy-to-install package and to provide developers with a strong starting point for their Alfresco implementations. Both of these goals are fundamentally aimed at getting both business people and developers up and running with the Alfresco WCM platform in as short a time as possible. The Alfresco core product has not been changed in any way, just extended by plugging in content model, behaviours, workflows, etc using the many standard hooks provided by the Alfresco product.
The QS website will eventually be available in three flavours for different vertical markets, however the version in HEAD currently is loosely modelled on a Finance news site, but with the intention that this can be re-purposed very easily.
{ 15 comments }
Below are the slides from the Alfresco WCM Roadmap webinar that covered:
The webinar can be viewed here.
{ 2 comments }
Recently I have been asked a few times for an example of how to copy content from the DM Alfresco repository into the AVM (WCM) repo, so I thought I would post a simple example using the JavaScript API to help people get started. It can be a little tricky getting the paths etc correct if you are new to Alfresco, so hopefully this will assist.
The 3.1 JavaSccript API wiki page shows the required parameters:
ScriptNode copy(ScriptNode source, ScriptNode destination, String name)
Download the example web script here. This web script is based on some example code taken from the Alfresco Forge project – FlexSpaces which contains some great examples of WCM web scripts.
**NOTE: This articles uses features found in HEAD which are considered to be work-in-progress. This article is for demo purposes only.**
In this article I will look at deploying and consuming WCM content from a SURF web application. To make this very simple, we have created a standalone Tomcat 6 bundle which has an example SURF web application pre-configured (thanks to Michael Uzquiano for all the assistance!). This is the same web app as used in the previous articles, so all previous material is still relevant.
Once the Tomcat bundle is deployed and your WCM instance configured, you will have working examples of:
Initially I will describe the steps required to get up and running, and then I will dissect the configuration so that we fully understand how it is working.
{ 19 comments }
During part 1, the process of creating a simple web page using the SURF framework was discussed detailing creating a basic template and various components. Next I will look at adding additional pages and building some simple navigation utilising SURF’s “Page Association” features.
{ 5 comments }
This article is a step-by-step guide to manually building a simple standalone web site with the SURF framework. This will familiarise you with some of the major components and building blocks used by SURF and provide a good foundation for understanding how Web Studio works under the covers.
As described by the Alfresco Wiki – Alfresco Surf is a lightweight, scriptable web framework built on top of Alfresco’s Web Script and Templating runtime. It is packaged as a single WAR file meaning it can exist as a standalone application. One of the nice things about the SURF framework is that you do not HAVE to use Alfresco, or any other data source to construct a web application, so for the purposes of this example, we will simply construct a basic standalone website without using Alfresco. We will take a static HTML web site template, componentise it and demonstrate loading different areas of the page using very basic Web Scripts.
[click to continue…]
{ 10 comments }
Here is a very simple example of using alf:parseXMLDocuments with both XSL and Freemarker. This example will effectivley load all XML output files from the root dir of type ‘blog-article’ and complie them into an output rendition.
Download the example files here or [click to continue…]
{ 10 comments }
When creating an XML asset using a Web Form, it is sometimes required for an element of the output XML file, to be used within the output path. For example, if it was required that the save directory was input by the user. The examples below shows two output path strings that could be used to acheive this. In this example the “region” element is a user input within the web form, and the produced XML file is saved into this folder within the users sandbox.
{ 2 comments }