The official documentation is at: http://docs.alfresco.com
Alfresco 2.2 now adds greater configurability for how sites are configured for test and live deployment. Our enhanced deployment supports includes capabilities for enabling site preview for non-Java, non-virtualizable websites and web applications via shared pools of remote test servers that are dynamically allocated and de-allocated, and now supports advanced run-time server deployment options such as multiple deployment target for each file system receiver and source path and path exclusion parameters. 2.2 also adds support for archives of deployment reports for rich audit trails. For more detail on our new deployment capabilities, now feature complete and available for test by enterprise customers, please read here.
Alfresco 2.2 now adds greater configurability for how stores and store versions are accessed via CIFS. 2.2 now supports filtering of available stores by store type, version, and user role. For more information on upcoming 2.2 AVM/CIFS configuration enhancements, please read AVM/CIFS Configuration Guide.
Based on popular demand, 2.2 extends the indexing and search support for both Staging sandboxes and deployed repositories with new end-user search support in the Alfresco web client. In 2.2, Alfresco users can do a simple search in both a Staging sandbox and a user sandbox. Because only content checked-in and snapshotted in Staging is indexed for searching, search within a user sandbox returns just those items currently available in Staging, filtering out any items a user may have deleted within their sandbox (this to ensure that any resource in the search results is actionable in terms of edit or preview). Any new items added in a user's sandbox, however, will not be visible within the search results screen. These assets instead can be found via the Modified Items listed.
Users can execute a simple search by entering keywords in the textbox located in the upper-right-hand corner of the title bar for any Staging or user sandbox they are browsing:
After clicking on the search icon, users will be presented with a paginated results list along with relevant action (view properties and preview in read-only Staging sandboxes; full set of actions including edit and delete in user sandboxes where a user has permission). In addition, folder paths where the content is located is also displayed, and clickable to take a user directly to that section of the website:
Also within the web client, when browsing a Web Project, users in 2.2 will also have pre-canned search queries available directly from their list of Web Forms. In addition to having immediate access for creating a new content item, users can also immediately browse a list of all existing items created using a particular form to edit or delete without having to know anything about the underlying folder locations in which these assets are stored:
After clicking Browse Content, users will see a listing of all XML assets generated using that Web Form:
Alfresco's 2.2 WCM release includes support for creating Web Project templates. These templates can be used to quickly create new websites pre-populated with an existing body of content and pre-configured with Web Form, templates, workflows, and user sandboxes. These pre-configured settings can be modified either when the new website is created or anytime afterwards using the Edit Web Project Settings Wizard.
When creating any new Web Project, on Step One of the Create Web Project Wizard, you can now mark the Web Project as a template for use as a baseline for future projects:
When creating any new Web Project, on Step Two of the Create Web Project Wizard, you can now choose to create a blank Web Project (what happens in Alfresco 2.1.0E and earlier) or baseline off one of your marked templates. You can also choose to view all Web Projects at the bottom of the screen to baseline your new site off any existing site, whether marked as a template or not.
After selecting the template, you can click next and go through the remainder of the Create Web Project Wizard and confirm or modify the cloned settings from the template for Web Forms, templates, workflows, and users. Or, immediately after selecting the appropriate template, simply click Finish and immediately go into the newly created and configured Web Project and start working using the pre-configured body of content and Web Forms.
To later change anything related to your newly created Web Project, you can always re-run the Edit Web Project Settings Wizard to update any settings you inherited from the parent Web Project template.
Web Project Templating makes use of the AVM's underlying branching capability. The AVM (the underlying Subversion-like repository implementation used to support web content) supports branching at a file, directory, and store-level. Branching within the AVM is a constant-time activity that requires no incremental disk space. This means that creating a new branch of a body of content takes the same amount of time whether your templated Web Project has a pre-set body of content of 10 assets, 1,000 assets, 10,000 assets or more. And because it takes no incremental disk space, spinning off multiple instances of a base template (for example for regional marketing sites) is not only fast, but cheap.
When Web Projects are created, the Create Web Project Wizard by default creates one AVM store called Staging, and one store for use by each user invited to the Web Project. The Staging store in 2.1.0E and earlier is created as an empty store and each user store after creation is populated with a single layered directory at the root of the store that points to Staging. This layered directory in each user store ensures that any content promoted to Staging is transparently available to all users in the Alfresco web client and via CIFS so that they always are working with the latest and greatest approved version of the websites. These stores created by the Create Web Project Wizard are each registered with the Virtualization Server to support website / web app preview are collectively and individually referred to as sandboxes to their use for staging proposed sets of changes to the websites that are independently previewable and non-conflicting.
In 2.2, the Create Web Project Wizard has been modified to branch the content of the base Web Project to pre-populate the Staging store of the new Web Project. In this case, the entire Staging store of the source Web Project is being branched with the new Staging store as its target. Branching within the AVM is much more granular; however, for fast and efficient cloning (and later synchronization to updates) of a Web Project, store-level branching is what is used to support this new feature.
The remainder of the Create Web Project Wizard continues working as it normally does: creating user stores with a layered directory that points to Staging. Because that Staging store is now pre-populated with a branch body of content, those user sandboxes now have an immediate context for your Publishers to create and modify Web Pages.
Alfresco 2.x will focus on enabling business-users to create enterprise mash-ups using new Web Script-based Alfresco Web Components. Alfresco WCM will provide a simple interface for business users to create new mash-ups based on templates and easily add and customize web pages using Web Forms. Alfresco 2.2 WCM will also provide a default site template for a simple mash-up site and have a variety of enhancements for Web Developers, Web Designers, Content Managers, Content Publishers, Content Contributors, and Content Reviewers to make getting up and running with Alfresco WCM fast and easy.
PLEASE NOTE: This page is a work in progress, and does not represent a commitment by Alfresco. Actual product plans will vary significantly from this list, although this list is indicative of those items that are under current exploration. Actual release will be significantly scoped down from this expansive list of feature requirements.
Web Developers need the ability to:
Web Designers need the ability to:
Content Managers need the ability to:
Content Publishers need the ability to:
Content Contributors need the ability to:
Content Reviewers need the ability to:
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.