benjaminduall

+1 for python. See the magic that happens with drawbot or nodebox

+1 for python. See the magic that happens with drawbot or nodebox

Same here,
my work depends on "global" layers aka the InDesign layers.
Example: a brochure which I design for 6 different languages:
masterpages used for different types of pages (cover, intro, detail,…) layers used for different content (languages) and backgrounds. I have al my pictures and backgrounds in one layer, text on the others, so I can easily switch which brochure I can edit or export to PDF. This is really necessary if we want to use aPub for long and complicated documents.
 
 

Same here,
my work depends on "global" layers aka the InDesign layers.
Example: a brochure which I design for 6 different languages:
masterpages used for different types of pages (cover, intro, detail,…) layers used for different content (languages) and backgrounds. I have al my pictures and backgrounds in one layer, text on the others, so I can easily switch which brochure I can edit or export to PDF. This is really necessary if we want to use aPub for long and complicated documents.
 
 

Presently, one can add empty container layers (i.e., not object or text layers) from the Layers Panel, but these layers are properties of individual pages. Would it be possible (without mucking up the architecture of the Affinity Suite) to be able to add document-wide Global Layers from the Layers Panel?
In this conception, Master Pages would offer repeatable but page-specific page composition schemas (not necessarily applied continuously or document-wide), Layers (as currently defined, and what might be called Page Layers) would offer Page-specific object containers, and Global Layers would offer document-wide containers for organizing types of content that need to be switched on/off globally (e.g., alternate texts in a multi-lingual document).
Global Layers would always preserve their stacking order relative to each other, but otherwise, for each spread, the user could freely arrange the stacking order of applied Master Pages, Page Layers, and Global Layers.
See screenshot illustration below.

+1 for python. See the magic that happens with drawbot or nodebox

Same here,
my work depends on "global" layers aka the InDesign layers.
Example: a brochure which I design for 6 different languages:
masterpages used for different types of pages (cover, intro, detail,…) layers used for different content (languages) and backgrounds. I have al my pictures and backgrounds in one layer, text on the others, so I can easily switch which brochure I can edit or export to PDF. This is really necessary if we want to use aPub for long and complicated documents.
 
 

