Madcap Flare: CSS perils publishing to Salesforce, Zendesk, or ServiceNow
The 2019 release of Madcap Flare added support to publish your output to Salesforce and Zendesk. Support was added to publish to ServiceNow in the Madcap Flare 2020 release. To do so, you need to purchase a separate plug-in licence for the appropriate platform. Use the links below for further details:
- Madcap Flare Connect for Salesforce
- Madcap Flare Connect for Zendesk
- Madcap Flare Connect for ServiceNow
- Install the relevant plugin. I've covered how to do this in a previous post.
- Configure the connection to the hosting platform in your Flare destination file.
- Ensure the "Convert Stylesheet Styles to Inline Styles" option is enabled in your Flare target file.
The CSS Conundrum
- Publish the target. If the limit is reached, an error is returned.
- Open the source of each page's output, copy it to your clipboard, and paste it into a blank Word file. The number of characters is displayed in the Word Count function.
- In the list topic, the total number of characters in the Flare project's HTML equals 759. In the Clean HTML output file, that jumps to an impressive 1213. That's a 62% increase!
- In the table topic, the total number of characters in the Flare project's HTML equals 1865. In the Clean HTML output file, that jumps to 1908. That's not a big jump, but it's a small table with limited formatting.
- Splitting topics into smaller chunks.
- Not having over complex CSS styles, particularly in table styles.
- Checking the topic's HTML for any unnecessary characters (e.g. " " or "<span>" tags).
- Removing all unnecessary topic text. This is a great way to improve your editing skills and reduce localization costs.
- Use shorter topic titles and headers.
- Only use hyperlinks and bookmarks where necessary.