Pixelkobold

Only a week to go

I'm not sure what you mean about seeing the position of the guides while you move them. Doesn't the ruler show you that.
Also, though there's no option to put them on all pages, you can put them on a Master page, and they'll show up on any page that uses that Master.

You can also use the guides manager to put them precisely where you want them.  Having said that @walt.farrell, it would really be helpful if you could see the the Guide in the ruler as you are moving it.  I think this might be an enhancement, or really a bug, but when you are moving the cursor around on the document, you get a line in the rulers showing where the cursor is, but once you click on the guide, the line goes away.  I'm running version .283 on Mac 10.13.6.  Looks like the problem only occurs for the vertical guides.
@Ernesto José  Here's a screen capture of the guides manager showing how you can set the precise spot where you want the guide. 

screencast 2019-03-31 20-06-21.mp4

I make the graphic design and illustration for book covers. Is quite fun.

Someone mentioned, in the Facebook Affinity Publisher group, that they would like book and book cover templates.  I think that's a great idea.  Can Affinity please create some book and book cover templates in Affinity Publisher?  Thank you!

Hey,

You have a good product with a terrible name, it reminds us graphic artists of a M!@@))@@)@t product.

Change the name to Affinity Layout and thank me for a couple of decades.

Rodi

Hi musictobemade
Assets are like a clipboard that can contain many items.  Assets are normally something that you will use frequently in many publications, for example a company's name, address, telephone  number and contact details  or a logo, etc
Unlike a clipboard,  Assets are retained  i) even when you place a copy in your publication.  ii) when you close Publisher and they become available again when you re-open Publisher.
Once an Asset has been stored, you can put a copy/copies anywhere in your publication by simply dragging it from your Assets panel into your publication/s.
This means that you can store commonly used  objects such as company logo, explanatory text, etc and if you want others to be able to access them, you can embed them in your current publication.  If you pass that publication to someone else, then when they open they will be asked if they want to to import the Assets into their Asset panel.
You can create Assets using the 'bun'  top right of Assets Panel (fig one)  and Create New Category from the menu (fig2) and then add your own sub-categories as I have (fig 3)
               
