![mediawiki vs.confluence mediawiki vs.confluence](https://www.saashub.com/images/app/context_images/7/7c6e469a565e/documize-alternatives-medium.png)
You want to insert these blocks into various pages: Page for Audience 1 We'll call this re-used section "Block A." You probably have a page called “Re-used Blocks” that has Block A, Block B, Block C, and so on, representing other re-used components. This creates difficulties with re-use.įor example, let's say you have a section you want to re-use in two places. The basic problem stems from the fact that Confluence puts both source files and production files on the same platform. If you have a content re-use scenario, however, watch out. So here you go.Ĭonfluence works well as an internal wiki when you don't need to re-use content. I didn't plan to provide any more detail, but today as I was making a few edits on Confluence to fix some last content before migrating it to DITA, I got somewhat frustrated and realized it might be helpful to some technical writers evaluating tech comm platforms to have more insight about why Confluence kinda sucks for tech comm authoring, particularly when it comes to re-use scenarios. Berger ( September 22, I am still in the "omg confluence is great" phase would be interesting to know your thoughts on this Blog it, please! I'm becoming disillusioned with Confluence. #techcommĪnd a couple of people asked me for a post with more Please blog it. Am so happy to be migrating Confluence content to DITA. I don't mean to be critical, but I really hate using Confluence for doc. The other day I tweeted about a brief frustration with Confluence:
![mediawiki vs.confluence mediawiki vs.confluence](https://trackdaytrailer.com/images/142509.jpg)
Academic/Practitioner Conversations Project.Author in DITA and Publish with WordPress.Reflecting seven years later about why we were laid off.A hypothesis about influence on the web and the workplace.