lpm

Hello, fellow creatives and Affinity Publisher enthusiasts, As we navigate through the myriad of tools and formats in our digital workflows, one feature request seems to recur within this forum with noticeable frequency: the integration of markdown (md) import capabilities into Affinity Publisher 2. Many of us have adopted various workarounds to bridge this gap, such as utilizing the Ulysses app to export md files to docx format—a solution I have personally relied on. However, with the ever-evolving landscape of digital tools, adaptability becomes a challenge. My recent transition to JetBrains Writerside, for drafting and online work, illustrates this perfectly. Writerside’s export limitations to pdf, coupled with Affinity Publisher’s less-than-ideal handling of multi-page text pdfs, underscore a significant workflow disruption. This scenario often leaves us resorting to the cumbersome process of cutting and pasting markdown text directly into Publisher. While this workaround suffices for transferring plain text, it falls short when dealing with md’s more complex features, such as code blocks or tables. The essence of our workflows today is increasingly intertwined with markdown due to its simplicity, versatility, and widespread adoption. It is curious, then, that a tool as sophisticated as Affinity Publisher does not yet support markdown in a manner akin to its handling of txt, docx, and rtf file formats. This oversight not only hampers efficiency but also limits the creative potential of those who prefer or are required to work in markdown. Incorporating markdown import functionality into Affinity Publisher 2 would significantly streamline the workflow for a vast array of users, eliminating cumbersome workarounds and fostering a more seamless integration of ideas and content. Such an enhancement would not only acknowledge the evolving needs of the digital publishing community but also affirm Affinity’s commitment to user-centric innovation. Let’s discuss how this feature could reshape our workflows and potentially elevate the utility and versatility of Affinity Publisher. Your thoughts, experiences, and any additional workaround insights are warmly welcomed and highly appreciated as we collectively advocate for a markdown-friendly future in Affinity Publisher. Thank you for considering this feature request and for your ongoing contributions to making Affinity Publisher a tool that truly meets the needs of its user base.

Yes, I am aware that there are many like requests. Me making yet another may or may not signal to the developer team that it might be time to add the diagram feature to the Designer. 😀 At present, I use an external diagram tool and it works ok, but the persona feature in Publisher calls even more for the diagram feature in Designer. It is a very effective workflow. 👍

I am reaching out to request the implementation of an enhanced feature within Affinity Designer (for both iPad and Mac) and Affinity Publisher, inspired by the functionality observed in applications like Draw.io. The specific enhancement sought is the ability to draw figures, convert these drawings into nodes, and then seamlessly connect these nodes with lines that automatically format to indicate direction or movement. This capability would significantly benefit users who require advanced diagramming tools for their projects, facilitating a more intuitive and efficient design process. The addition of such features would not only streamline the creation of complex flow diagrams and schematics but also elevate the overall versatility and appeal of the Affinity suite for a wide range of professional and creative endeavors. I understand the challenges associated with developing and integrating new functionalities. However, this particular enhancement has the potential to fulfill a critical need within the Affinity user community, offering a more comprehensive and competitive solution for both design and publishing needs. Thank you for considering this proposal.

Here's an example. Works fine on other diagrams from other apps. It differs from app to app. Class-Instantiation.svg Class-Instantiation.afdesign

I use Designer 2 on iPad Pro latest iPadOS. - When I open an SVG I usually have issues that the text is not where it should be. - The same if I place the SVG. The same file is fine in online SVG editors and on iPad preview. I tried several different SVG files. Same issues. Issue only with SVG's with inline text.