Catshill

If you would like each newly created text frame to remain [No style] for character and paragraph, despite changes made to the previous one. If that's what you're thinking, there is no such setting or possibility.
 
I'ts a nightmare for me to. That's not how it should work by default.
 
Yes. I think the same.
The user shouldn't be forced to drag text frames from the "Resources" panel just to ensure that the default text style in a newly created frame wouldn't change and stay's how he wants. This is crazy

In APub we have a confusion of the role they have to play, the text frame, the text styles, and object styles.

I agree but to clarify, there are three ways it can work.
Always use the app's default formatting. This is a crude and inconvenient approach because for those not using text styles, each time you create a little caption you're going to get Arial 12 Black even though you're making a dozen Times 11 Red captions. Affinity would need a way to explicitly set document defaults instead of setting them automatically based on the last formatting applied. No app does this. Always use last applied formatting - what Affinity is doing. IMO Affinity's approach is good for those not using text styles - make one little caption Times 11 Red and all subsequent text objects will be Times 11 Red. The downside is that after I've made my dozen captions, I can edit some Arial 12 Black text, save the document, restart Affinity, and a week later when I open the document and draw a new text frame, it's Times 11 Red. This approach makes Affinity feel unpredictable. Always use current formatting. This is the way most apps work, including Adobe. Draw two frames and they're Arial 12 Black. Make dozens of Times 11 Red captions. Click in the Arial 12 Black frame and then draw a new frame - it will be Arial 12 Black because the document default is whatever is at the text cursor position. I would obviously prefer that Affinity switch to the "current formatting" approach like other apps. Making this change would also fix the bugs with updated TOCs suddenly becoming italicized, or inserting a new footnote and it being bold.

Oh look, more freaking moonspeak 🌙 ... Might as well be written by AI.

Exactly. Even if Serif announces tomorrow they are to reveal all our hopes and dreams will come true (in a future update, of course), it means very little in the grand scheme of things as they are the ones who have been bought out. At best they buy some time until Canva figures out what they will ultimately do with the software, but what Serif says itself is irrelevant. Canva can allow them continue to run as-is for a little while to maintain some semblance of stability, but the longterm is now uncertain and the rug can be pulled at any moment.

I'd already started packing my things before this announcement because I could see clear as day that the suite was not being maintained but superficially (unfixed bugs&features, patch updates, lack of polish). We now see why.
It's disappointing for its users, but it's literally a Tuesday for most other people in the design world. Serif does have its own employees to look after and if it can't go full steam ahead on its own, it is what it is. I don't take it personally.

I appreciate that the effort was made and that we got this far. It's been a pleasure watching development, but at some point I'd like to just get on with reality. I do also appreciate that we can now take a moment to again review our own individual decisions in terms of where we invest our time and energy and go from there... so there is that.

In the end, our tools do not make us, but rather we are what make our tools great and that the growth process involved there is what makes us better designers...

Disappointed but not surprised by this. The excitement of version 1 and new functions slowed and the much-touted version 2 was welcome but not that exciting. The numbers simply didn't add up.

Disappointed but not surprised by this. The excitement of version 1 and new functions slowed and the much-touted version 2 was welcome but not that exciting. The numbers simply didn't add up.

I agree with @anto
It would be great to have this functionality in APub. 
+1 from me for Data Merge text in a single text frame.

It reminds me to a known V1 oddity with ghost frames caused by a "selection vs. current page" issue …
… or might be technically related to / a regression of an issue reported for V2 only but solved in a 2.1 beta:

You’re not missing anything, it’s the way it works and fools me occasionally. Drag the ghost image across to the frame or use the picture frame anchor option window to centre it.

I don’t place text frames on master pages but use layout guides. That is because I am designing magazines that are based on a two column layout with different frame heights and stories that don’t flow into one another.

Thanks for your post @AvdB-Netherlands!
I can confirm this is logged with our development team, as thomaso has outlined above (specifically 'AF-86') and I've bumped this with the team now, to bring it to their attention once again.
I certainly understand the frustrations here and apologise for any inconveniences caused due to this setting not being retained in the meantime.

I’ve mentioned this a number of times, as have others. It doesn’t seem to be a priority fix and has been around for a long time. It at least should remember the last setting.

I’ve mentioned this a number of times, as have others. It doesn’t seem to be a priority fix and has been around for a long time. It at least should remember the last setting.

I'll add that when comes the time to type the corrections in the laid out document, I begin with the last correction first — so, because the text above will not flow, I will always visually find easily the next item to correct. 
(If I began with the first item, next lines would be changed and a word which was on the left of the column in the annotated PDF could be moved on the right in Publisher for example, making harder to find it.)

Yes copy and paste without format. And yes I manually apply bold and italic in APu. Importing styles (even just bold and italic)from Word was just too time consuming and I just prefer having a ‘clean’ base to work from.

I find it more reliable to do all my formatting in Affinity and only import Word files as plain text.

I find it more reliable to do all my formatting in Affinity and only import Word files as plain text.

I find it more reliable to do all my formatting in Affinity and only import Word files as plain text.

I don't think exporting a Publisher document to a Word document would be practical.  Exporting the text of an individual story, sure, but not the entire document.  The structure of a DTP document is just too different from that of a traditional word processing document - it may be possible to export something which loosely resembles the Publisher document, but it would not be practical to work with in Word and some of the formatting would be very likely to break during the export.
 
Convince them that what they really want is PDF.  DOCX files make for a *very* poor distribution format, however much some people might wish to pretend otherwise.

Almost certainly your printer will require the export as pages not spreads. As @walt.farrell says just run two exports (as pages), one for the cover and one for the other pages. Just remember that (annoyingly) you have to change it from spreads to pages every time. 

https://store.serif.com/en-gb/sign-in/

The entire interface of version 2.0 is a degradation from V1. A thorough redesign is no longer an option but a necessity. 
Incredibly poor contrast (shades of gray used to build panels, buttons, category backgrounds). Lack of consistency when it comes to the design of elements such as drop-down lists, text fields (size, padding, alignment, text line heights, appearance)  Different shapes of tabs in panel groups for active states, hovering states. Blending of the background color of the text box with the panel itself. Lack of consistency when it comes to the quality of icons (some look sharp, pixel aligned and pixel perfect others are blurry) Visual noise. (to much bad previews, icons) ... It would take a long time to list. It is simply unpleasant to work with such an interface.
When I read the following article on Affinity Spotlight it gave me a good laugh.
Specifically, I am referring to the beginning of the article which reads:
EDIT: link to article corrected.

It isn't a "bug", it's "by design" – it is also very stupid and annoying! (I have no idea why Serif refuse to let the user decide which default export option they want!)

I find the easiest and most reliable way to do this is to export to PDF and then use the booklet option to print from the pdf reader.

I find the easiest and most reliable way to do this is to export to PDF and then use the booklet option to print from the pdf reader.

This is done via Windows settings not Outlook.