I appreciate everyone's reply... thank you so much. But this is really frustrating me.
I mean, Confluence gives Zendesk or WordPress the ability to publish or export/import for free. MadCap Flare can publish to Zendesk, so it seems logical that Flare should be able to publish to Confluence without paying a third party.
But they just want to force us to use Confluence for documentation, and it just doesn't have the advanced features of single-sourcing content that Flare has.
Imagine a 500-page manual created in Confluence. Now imagine eight client-specific versions of that 500 page manual. What would you do if four clients needed 100 pages updated (to their specific scenarios ... all different scenarios), and four clients didn't need any updates?
Would you want to update 100 pages four times (100 x 4 = 400 pages manually updated), or would you want to update 100 pages one time and automatically publish four client-specific versions of the doc based on conditionalized content? I would choose the latter. For example, I create one how-to article for multiple audiences and condition content for specific audiences (i.e., audience1 gets 'chapter 1' but audience 2 doesn't need that, so I tell Flare to not include chapter 1 for audience 2). Then I publish one time and create multiple, customized versions of the same doc. This is single-sourcing HTML documents.
One of my audiences is Confluence users (who also refuse to use PDFs files). So PDF isn't a delivery option.
This is why I want to publish HTML directly to Confluence Cloud, and it just becomes more and more frustrating to use.
NOW, imagine real-world and your business really has 8,000 clients. In Confluence, you'd have to have 8,000 individual manuals and update each one (and many chapters might have the same updates). So, in Confluence, I'd have to update the same article hundreds or thousands of times instead of updating ONE article ONE time... then publish 8,000 manuals.
I just want to publish the "confluence" version I've created in Flare to a Confluence Cloud space. Good lord, this can not be this difficult. Or at least upload the dang HTML pages into Confluence (which is also a no-no and not allowed by Atlassian). There must be a way to publish HTML content to a Confluence Cloud space.
Frustrated and pretty much "not a fan" of Confluence Cloud so far.
Jim
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.