Comala Publishing

Our company has a great experience with Appfire team and tools we use. Tools - we find to be reliable, well-structured and well-optimized. UI simple. Flexibility on a high level, allowing easy set-up and necessary controls. Support - fast, polite and helpful. Guys do their best to address questions fast and solve problems ASAP.

• 

  Appfire

  Hi Alexey,

  Thank you for the fantastic feedback! It is great to hear that Comala Publishing is providing the reliability and flexibility your company needs. We design our tools to handle complex publishing workflows while keeping the interface intuitive, so hearing that you find the setup easy and well-optimized is a big win for us.

  We also appreciate your shout-out to our support team. They take great pride in resolving issues quickly to keep your documentation moving forward. If you ever run into a new use case or have ideas on how we can further improve the UI, please feel free to connect with us through our support portal.

  We look forward to continuing to support your team’s success!

  Cheers,

  Paweł Customer Success Team | Appfire

(+) I started implementing Comala publishing after using Comala Document management for years. When that didn't go as smoothly as I hoped for, the team was super responsive. We got the issue fixed in 5~7 days with daily communications. It now works as intended. Thankfully the page tree architecture is now kept over from the source to the target space. I am now confident that the team will only see the documentation I intend them to see. I like the dashboard view (with room for improvement), and the possibility to push bulk publication of several pages at once. (-) with Comala publishing, I miss the ability to move blogs over. I would also like to have the option to display the version history on the target space, as opposed to starting from v.1 again. I would like the option to cross the Document Report with Publishing report, and show the Comala document state, labels and any other page property for each page on the publishing report (i.e. a modular one-stop-shop rather than three different dashboards with partial information).

• 

  Appfire

  Hi Sophie,

  Thank you for being a long-term user of our tools and for sharing such a detailed look into your transition to Comala Publishing! It’s great to hear that the page tree architecture and bulk publishing features are providing the peace of mind you need to ensure your team sees only the right version of your documentation. We know that maintaining a "single source of truth" is vital for internal clarity.

  I’m also glad our team was able to stay in close contact to resolve those initial implementation hurdles. Regarding your feedback on blog synchronization, version history persistence, and the desire for a more unified "one-stop-shop" reporting dashboard, thank you for these specifics. Consolidating page properties and document states into a single view is a powerful idea for improving oversight. I have shared these suggestions with our product team as they look at future enhancements for our dashboard and reporting modules.

  If you have any other questions as you continue your rollout, please feel free to reach out to us at our support portal.

  Cheers,

  Paweł Customer Success Team | Appfire

I'm using Comala Publishing on Confluence Cloud along with Comala Document Management. It is helpful to connect publishing to a document management workflow. However, there are two issues that make this very challenging to scale. First, publishing does not retain a document's location in a page tree. The document always goes to the root of the target space, and you have to move it. This is how it works not only on the first publish, but every time you publish the page. Error prone and time wasting, and not as advertised. Secondly, the publishing status widget Comala adds to all of your draft pages does not work. This status is supposed to display "new" when the page hasn't been published, then "published" after the page is published. This would be a great feature if it worked, but in my situation, after successfully publishing from a Comala Document Management workflow, my publishing status does not update, and the status badge is always "new". Now the status is simply misleading visual clutter and if I want to check on publishing status, I have to navigate to the published space and manually confirm. Comala is supposed to be the industry standard for building QMS workflows in Confluence, but I find it very disappointing that the two basic features I described don't function. I'll be looking at the Scroll products and hopefully have better luck there.

• 

  Appfire

  Hi Matt,

  I sincerely apologize for the frustration these technical hurdles have caused you. It is clear that the manual overhead of reorganizing page trees and the lack of accurate status visibility are significantly impacting your QMS efficiency. When you are managing critical documentation, you need the tool to handle the structure and status reporting reliably so you can focus on the content itself.

  Regarding the page tree hierarchy, this behavior is often tied to specific configuration settings between the source and target spaces, and we want to ensure your setup is optimized to preserve that structure. Additionally, the status badge sync issue sounds like a localized synchronization error that our engineering team should investigate immediately to remove that "visual clutter" and restore trust in your workflow.

  Please reach out to us at our support portal so we can collect your site details and look into these two specific issues for you. We are committed to resolving this and would appreciate the chance to get your workflow back on track.

  Kind regards,

  Paweł Customer Success Team | Appfire

I've been using this app for a long time and really couldn't manage without it. It allows me a place to stage big changes to the doco. And when I had a bug, support was there with the answer. Thanks, guys.

• 

  Appfire

  Hi Jennifer,

  It’s great to hear that you’ve been a long-time user of Comala Publishing! We really appreciate you sharing how the app helps you manage your documentation lifecycle. We know that having a dedicated space to stage and refine major content updates is crucial for maintaining a "source of truth" without disrupting your readers, and we’re happy to be part of that workflow.

  I’m also glad our support team was able to step in and resolve that bug quickly for you. Keeping your publishing process smooth is our top priority. If you ever run into anything else or have ideas for new features, you can always find us at our support portal.

  Cheers,

  Paweł Customer Success Team | Appfire

Great app to use

• 

  Appfire

  Hi Nikita,

  Thank you for the rating! It is great to hear that you are finding Comala Publishing to be a useful addition to your workspace. We designed the app to simplify the way teams manage content lifecycles and sync documentation, so it is rewarding to know it is working well for you.

  We are always looking for ways to improve the publishing experience. If you ever have suggestions on how we can make your workflows even more efficient, or if you need assistance with a specific configuration, please feel free to reach out to us through our support portal.

  Cheers,

  Paweł Customer Success Team | Appfire