Fig 1                                                                                               Fig 2                                                                                           Fig 3
To make your own assets, simply select an object (text frame, or image or table, whatever) and then open the menu on a category/sub category (click on it's 'bun' and choose  Add from Selection.

 An Asset remains available both in your current publication and any future publication until you Right click on it and Delete it.  Deleting an Asset does not delete any copy of it that you may have used in your document.
Hope that this has helped introduce them for you. More info in the Help document
Pman

You're looking at the items on each layer, not the layers themselves. It looks like "Ebene 1" is the actual layer in your file.  Since you have different items on different pages, those items will be different but the layers themselves remain the same across all pages.

You may have seen this video on YouTube about Affinity Publisher Beta v. Adobe InDesign. which is in my opinion a massive fail. Affinity Publisher isn't a copy of of InDesign. It's a different operation concept. Think different!
I really like what I've seen and tested so far in APub - very good job!
To solve the problem of the video I've nested picture frames inside the beautiful symbols and with one click you've added a picture to all linked triangles as shown in this demonstration:
https://drive.google.com/uc?id=1x5G9JD5bLlmhiIYhQWnAoigEL1Q7LhZx
Keep on drawin'
Norbert

No, the difference is that layers in Indesign are not per-spread items, but per-document entities. That means, the same layer can contain objects that are placed on different spreads. Therefore, you can hide all these objects by simply toggling the visibility of the layer they belong to.

Indesign-Layers.mov

If all of these features, which are qualified as „very important“, „indispensable“, „basic“ and „crucial“ features, should have been already present  „in the beta launch“, we would be looking forward for the initial release of Publisher in 2024!
If somebody needs these features now, he (a) unfortunately has to look for a different piece of software — or (b) try to achieve his goals with Affinity Publisher without applying a dedicated feature. In most cases this is possible by mobilizing a small amount of flexiblity and creativity.
These are the 2 alternatives. There is no third one.

For the first version yes. 
Appreciate your other feedback. We understand the first version of the app isn't going to have the functionality some people need, but we are listening to all the feedback and suggestions which are made. I'm comfortable we will be making the right calls in terms of prioritisation of what new features we implement in subsequent updates and future versions over the coming years, but it is very much a long term project.
 
Thanks,
Ash

This „Files in one place“ only works for people with a special workflow. If you, for example, compose images using other source artwork, you probably want to keep these assets together. Packaging the final result separates the result from its sources, if you don’t want to have two instances. If you want the assets and sources in one place – why not doing this from the beginning? So you don’t need to collect them afterwards. And collecting assets for print – who does this any more? Are there really people out there, who send source data to the printer and not a PDF?
Your opinion concerning fonts: "Quark and Indesign have been doing it for years with no legal issues. There is an initial dialogue box that warns you of the legality and you can choose to ignore in the future.“ Don’t think, you really mean this! Or would you accept this: „I send my copy of QuarkXpress to a friend of mine with a statement that warns him of the legality and he can choose to ignore in the future.“  And: The statement of Quark and Adobe is no „warning“, as you might think. It states very clear, that you only are allowd to hand over fonts to someone else, if you have the legal right to do so, and if your font license allows you to do so. Most font companies don’t allow this. By the way: Even the Adobe owned TypeKit company doesn’t allow to hand over fonts via packaging:
But I don’t want convince you of my opinion. I only want to make clear, why I think – especially in regard to „Publisher“ – packaging is of minor importance, and there are much more important things to do.

It isn’t for actual Publisher, because even if you „unembed“ the assets, they remain within the file. No need for packaging. (The images have to remain in the file, because of interoperability with Affinity Photo, which you will see in one of the next updates).
Packaging fonts always was a shady, semi-legal thing. Transfering fonts in most cases is forbidden for copyright reasons. I know, that QuarkXpress and InDesign do it, but …
On the other hand: It is real no big action to collect the used fonts manually. This normally is done in a minute.

its not a beta .. it's barely an alpha
a beta is a pre-final feature complete solution that you're doing final rinse testing on (feature complete for that version) an alpha is where you're testing/trying ideas to see if they work .. experiments to see if user needs can be met user needs include master pages as template designs for projects larger than about 5 pages ... the current release is an experiment to see if the solution they came up with works for these users .. it so happens that experiment failed.. which is ok.. that's what alpha experiments are about 
you can't just divide up a list of "features"  into 2 and call it alpha and beta
 
more here:
https://www.gov.uk/service-manual/agile-delivery/how-the-alpha-phase-works https://www.gov.uk/service-manual/agile-delivery/how-the-beta-phase-works

Just the rust styles (grunge rust textures):
 

   
The old rusty compressed styles file:
rust-textures.afstyles.zip

Here are also some Div Metal Styles (mostly dark textured/structured ones) for those who might have a need for these!
The compressed AD styles files ...
Div Metal Textures.zip

Exactly. A PDF won't include your styles sheets and edits from InDesign. PDFs are generally part of a proof and print workflow. Without the ability to import InDesign documents more or less intact, Publisher will be dead in the water. If you can't migrate from InDesign, Publisher is useless as an InDesign alternative. Once it can handle InDesign docs, then Katy bar the door. Why to you think Adobe offers their Photo Package, including Lightroom and Photoshop, so inexpensively? Obviously they are feeling the heat. It will be interesting to see if InDesign comes down in price once Publisher is cutting their water. If you need InDesign's e-publishing features no doubt you hope so. Otherwise, Publisher looks great. If you have not done so already, take a look at their online tutorials. They cover Publisher pretty thoroughly.

You are too dramatic. Just use the software, that is migration enough. Ability to open InDy files is just a bonus when it comes.

Just observation from somebody who switched from Adobe software completely to Affinity for both Photoshop and Illustrator. Same surely will apply for Publisher. In the beginning you will need (and look for) that Adobe "crutches". Old files, clients sending something in known file format and so on. My advice is - weed out Adobe software from your workflow and move entirely to Affinity. Affinity works best with native formats - you can start by making new jobs entirely in Affinity software and after a while you will notice you don't need to look back - why would you? Transition may not be as smooth as one would desire but it is worth it.
Treating Affinity software as something that should work seamlessly with Adobe isn't the way in my experience. When Publisher will reach certain maturity - work within it. Instead of "but in Indesign I could do this! When it will be possible in Publisher" be little more flexible. Indesign was released in what? 2002? And was build up on PageMaker from 90's, right? Imagine all the time they had to polish it (and in my opinion they still failed at one very important thing - making it pleasure to work with). We will get there, but not with first beta Publisher is not made to kill everything that exists for years now at release. It is beginning and for what I see - it will pay up to support Affinity. Because they managed to make daily work (almost :D) a pleasure.

I, like many, can appreciate the amount of work that has already gone into creating Affinity Publisher Beta and I'm sure they will continue their work on the .indd import. In the meantime after running a few tests (both simple and complicated) I too have my workaround when need arises as @David Simpson has already stated in order to open an already finished InDesign document for further simple editing when necessary. Simply exporting the .indd into a PDF format imports quite surprisingly tidy into AP with editing possibilities that are fine for my needs.
As well, exporting from InDesign into an .eps file imports nicely although the text comes in as shapes so is not editable. Between both ways, this works for simple edits on an already finished .indd document. I wouldn't be switching to AP in the middle of a ID project anyways, so the finished .indd versions -> PDF is fine until AP gets the update for importing and hopefully exporting to .indd or at least .idml formats. 
I understand a lot of the criticism at this point, yet still think Affinity deserves a good round of applause for taking on such a giant and I'm confident they will listen to their community (which personally I feel Adobe does not) and will produce their updates. I already like AP and am well excited to see where it goes. 

indd export not as critical as is the ability to import. Most are probably exporting the bulk of their efforts into some variation of pdf, but to move ongoing legacy projects to Publisher will require an InDesign import system of some sort (preferably sooner than later). 

yeah but then it is still early beta....

I can't give any timelines for this (IDML import, not INDD). It's being worked and will be in an update when it is considered working and relatively stable. But I would be talking more than a few weeks in not months, It's not a simple thing to just implement 
(edited by Patrick Connor for clarity that this is a statement about IDML and not INDD: 08 July 2019)

@Gabe Logan
Welcome to the Serif Affinity forums
It's not possible yet. There are plans to be able to open IDML files in the future
<mod edit> IDML not INDD file clarification was made in an edit on 6th July 2019 </mod edit>