We are already generating separate roleList pages at build time from the contents of the <particDesc> in modern plays. These are injected into the edition pages as separate documents, so they can be kept open by a user when needed, while the same original <particDesc> is still turned into a popup version of the character list which is linked from the slideout panel.
The next stage of this is as to implement support for what follows:
Editors may add introductory material to their <particDesc> in the form of one or more <p> elements preceding the <listPerson> element(s). These paragraphs will be rendered in the roleList page view of the character list, but they will be dropped in the popup version.
Editors may add prefactory material for individual <listPerson type="castlist"> elements in the form of a <desc> element at the beginning of the <listPerson>. These will be rendered as paragraphs, and will be shown in both the standalone page and the popup view; we expect them to be relatively short, and may impose a constraint on length.
Editors may link to a <person> element in a <listPerson type="castlist"> by using a role: prefix, followed by the (globally unique) id of the <person> element. At build time, this link will be expanded into a pointer to the generated roleList document, and to the specific role inside that document; a :target pseudo-class should be used to ensure that the role is highlighted when navigating to it. Since the <person> id is globally unique, and the mechanism which generates a roleList file name and its constituent ids is predictable, there should be no problem processing these links at build time, and this expansion should happen at the Original XML phase, when the other <particDesc>-related expansion is happening.
We are already generating separate roleList pages at build time from the contents of the
<particDesc>in modern plays. These are injected into the edition pages as separate documents, so they can be kept open by a user when needed, while the same original<particDesc>is still turned into a popup version of the character list which is linked from the slideout panel.The next stage of this is as to implement support for what follows:
Editors may add introductory material to their
<particDesc>in the form of one or more<p>elements preceding the<listPerson>element(s). These paragraphs will be rendered in the roleList page view of the character list, but they will be dropped in the popup version.Editors may add prefactory material for individual
<listPerson type="castlist">elements in the form of a<desc>element at the beginning of the<listPerson>. These will be rendered as paragraphs, and will be shown in both the standalone page and the popup view; we expect them to be relatively short, and may impose a constraint on length.<person>element in a<listPerson type="castlist">by using arole:prefix, followed by the (globally unique) id of the<person>element. At build time, this link will be expanded into a pointer to the generated roleList document, and to the specific role inside that document; a:targetpseudo-class should be used to ensure that the role is highlighted when navigating to it. Since the<person>id is globally unique, and the mechanism which generates a roleList file name and its constituent ids is predictable, there should be no problem processing these links at build time, and this expansion should happen at the Original XML phase, when the other<particDesc>-related expansion is happening.