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.

xml content authoring in (wcm)

pmarreddy

Content Creation
Ability for content publishers to create and modify structured assets (XML). XML authoring will be browser-based and support optional WYSIWYG HTML editing on a field-by-field basis. Support for applying transformation templates for offline content generation and multi-channel publishing.

hi,

1) i like this idea very much, i would like to know that will u guys be providing webservices for creating and authoring structured content(XML)

2) and in general what kind of support are u thinking to provide for webservices. will it parllel current alfresco repository implementation.

3) how about ajax?

thanks prasanth

Find more posts tagged with

Comments

kvc

hi,

1) i like this idea very much, i would like to know that will u guys be providing webservices for creating and authoring structured content(XML)

2) and in general what kind of support are u thinking to provide for webservices. will it parllel current alfresco repository implementation.

3) how about ajax?

thanks prasanth

1. We will be providing a comprehensive set of webservices for interacting with our new forms services. This includes getting a list of available forms by user, group, role, workspace and fetching any specific form to either (a) render to an end-user using Alfresco's default form look-and-feel or (b) embed in your own custom web page / web app.

Our goal is to make any data collection on your website potentially an Alfresco form so that the data can be saved as XML and saved in a secured content repository subject to workflow, version control, auditing, and reporting. Web services is critical as the source Alfresco server may be behind a firewall.

2. Our plan is to parallel the current Alfresco implementation. It is, of course, one integrated product suite built atop a core base platform (the Alfresco server and repository).

3. Looking into it! We will most likely be incorporating and AJAX front end to at a minimum our default forms presentation and potentially other areas of our WCM web app extensions - and ultimately our entire Alfresco user experience (both WCM and DM).

Stay tuned to the Wiki where more details will be published on our AJAX findings and intent.