Have you considered using the LIST view instead of GRID view for the dropdown menu?
My understanding is that Books have the option to change from grid to list view, but that Chapters to not have that option. Is that correct?
Originally the markup provided by the team was all in one chapter in PT, using the \xt tags to create the cross references under each topic. I’ve used regex rules and some python to split each topic off into it’s own chapter and to create chapter labels (\cl) which copy the topic name.
One other thing I’ve experimented with was to branch the topics off into its own Collection, where each individual topic becomes it’s own Book. That gives me access to the dropdown List (as opposed to the Grid), but it causes cross references to stop working (I think that’s a bug, and I’ve reported it).
Another idea is create an introduction that will appear in the Chapter dropdown for each book with a hyperlink to your secondary menu
This looks like an interesting idea and worth pursuing.
Is the idea that someone would click the Introduction button, the introduction would open down below, and then a link back to the topic list would appear in that intro space? Or is it possible to have the link directly attached to the dropdown introduction, so that when you click that bar above the chapter numbers it takes you directly to the level-2 contents menu that lists the different topics?
How do you create a link that navigates back to a particular topic menu (a Contents menu)?
Have you considered using hyperlinks and the Glossary feature.
I don’t think that would really apply here. Basically we just have a few words to introduce a topic, often just a single word, and then a list of cross references. If we used the glossary feature, I guess it would just act as a list of parallel passages that would show up when you clicked a word in the text. But it would be something you’d only discover as you were reading, and couldn’t be used directly by a person who thinks something like “I wonder what the Bible says about raising children” and then opens up the app to search for that.
Did you create the index yourself or start with another index?
I’m working on this as a service to a team that I’m not directly a member of, so I’m not sure. I’ve written them to ask.