Jump to content


  • Posts

  • Joined

  • Last visited

Recent Profile Visitors

297 profile views
  1. Just commenting to add my support to this request - being able to draft in markdown would open up a lot of workflow possibilities for me and the teams I manage. Baseline features to make this useful to me: Heading paragraph styles (#, ##, ###, etc. - as well as ---- and ==== markup for h1 and h2) Bold and Italic character styles Block quote paragraph style Tables would be great but I know they're not standard across all Markdown flavors, and Affinity Publisher handles tables a little differently such that they would need special consideration. I know there's other things that would need to be considered, but if I had those things my workflow would be improved dramatically.
  2. About a month ago I launched a website for my games, and I want to share it with y'all. All of the layout elements were created in Affinity Designer, as well as the logo. https://mnemonicrpg.com/setting.html Things I'm proud of here that I created with Affinity Designer: The woodgrain background of the site, which is the exact same asset as the top menu bar, with some clever filters applied The book cover in the table of contents The parchment texture for the page's main content The logo It's gonna look different between mobile and desktop, but everything but the table of contents should be visible on both. Lemme know what you think!
  3. I love the Paragraph Decorations. That being said, there are a couple of wish list items I think would make this feature even more useful: Let me apply a Brush to the border decorations. That would enable me to create more interesting effects without having to add them as inline pixel layers. Let me set a more complex background fill. Ideally I would like to be able to set a Symbol as a fill object. Let me create a decoration that goes from the right edge of the text to the end of the column (or from the left edge of the text to the beginning of the column). I've wanted to do all three of these things in the current project I'm working on and haven't been able to. Thanks!
  4. I ended up working around it, so I don't have the issue reproducible on my end. But I'll see if I can recreate it.
  5. Okay, I did some digging, and it looks like if there's a hyperlink on Spread 1 that goes to an anchor on spread 5, when you export the pages that include those two spreads, Affinity Publisher doesn't know how to map the anchors to their new page numbers, and so it errors out during export. For now, removing the hyperlinks and anchors fixed the problem for me. But this is something the devs probably ought to look at.
  6. I'm trying to export my afpub document to pages so that I can publish it, but I get an error during the export. The error only appears if I export with the selection "All Pages"; if I select "All Spreads", or even "Current Page", the file exports just fine (but is unusable for my purposes). I saw somewhere someone pointed out a way to get a log file to generate on Windows; is there a similar solution for macOS? Or, ideally, a known solution for this particular issue?
  7. I've used it for three published projects now, with a fourth on the way. It has some limitations, and bugs, but nothing show-stopping yet.
  8. I do layout work for TTRPG (tabletop roleplaying game) designers, and this week I decided to give Affinity Publisher an honest go of it. I took two commissions, and put both of them into Publisher. I'm pleased to say that it mostly went smoothly, but I have a few things that would have made the experience even better. A lot of us in the TTRPG industry are looking at Affinity Publisher as a more manageable alternative to Adobe's subscription model, and we bring with us some very specific needs that would be great to accommodate. I put a thread up on Twitter talking about them, which I'll link at the bottom of this post, but here's the bullet list of things we'd like to see: Impovements to the Place tool when used with text--specifically, we need the styles to map consistently every time a given file is placed--or, more preferably, a menu to appear prompting us to map the styles in the source file to the styles in the Publisher file, with additional options to keep or discard any style changes from the source file. Place tool support for Markdown (.md) files--right now we have to use Pandoc to generate a docx file in order for it to work with Publisher, which adds a layer of complexity that can cause problems. Let us skip that step. Export/Persona for HTML output--this is a big one for me, but web designers could get a lot of mileage out of this application if it could generate HTML code. I've been wanting to create interactive character sheets for games, with trackers and toggles and text fields and menus. Being able to do all of that within Publisher would be awesome, but being able to add those things to the HTML output would be a nice first step. Export/Persona for ePub output--this would be good for generating multiple versions of a document without having to maintain multiple source files. Those are the big-ticket items for me as a TTRPG designer and layout artist for the industry. I know there are others who would also benefit from these things.
  9. (Sorry for the cross-post; I'm realizing this is less of a bug report and more of an ask for help/suggestion for improvement.) I'm importing a .docx file that I generated from a Google Doc, and it doesn't map the body paragraphs to the Body text style, nor the lists to the relevant Bullet List / Numbered List styles that are included in Publisher. Same thing with the headings; it creates new heading styles and assigns the headings to those, instead of using what's already there. Is there a way to make Google Doc or Word use styles that can be recognized, or alternatively is this something in the Affinity dev pipeline that I can expect to see in a future build? This is already leaps and bounds better than before, but if I have to re-update all the styles every time I load in a new draft that's going to seriously slow me down. As an added note, after I updated the imported styles from the docx file, I then imported the same docx file again--and the newly imported text from the same file still didn't respect the styles I had updated.
  • Create New...

Important Information

Please note there is currently a delay in replying to some post. See pinned thread in the Questions forum. These are the Terms of Use you will be asked to agree to if you join the forum. | Privacy Policy | Guidelines | We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.