[IanMayo]

Fixes #198.

Problem

Pubs 9 and 10 publish from one ditamap, so they share one map title, which becomes the <title> of index.html and search.html, the publication title in every page header, the logo alt, and the root entry of nav-links.js. The author renamed the map by hand before every pub-9 publish and back again for pub-10.

Why not a scenario parameter

The issue asked for the title as a scenario parameter, ideally an existing one. There is none to reuse: the WebHelp Responsive parameter set has nothing that overrides the publication title (webhelp.logo.image.alt covers the logo alt only) and DITA-OT has no such argument. The alternative was a Fi3ldMan parameter plus an XSLT override of whc:webhelp_publication_title in the template, which is a customisation to re-verify on every Oxygen upgrade.

What this does instead

The edition is chosen by the mechanism that already tells the two scenarios apart: DITA profiling on the audience axis, through the scenario's own Filters tab. Pub-10 is the edition with the content withheld from trainees and Pub-9 is the edition without it, so the two names in the title sit on the same axis as that content.

• publications/pub-10/dita/index.ditamap: the title becomes Field Manual <ph audience="-trainee">Pub-10</ph><ph audience="trainee">Pub-9</ph> Mar 2025.
• DITA_project_pub10.xpr: the Pub-10 scenario excludes audience=trainee; the Pub-9 scenario keeps its existing audience=-trainee exclusion. One row each. The Pub-10 scenario also stops using an unset profiling condition set, so the two differ only in that row and neither depends on whatever condition set an author has applied in the editor.
• DITA_project_pub10.xpr also carries a project-level profiling definition for audience with -trainee and trainee, so Oxygen stops warning CND_PREF about undefined values and authors get value completion.
• check-publish.py prints the publication title it finds in index.html, so a publish can be confirmed as the edition it claims to be before it is copied into site/. Run against the current site/pub-9/current/ it reports "Field Manual Pub-10 Mar 2025", which is the bug this fixes.
• Docs updated: README, context-docs 01, 02, 03, 10 and 15 (new subsection in section 3 with the rationale), and the hub page note.

A first cut used a second attribute, product, with each scenario excluding the other edition's value. It worked but duplicated the trainee axis, and a profiling condition set on product could switch the title without hiding the trainee content. On one axis, a condition set per edition (Pub-10 ticks -trainee, Pub-9 ticks trainee) previews name and content together. Condition sets are created in the Oxygen UI and not committed.

Also: Author mode could not load its stylesheet

Found while checking the above in Oxygen. Both DITA_project_pub10.xpr and DITA_project_pub5.xpr attached f13ldman_author_mode.css to the DITA document type by an absolute file:/Users/… URL pointing at the retired template folder, so Author mode showed "Cannot load the associated CSS file(s)" and no Fi3ldMan styling. Each project now reaches the stylesheet in pub-5/template-2026/ through a ${pdu}-relative URL, the same way the scenarios already use ${pd}.

Not yet verified in Oxygen

This went in without an Oxygen run. On the next pub-9 and pub-10 publishes, check the header title and <title>. DITA-OT will report DOTJ031I No rule for 'audience=…' for the value each build keeps; that is information, not an error, and confirms the filter ran. The DITA Maps Manager shows both names in the title until a condition set is applied. The published site/pub-9/current/ keeps the old title until it is republished.

🤖 Generated with Claude Code

https://claude.ai/code/session_01PYsbdyzpWXUJAMGoXaiauD

[github-actions]

Preview removed

This PR is closed, so its preview has been deleted from gh-pages.