Distributing HTML5 output from SharePoint

[April Bosworth]

Has anyone successfully used SharePoint to distribute your HTML5 output with others (outside your organization)? Any guidance would be greatly appreciated. 

Our files are saving to SharePoint, but attempting to open the index file downloads it rather than opening a browser to show the content output from Robohelp. The index file opens as expected from the "output" folder I have saved to our network drive. (My "local" folder and the content saved to SharePoint are both creating .aspx files, which I don't know what to do with as they won't open in a browser--except to show html gibberish).

[Jeff_Coatsworth]

IIRC, somebody had this effect of downloading vs. displaying before here on the forum - I think it came down to a setting on their server.

[Jeff_Coatsworth]

and the .aspx files are in the Sharepoint output file type for HTML5 output.

[April Bosworth]

Do you have any recollection of key words I could look for to find the previous discusion? I didn't find it looking for "SharePoint" (though I did give up once is seemed like the posts were old). Thanks!

[Jeff_Coatsworth]

See this thread - https://community.adobe.com/t5/robohelp-discussions/robohelp-2019-update-5-published-help-to-sharepo...
and maybe this one - https://community.adobe.com/t5/robohelp-discussions/robohelp-2019-reimagined-not-publishing-correct-... - where a caching issue was taking place.

[Amebr]

Perhaps this: https://learn.microsoft.com/en-us/sharepoint/allow-or-prevent-custom-script#to-allow-custom-script-o...

[April Bosworth · Accepted solution]

Our solution has required multiple actions:

1-Adjust the scripts on the SharePoint site as @Amebr Amber suggested https://learn.microsoft.com/en-us/sharepoint/allow-or-prevent-custom-script#to-allow-custom-script-o...

{This step switched our index file from downloading to opening}

2-Change our sharepoint library settings: (from the root folder on SharePoint) Settings Gear > Library Settings > More Library Settings > Versioning Settings > Requred documents to be checked out before they can be edited = No

{This step straightened out our ability to "check in" files from RoboHelp. Checked out files were not viewable from SharePoint to anyone with SharePoint access other than the person who had them checked out, i.e. I could see it, but my colleagues could not.}

3-In Robohelp, set up collaboration. From the top ribbon menu: Collaborate> Open Connection > select profile > Add project > pick the sharepoint folder where this published project lives. Republish the project. (And possibly return to the collaborate menu which now includes a "check in" option.)

{This allowed me to remove the "checked out" status on the SharePoint files from within Robohelp and to do it all at once. If I tried to check in from the SharePoint side I had to check in all the files in each folder.}

4-Publish the project from Robohelp (to SharePoint). 

[Peter Grainge]

Thank you for posting your solution. I am sure it will help someone in the future.

________________________________________________________

My site www.grainge.org includes many free Authoring and RoboHelp resources that may be of help.