Obsolete Pages{{Obsolete}}
The official documentation is at: http://docs.alfresco.com
Alfresco Share is a new application from Alfresco, providing collaborative content services built on Alfresco's core repository and the new Alfresco Web Framework.
Absolutely not. It is complementary to our core document and web content management capabilities - both areas where we continue to invest as well.
Slingshot is the internal project name we have been using for Alfresco Share.
Yes and yes: the Alfresco Surf Platform is an enterprise-class web application and site assembly framework. It's built on the Web Scripts features that were introduced in 2.1.
The Web Framework is the internal project name we have been using for Alfresco Surf Platform.
In a word, extensibility. JSF was the right choice when the original Web Client design was completed. Over time, we realized that it was too difficult for Alfresco and it's customers and partners to extend.
No. Alfresco Share (project name Slingshot) is a new application that can be used along side the existing Web Client. The current Web UI will continue to be available for pure play Document Management and WCM applications. The Web Client is also required to perform some of the more advanced actions in Share document libraries such as maintaining rules.
Not initially. The Alfresco Share application was built to address an Extranet application use case. It introduces a new User Interface design, interactions, and components. These features will be built out over time to accommodate more scenarios.
Customers can reuse existing content managed by Alfresco by moving / copying content from any spaces in the Web Client to the Document Library portion of Alfresco Share. Note: Any rules defined on the spaces moved / copied *will* continue to work.
Administrators can access Share sites from the Web Client to perform actions not initially available from the Share interface. Standard users should use the Share client only.
This type of access is analogous to system folders in Windows, i.e. only experience users should make changes to system folders, in the same way, only experienced Alfresco users should use the Web Client against Alfresco Share Sites.
Yes, there are number of enhancements to the core repository in the areas of performance, integrity and support including:
We are also looking to address performance issues with versioning. We hope to complete this in the 3.0 timeframe.
We are focusing our efforts on the new Alfresco Share UI. Moving forward, we plan to provide all the Document Management and WCM capabilities in the Alfresco Share UI.
Any Web Client enhancements will therefore be carefully targeted at addressing specific issues. For 3.0 we will be providing new user interface components to allow the management of permissions within a Web Project.
For the WCM Web Client:
For the 3.0 release we are focusing on WCM stability, ease of integration and development and the Alfresco Dynamic Website.
Specific enhancements include:
Not initially, there are a number of issues that need to be resolved before this will be possible. However, MT support for Alfresco Share is on the roadmap for possible inclusion in the next Labs release.
Ask for and offer help to other Alfresco Content Services Users and members of the Alfresco team.
Related links:
By using this site, you are agreeing to allow us to collect and use cookies as outlined in Alfresco’s Cookie Statement and Terms of Use (and you have a legitimate interest in Alfresco and our products, authorizing us to contact you in such methods). If you are not ok with these terms, please do not use this website.