9

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?

Improve this question

1 Answer 1

Reset to default
0

My vote is for moving the content to a hosted solution. It reduces the burden of including the content with your managed package and ensures the latest copies can be referenced by customers without having to wait on their managed package being upgraded.

For my hobby projects, I've started including links to my GitHub README or wiki that hosts a living FAQ.

Improve this answer
7
  • I was kind of thinking the reverse. With Static Resources the help content would always correspond to the version it was released with. Pluses and minuses...
    – Daniel Ballinger
    Commented Jul 2, 2017 at 23:01
  • I would do it just like Salesforce Release Notes; have each version out there. Especially if customers don't all upgrade at same time. You at least have one spot to worry about publishing docs than include in managed package pushed to each customer, especially if SIZE is a concern.
    – Doug Ayers
    Commented Jul 2, 2017 at 23:03
  • Which makes me wonder what drives the Salesforce Docs themselves? API version selection is one of the things they do well.
    – Daniel Ballinger
    Commented Jul 2, 2017 at 23:07
  • Doug, yeah, wondering if anyone has come across a good authoring tools and a good way to publish; we are talking about hundreds of pages and lots of screenshots. And as Daniel mentions versioning. And securing the content...
    – Keith C
    Commented Jul 3, 2017 at 8:36
  • Have you considered Confluence?
    – Doug Ayers
    Commented Jul 3, 2017 at 13:46

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .