What are the benefits to using FrameMaker along with AEM?

FYI, FrameMaker does not support nested tables. The most common workaround for this is to insert a text frame into a cell and then insert a table within the text frame. It's also possible to create the illusion of nested tables through the careful use of additional rows and columns combined with straddling, borders, and shading.

Thank you for the information. 🙂

With XML Documentation for Adobe Experience Manager, you can use the built-in DITA Web Editor to author and review DITA-based content. FrameMaker works as a DITA XML desktop editor in this scenario. You can check out, edit, and check-in files from AEM.

You can create PDFs from AEM with DITA OpenToolkit or with FrameMaker Publishing Server or locally with FrameMaker. Which route you choose, depends on your requirements in terms of layout quality and complexity. Generally said, for simple layouts, DITA OT can be enough. The more complex your requirements are, the less DITA OT makes sense as it becomes more and more development effort. You can easily end up with weeks and months of DITA OT development for things you can do with FrameMaker in a few minutes or hours.

So, FrameMaker plays two roles: As an easy-to-use template designer for your DITA XML, AND as a powerful DITA Desktop XML Editor with out-of-the-box integration with AEM. Plus it gives you a lot of things, you do not have in a DITA web editor like WYSIWYG view, a powerful source code editor, support for XPATH, XSLT, etc.

Not sure of the specific benefits of AEM with FM, but the traditional explanation of FM's benefits are things like long document support (it came from the book publishing industry after all) and excellent PDF creation. Support for Structured writing, localization, CMSs and things like that are just a bonus.