Change 33540
Document the PDF-regeneration policy: only at release time, not
during ordinary development.
Per the user: PDFs are large, heavy files with almost no
incremental value day to day; regenerating them for every doc
change wastes disk space for no benefit. HTML stays cheap to
regenerate and should track its source; PDF generation is
deliberately deferred to the release process (Step 14 of
ReleaseProcessOverview.md), where it gets caught up all at once.
Added a "Documentation Builds" section to SDP_DeveloperGuide.adoc,
and a cross-referencing note at ReleaseProcessOverview.md's Step 14.
Agent: Claude (Sonnet 5), on behalf of Tom Tyler.
during ordinary development.
Per the user: PDFs are large, heavy files with almost no
incremental value day to day; regenerating them for every doc
change wastes disk space for no benefit. HTML stays cheap to
regenerate and should track its source; PDF generation is
deliberately deferred to the release process (Step 14 of
ReleaseProcessOverview.md), where it gets caught up all at once.
Added a "Documentation Builds" section to SDP_DeveloperGuide.adoc,
and a cross-referencing note at ReleaseProcessOverview.md's Step 14.
Agent: Claude (Sonnet 5), on behalf of Tom Tyler.