A cloud-based, centralized solution for project hosting, build automation, task management and team collaboration – this is what MadCap Central (MCC) is meant to be. The idea of handling all those processes with a single tool sounds great. How does it work out in practice?
We decided to spend some time with MCC to see if companies providing technical communication services, like 3di, could consider it as the primary tool for day-to-day work.
As we would expect, the new platform is designed primarily with Flare projects in mind. MCC integration with Flare works great. You upload and import projects directly from Flare, using the new MadCap Central window. The whole process is quick and intuitive.
At this stage, only MadCap Flare 2016 r2 and 2017 are integrated with MadCap Central, which means you need to consider additional costs and potential issues related to upgrading Flare, unless you’re planning to get the new Flare version anyway.
As far as source control goes, MadCap thought of two alternative solutions – a single-bound and dual-bound model. In the single-bound model, you use MCC as your primary source control system. In the dual-bound model, you use a system like SVN or Git, and MCC serves as an additional repository. It is certainly good to have that choice if you already have a source control solution in place and you don’t want to abandon it after moving to MCC.
You perform all source control tasks, like push and pull, from Flare. Depending on the chosen model, you use the new MadCap Central window, the Source Control tab, or both. If you used Flare projects bound to source control before, you will be able to quickly start working with MCC-bound projects.
Currently, you can’t perform source control tasks directly from the MadCap Central portal. We’d certainly welcome such a possibility in upcoming versions.
Admin features are simple and intuitive. You can quickly add new users, create teams, assign them to projects and manage their permissions. The possibility to bulk add users using a CSV file will for sure come in handy when setting up MCC for the first time.
All existing features are useful but the set of permissions could be expanded to make them more robust. For example, allowing users to edit only their own tasks or to change task assignment without a possibility to edit any other information would be a valuable addition to the existing permission set.
Task management features are helpful and transparent. The calendar view provides a neat look at deadlines while the task board allows you to change task statuses quickly by moving task cards between columns.
What we found useful are customisable widgets that can be added to MCC dashboards. We really liked the task summary widget that sums up all the work in a sharp-looking doughnut chart. All the widgets can be filtered, which makes them even more useful.
MCC users can collaborate more efficiently while dealing with their tasks thanks to the built-in messaging system. Although, it’s purely internal (there is no integration with any external messaging systems), the possibility of communicating with your colleagues without the need to leave MCC can definitely speed up the process of resolving tasks.
It’d be great if the task management could be enhanced in upcoming versions of MCC with some additional features. We’d really like the option to link tasks to one another and the possibility to mention other users in comments that triggers notifications.
Building and publishing
Apart from managing tasks, MadCap Central also offers some features for managing builds. You can build your Flare projects, download the output, and schedule the build process. Scheduling is very handy because you don’t need to install a separate build automation tool.
Builds can be set as private (to view them only from MCC) or live (to get permanent links for public access). If you don’t need all the customisation possibilities offered by a traditional hosting service, MadCap Central can be a good candidate for taking over the role of your publishing platform. Even if you already publish your documentation in a hosting service, you can still use MCC as a temporary publishing platform for testing and reviewing purposes. This combo solution will be much easier to implement if in the future MadCap decides to extend MCC with the possibility to publish to external servers.
It goes without saying that MCC offers useful build management features, but there are also some limitations that you need to consider. There’s no auto-sync of imported files, no support for multilingual output, and you can’t automatically get latest files for dual-bound projects. Some output formats cannot be generated from Central (e.g., Adobe FrameMaker) and some more output formats cannot be viewed there (e.g., DITA and MS Word). In some scenarios, these limitations may be hard to overcome but let’s keep in mind that this is the very first version of MadCap Central. We believe that these obstacles will be tackled in subsequent versions.
In the current form, MadCap Central and Flare 2017 are an interesting solution for simple, small-scale projects. Clients who don’t have very complex needs and look for an out-of-the-box solution to deliver content easily may consider MCC and Flare as one of the options. For example, this tandem could work in a company that has a few authors who create documentation with a simple tool, like MS Word, and don’t have any publishing platform. They aren’t part of any larger team and don’t have any tools for source control and for task and project management. Generally, they need to start building their documentation infrastructure from scratch. Instead of investing time into putting several tools together to build a solution, they could take MCC and Flare and get to work straight away.
On the other hand, if a company already has tools in place for task management (like Jira), source control (like SVN), build automation (like Jenkins), and a publishing platform, it may be hard to find a strong case to replace them with MCC. Also, if a company has complex documentation needs (like multilingual output), considerable number of users accessing the documentation server, existing tools that they would like to integrate (SSO, Outlook), MCC may not be up for the challenge due to its current limitations.
We see a lot of potential in MadCap Central and we love the idea of having all those necessary tools merged into one. It’d be great if in the future MCC could be developed into a unified solution for storing text, templates, page layouts, CSS files – a central place for reusing content across Flare projects.
If you want to try MadCap Central, visit https://www.madcapsoftware.com/downloads/?p=RCE#select.