These are tips shared directly from a team using this process to publish their in5 files to Microsoft Sharepoint.

The InDesign Document

We design the pages in InDesign, using a 1280px by 720px* layout.

in5 Settings

Then we export it into in5 using the settings below.

Basic setting

  • Slider (Fade In)
  • Enable Swipe
  • Show Arrows (we don’t always use this for our SharePoint sites – just depends on how they are designed)
  • Text Rendering = Images (preserves exact appearance)

Backgrounds

  • Background Color = Paper
  • Page Color = Paper

Advanced

  • Image Quality = High Definition – Text Frames Only
  • Mobile Device Viewport = Use Desktop Scaling
  • Desktop Scaling = Best Fit
  • Check Render Rectangles as CSS
  • Check Lazy Load
  • Check Allow Page Items to Span Across Pages within Spreads

Inserting the in5 (HTML) Output into Sharepoint

Next, we put the in5 published file (and associated assets folder) onto our (private) internal web server (this process may vary at your workplace).


Once uploaded to the web server, we now have an internal URL that points to our in5 document.


In SharePoint, Insert > Web Part > Media and Content > Page Viewer.


Click the tiny black arrow to Edit Web Part.


Linking to the internal URL

In the Page Viewer properties, we enter the internal URL (from above).


Preventing an unnecessary page title from showing

In Appearance, we put a space or two in the Title box. 


Otherwise, you’ll have the words Page Viewer showing above your page. We set a fixed height of 700* Pixels.


Additional Settings

  • For Layout, we use Zone 2.
  • For Advanced, we keep all the default settings.

Applying the Settings

Click Apply and you should be all set! 


Sometimes, we need to putz around with the Height pixels*, but for the most part, this is what works for us.


* These settings may vary according to your project.


Disclaimer: It is SharePoint, so sometimes things work perfectly and other times, it gets fussy and what worked for one site doesn’t work for another site. Not sure why, but are pretty sure that SharePoint does these things on purpose just to make us think we are crazy.