HTMLResources similar features | Community
Skip to main content
This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by JohnMetzger

Yes and no. Content migrated from the older DPS to the new system, will still have access to HTML resources added in the older system. Users of the content producer API have a path to upload shared resources for a project. The Content dashboard does not currently have a way to upload the equivalent of HTML resources or any assets shared across multiple articles. It's on the list.

4 replies

JohnMetzger
Adobe Employee
JohnMetzgerAdobe EmployeeAccepted solution
Adobe Employee
August 4, 2015

Yes and no. Content migrated from the older DPS to the new system, will still have access to HTML resources added in the older system. Users of the content producer API have a path to upload shared resources for a project. The Content dashboard does not currently have a way to upload the equivalent of HTML resources or any assets shared across multiple articles. It's on the list.

Neil_Enns_-_Ado
Adobe Employee
Adobe Employee
August 4, 2015

Also note that the iOS and Windows viewers support shared resources that were either migrated or uploaded via the APIs John mentions, however the Android viewer doesn't yet. It will soon though!

Neil

Felipe_-_dualpi
August 5, 2015

Thnaks John, Neil

Where can I get this API - "Users of the content producer API have a path to upload shared resources for a project."

Is there nore information about it?

Regards

Adobe Employee
August 5, 2015

Hi Felipe,

In the coming weeks, the API package (Digital Publishing Solution Help | Integrating with Adobe Digital Publishing Solution) will be updated to reflect this API. This will include guidance on how to use it.

The intend of the API is to share resources between (HTML) articles; for example CSS / JS / Images and Fonts.

HTMLResources have been used in DPS in the past to 'stick PDF documents in the viewer' (which only worked to some point on iOS). This is not a supported use case.

-Klaasjan