Hi guys.
Sorry in advance for the redundancy, but I'm creating a new, separate topic, since part of this request was already kinda “solved” and my earlier post on said thread is TL;DR material. So here goes the shortened [it ballooned a bit again, but now with new, useful ideas] and focused version:
There's a super easy way to solve a very serious philosophical UX choice which almost completely prevents me to recommend Affinity Designer to, well, mostly everyone.
As you know, when you have a document into artboard mode, objects will be cropped whenever they go past the boundary(ies) of their respective artboard and reappear once they fully transition into the pasteboard, and AD automatically moves them in the layers panel according to whichever artboard they touch/hover above. This is already normal and expected AD behaviour for most users.
You can also manually move objects and layers outside/above artboards (I'm henceforth calling those “universal layers”, but feel free to give them a better name, like “document layers” or whatever), which do allow you to have any objects they contain appear – and, obviously, export – in two or more adjacent/close artboards. This is a great sign of a potential UX choice, as it is proof the document and layer model is completely ready for the addition I'm proposing; only the UX and the UI need a slight tweak in the form of a toggle and a few lines of code (by the way, nudging objects with the arrow keys doesn't trigger this behaviour, so it should be properly harmonised with the click+drag behaviour in both modes).
The only issue is that doesn't allow you to deactivate said behaviour of automatically moving objects/groups/layers into artboards when dragging them around with the mouse/trackpad, even with the “Edit All Layers” option disabled (the logical behaviour would be for objects not to switch layers or move into artboards under any circumstance if you're working in one layer in isolation, period. That particular case should be treated as a bug, not as a feature, and maybe the devs should ask users if they mind that slight change).
That could and should still be the default behaviour, so as not to confuse current happy users, but if we were given said toggle, AD would instantly become much more usable for 99,9% of use cases and a much bigger percentage of current and prospective users.
As I've said before, if any of the devs/mods or other users want me to do a little narrated screen capture to demonstrate this, I'm all up for it.
Kudos for the Affinity team and all the best for you all,
João

Same behaviour in Publisher Beta 1.7.0.337
I found out that setting the grid type to "two axis custom" and setting the "second axis angle" to -90 seems to fix it.
See the attached movie
Affinity_Publisher_-_Grid_Bug.mov

Same here,
my work depends on "global" layers aka the InDesign layers.
Example: a brochure which I design for 6 different languages:
masterpages used for different types of pages (cover, intro, detail,…) layers used for different content (languages) and backgrounds. I have al my pictures and backgrounds in one layer, text on the others, so I can easily switch which brochure I can edit or export to PDF. This is really necessary if we want to use aPub for long and complicated documents.
 
 

Bug still in latest Beta (.312)
Horizontal gridlines don't stay put when scrolling. Only happens with non-uniform grids.
Thank you for fixing.
 
 

Same here,
my work depends on "global" layers aka the InDesign layers.
Example: a brochure which I design for 6 different languages:
masterpages used for different types of pages (cover, intro, detail,…) layers used for different content (languages) and backgrounds. I have al my pictures and backgrounds in one layer, text on the others, so I can easily switch which brochure I can edit or export to PDF. This is really necessary if we want to use aPub for long and complicated documents.
 
 

+1 for python. See the magic that happens with drawbot or nodebox

Same here,
my work depends on "global" layers aka the InDesign layers.
Example: a brochure which I design for 6 different languages:
masterpages used for different types of pages (cover, intro, detail,…) layers used for different content (languages) and backgrounds. I have al my pictures and backgrounds in one layer, text on the others, so I can easily switch which brochure I can edit or export to PDF. This is really necessary if we want to use aPub for long and complicated documents.
 
 

It works on OpenGL (Basic) for all pages but not for OpenGL and Metal, which are the two that we are concerned about the most. I've logged this with the dev's for you.

Excellent Thank you v much! - this should be in the right click selection - it would be much faster

Thanks for raising the issue I'll get this reported

@kimtorch
Welcome to the Serif Affinity forums
There are plans to add scripting to the Affinity range, but few details have been released yet.

Hi,
Quark's "Step & Repeat" misses creating grid of objects like InDesign. So it will be perfect if we can get a combination of those two.

YIPPPPPEEEEEEEEE! we got bleed guides MINT! 
Table row and column sizing bug swatted ACE! 
Save table format as default works without bombing TECH-HOT!
Annoying sliders left on screen DESTROYED 
Well done publisher team great work

Click here to download the latest beta for macOS
Status: Public Beta
Purpose: General Testing
Requirements: None
As this is a beta it is considered to be not suitable for production use. This means that you should not attempt to use it for commercial purposes or for any other activity where you may be adversely affected by the application failing, including the total loss of any documents. 
We hope you enjoy the latest build, and as always, if you've got any problems installing or running up, please don't hesitate to post here.
Any problems actually using this version please post to post in this forum and we'll get back to you as soon as we can. Many thanks for your continued feedback.
Please post any bug reports here. Please feel free to leave general suggestions and comments in the Discussion Forum.
Fix List
Installer
- Fixed failure to start on some systems due to font issues
Start up
- Reset Table Formats and Title Exceptions missing from Ctrl+Run on Mac
Document / Page Management
- Offer option to convert Artboard documents to Spread documents on open
- Bleed guides / visible bleed now available in the main view
- Fixed document bleed not being automatically applied to new spreads and master spreads
- Fixed bleed from masters not drawing on applied spreads
- Snapping grid now draws on current spread rather than always the first spread
- Transparent background is a document setting, not a per-spread setting
- Adding a pages to a facing page document generates the wrong page labels
General Tools and Menus
- Fixed Pop up Sliders not closing on Mac
- Fixed priority issue with Select Tool / Placement Tool
- Fixed Zoom Out causing unwanted Pan
- Fixed Gradient Tool to add stops correctly
- Added Paste FX to Layout Persona Edit Menu
- Added Geometry operations to the Customise Toolbar dialog on Mac
- Fixed applying style from Styles Panel when in list mode
- Rearranged View menu to separate guides and rulers
Text Tool
- Fixed diacritic entry via dead keys on Mac
- Drop Caps now have a 'Scale for Descenders' attribute
- Fixed Leading entry glitches on Windows
- Fixed Kerning entry glitches
- Fixed Tracking entry issue
- Fixed intermittent crash when adjusting the Fill and / or Transparency for Decorations
- Fixed spelling error highlights not updating whilst editing Text Wrap settings
- Fixed crash setting Text Wrap option on EPS images
- Text flow handles now hide when view is zoomed a lot, out to prevent view clutter
Text Style Editor
- Layout improvements
- Fixed Style description truncation in Text Style Editor on Windows
Tables
- Setting Table cell size from Table Panel not working correctly
- Fixed Keep with next lines breaking Table layout
- Table Save as Default could cause app to crash 
- Right click on table header not deleting multiple columns / rows
- Table Formats should include Frame fill, stroke and insets
Resources / Resource Manager
- Document policy for Embedding / Linking images available from File > New / Document Setup
- Better prompting when missing Linked Images encountered on Document Open
- Resource Manager now always shows resource thumbnails
- Placement sort in Resource Manager fixed
- Resource Manager columns are now resizable
- Fixed Resource Manager grid scroll issues
- Fixed Properties read out for pasted Affinity Documents
TOC
- Fixed glitch when TOC was deleted leading to incomplete removal
Print / Export
- Double sided prints always flip on longest side (partial fix)
- Fixed converting colour for PDF/X-3 export rasterising elements
 

Your description is basically what we plan to do so just be a bit patient and give us feedback when we have a working version.
Other long document features will come over time. 

I think A-team must make an exception for this app and introduce "global" layers just as in ID and Quark. They will be created on all pages automatically but they must not act as master pages. It means, when you put some object on any of these layers it must not be copied on all other "global" layers. Only on that page.
The other type of layer should be called "local".

We’ve fixed the slider / pop up issue and you should see it in an update, hopefully later this week.

Also: the CMYK dialog.