I think I figured it out with the cover page. But trying to clarify the question anyway, I wanted to have two images for the cover: one for the smaller screen and the other for the larger screen, and also wanted to keep it one-level. So I created an HTML article for the cover with media queries. With HTML articles, the top navigation bar does not show up on the devices, unlike on pages created within the AEM dashboard, where it shows up, and stays there automatically. Since I wanted to be able to tap the cover image to go to the TOC page, and also wanted a way for the top navigation bar to show up, I added top-margin to the cover image. That bumped the image down, so when I tapped on the top part of the screen, the navigation bar showed up.
Thank you for those links, and I will watch the videos. It seems like a very long process to create a custom preflight app, with signing it, and everything that comes with that (getting the .ipa file, a .p12 development certificate, and a development mobileprovision file). Is there another way to see the custom fonts loaded on the device, or is creating a custom preflight app the only way?
Thank you for this response. For the issue with multiple covers, I would prefer to only have one top level, since that's really the only page that would have different content. I could create an HTML article for the cover, but when I preview it on a device, it does not have the top navigation, which is different than pages built from the AEM dashboard. Right now the cover is a full page JPG, and I want it to link to the TOC. Is there a way to make the cover JPG link to the TOC, and have a way that the top navigation shows up on the cover page?
Fonts are not supported in the AEM Preflight app. Instead, build a custom preflight app.
For the dynamic banner, is your AEM Preflight app updated? If you're using an older version, it won't work.
For the cover page, it really depends on how much work you want to do. If you want different content for phones and tablets, you can create a project with two top levels, and specify different content for phones and tablets (the desktop uses the tablet version). However, there's more overhead in this approach. If possible, use the same content for phones and tablets so that you avoid extra production work.
Let us know if you have more specific questions for any of these issues.