Skip to main content
Salesforce

Return to Question

added 120 characters in body
Source Link
Keith C
Keith C
  • 137.3k
  • 29
  • 218
  • 458

We have been using ZIP static resources included in our managed packages for help content. These are exported from Confluence and linked into our managed packages via Visualforce pages (so that $Resource can be used to reference the static resources).

We now have a lot more content that we want to make available, so the 5M limit on a static resource is a problem as is the 250M limit on the total size of all static resources.

I'm looking for any suggestions on how to handle this better. My assumption is that the content will need to move to an external system, be that some 3rd party product or perhaps a Salesforce Community. Looking for good authoring tools and easy publishing. Multiple versions of the information will need to be supported correspdonding to the multiple managed package versions. Any recommendations?

Ideally this content will only be accessible to Salesforce users (various single sign on mechanisms can handle that) who have a license for one of our products (much harder to achieve). Any recommendations?

We have been using ZIP static resources included in our managed packages for help content. These are exported from Confluence and linked into our managed packages via Visualforce pages (so that $Resource can be used to reference the static resources).

We now have a lot more content that we want to make available, so the 5M limit on a static resource is a problem as is the 250M limit on the total size of all static resources.

I'm looking for any suggestions on how to handle this better. My assumption is that the content will need to move to an external system, be that some 3rd party product or perhaps a Salesforce Community. Looking for good authoring tools and easy publishing. Any recommendations?

Ideally this content will only be accessible to Salesforce users (various single sign on mechanisms can handle that) who have a license for one of our products (much harder to achieve). Any recommendations?

We have been using ZIP static resources included in our managed packages for help content. These are exported from Confluence and linked into our managed packages via Visualforce pages (so that $Resource can be used to reference the static resources).

We now have a lot more content that we want to make available, so the 5M limit on a static resource is a problem as is the 250M limit on the total size of all static resources.

I'm looking for any suggestions on how to handle this better. My assumption is that the content will need to move to an external system, be that some 3rd party product or perhaps a Salesforce Community. Looking for good authoring tools and easy publishing. Multiple versions of the information will need to be supported correspdonding to the multiple managed package versions. Any recommendations?

Ideally this content will only be accessible to Salesforce users (various single sign on mechanisms can handle that) who have a license for one of our products (much harder to achieve). Any recommendations?

Tweeted twitter.com/StackSalesforce/status/881609543985364992
Source Link
Keith C
Keith C
  • 137.3k
  • 29
  • 218
  • 458

How to deliver large volumes of help content for a managed package?

We have been using ZIP static resources included in our managed packages for help content. These are exported from Confluence and linked into our managed packages via Visualforce pages (so that $Resource can be used to reference the static resources).

We now have a lot more content that we want to make available, so the 5M limit on a static resource is a problem as is the 250M limit on the total size of all static resources.

I'm looking for any suggestions on how to handle this better. My assumption is that the content will need to move to an external system, be that some 3rd party product or perhaps a Salesforce Community. Looking for good authoring tools and easy publishing. Any recommendations?

Ideally this content will only be accessible to Salesforce users (various single sign on mechanisms can handle that) who have a license for one of our products (much harder to achieve). Any recommendations?