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.

Alfresco Dynamic Website

tdombos

I have found the following page in the wiki http://wiki.alfresco.com/wiki/Alfresco_Dynamic_Website , but I could not find the project in Forge. Does anybody know anything about it?

Find more posts tagged with

Comments

uzi

Hello,

I'm one of the folks working on the project and it hasn't been committed to the Forge yet. I expect that we will do that by the second week of March and that it will consist of an AMP file and documentation.

We'll post more information to the Wiki as soon as it becomes available.

Michael

rscheele

This looks pretty great!

Who are the people behind this and how long have you been developing? Is development going to be continued on a regular basis?

Looks absolutely promising to leverage the current WCM capabilities of Alfresco and introduce 'site management' functionality.

rscheele

Any more news on the expected release date for the Forge?

rscheele

Okey, so you are actually saying that the new web client in 3.0 will be ADW (Alfresco WCM) managed? And the technology of the ADW project will be (partially) integrated into 3.0? And the april release will be the integrated functionality?

Hope i hear from you soon!

rdanner

[EDITED TO REFLECT CORRECTION FROM ENGINEERING]

The 3.0 Web Client will in fact sit upon a consolidated model based on ADW and the new UI framework prototype - and will use the webscript component-based framework prototyped by engineering i.e. webscripts + pagerenderer + some additional concepts from ADW - it will not use the component framework from ADW. It will probably use the site builder API and JavaScript root objects from ADW.

Alfresco 3.0 Community is scheduled for late July (see JIRA, under "Project Slingshot").

ADW will likely be made publicly available for testing by users of Alfresco Community 2.9 sometime around April once the final design is decided upon, the code is refactored, and we're confident that the framework is sufficiently "settled" so that anything developed on it stands a good chance of being more-or-less compatible with 3.0 with minimal changes.

Capish?

I'm glad you're as excited as we are. This is really cool stuff!

Cheers,

– Luis

Thanks for the clarity Luis!

gary2

I was wondering if there is an update on the timeline available for the dynamic website for 2.9?

lucien2046

Is there any news on the expected release date for ADW?

uzi

Hello everyone!

The Alfresco Dynamic Website community project has been a large focus of the company's efforts over the past two months. We've essentially taken it and split it into two projects (one which is the User Interface / GUI and the other which is the Dispatching engine).

The dispatching engine is now completely integrated into Alfresco 3.0. This means that Alfresco 3.0's new Web Client as well as other future Alfresco applications (such as our own Network product, under development) will use this dispatcher to describe pages, templates and components. This is known as Alfresco's Web Framework and it has provided a foundation upon which we can build web applications based on reusable, lightweight technologies like Web Scripts, Freemarker and JavaScript (client and server side).

Thus, the Web Framework portion is fully integrated and will be part of the 3.0 Community and Enterprise releases.

Along with this effort, Alfresco has also begun to invest time to develop a proper front-end UI layer. This UI layer consists of a JavaScript model and a library of functions for working with remote content, describing interactions between client-side components and things like that. Our goal is to have a common library so that our community and customers can build components, templates, themes, pages and all kinds of things that are easily swappable and reusable.

In fact, to be somewhat assertive, our goal is to make it so that our users can swap and install components with simple drag and drop actions. Since everything is based on Web Scripts and Freemarker, we can handle all of the dynamic loading and installation. All of that, without any server restarts.

In terms of ADW, this means that we're presently reworking the Ext dependencies into our new client-side UI framework. The main reason is that we want to give our users a single way to develop components without binding them into a particular UI framework. We also don't want to prevent them from using a particular framework. And, as noted, there are unfortunate licensing issues with Ext that made it impossible for us to bundle it with our distribution.

The timeline for an Enterprise release of ADW is about to be announced. The 3.0 team has been making incredible progress and we're very excited about how our various efforts have merged around a consolidated experience. ADW, in that sense, will position as a "visual design tool" (if you will) for adjusting or customizing existing Alfresco web applications. It will also, of course, allow you to build brand new web applications from the ground up.

Indeed, one interesting objective to ponder is the idea that Alfresco Dynamic Website could be used to build the Alfresco 3.0 web client. Provided that you already had the components in a library, you should be able to drag and drop them into place and build the very same application (or customize the look and feel to your preferences).

Stay tuned!

Michael