Preserve the generated files
Start by locating the generated HTML, the existing PDF, and any related source files for the offer. Make a separate copy of the original HTML before changing it. This protects the initial version and gives you a comparison point if the edit introduces a layout problem. Keep the existing PDF as an earlier output rather than replacing it immediately. If an optional cover letter was generated, keep it separate from the resume files so you do not accidentally rebuild or submit the wrong document. The Radaryno Resume Kit keeps files and generated documents on the buyer computer, so this organization can be done locally without adding the documents to an external service.
Edit the HTML source
Open the copied HTML and make only the intended correction. Check the surrounding section after editing, because a small wording change can affect wrapping, spacing, or page breaks. Keep the chosen design consistent unless the purpose of the revision is to change it. The kit offers default, classic, compact, and modern designs, but this rebuild task does not require changing designs. Avoid editing the old PDF as a substitute for updating the HTML. The PDF should be recreated from the maintained source so a later revision can be repeated without losing the correction.
Read the bundled builder instructions
Before creating the new PDF, consult the instructions included with the Radaryno Resume Kit. The kit contains a local script for generating resume files, but the exact command, path, and options should come from the supplied instructions rather than guesswork. Confirm which source file the builder expects and which output it creates. If the kit is being used with Claude Code or Codex, keep the local workflow and the instruction for the builder distinct: the AI provider may assist with the source, while the local script handles the document-generation step described by the kit. Do not invent a command or assume that a generic HTML-to-PDF converter follows the same process.
Run the local rebuild
Run the bundled builder exactly as described in the kit instructions, using the edited HTML as the source. Wait for the process to finish before opening the output. If the builder reports an error, keep the edited source and the earlier PDF intact while you resolve the issue from the supplied instructions. Do not compensate by editing the old PDF or by changing several unrelated files at once. The purpose of this step is to produce a new PDF that corresponds to the edited HTML and the intended resume design. Keep the output local with the source and note which revision produced it.
Inspect the rebuilt PDF
Open the newly created PDF and compare it with the edited HTML and the intended earlier version. Check the corrected wording, section order, page count, page breaks, margins, spacing, and readability. Also confirm that the selected design remains the one intended for the offer and that no stale wording remains. A PDF can be generated without an obvious technical error while still showing the wrong source or an unwanted layout change. Review every page at normal reading size, and use text selection or search where available to confirm the revised wording is present. If anything is wrong, return to the HTML source, correct it, and rebuild rather than patching the PDF.
Retain the approved version
Once the PDF matches the edited HTML, keep the approved source and output together and distinguish them from the earlier files. Use descriptive names or a local note that identifies the revision without relying on memory. If the resume was prepared in an offer language other than English, check that the rebuilt output preserves that language and the intended technical terms. Do not delete the original until you are confident that the new PDF is the version you want to retain. The kit also includes a local application tracker, but this document rebuild does not submit an application, search for jobs, or contact an employer.
| Choice or stage | What to verify | Useful evidence | Decision |
|---|---|---|---|
| Original HTML | The file is preserved before editing | An unchanged copy remains available locally | Use as the comparison source |
| Edited HTML | The correction appears in the intended section | The text, language, and design choice match the revision | Send this source through the bundled builder |
| New PDF | The PDF reflects the edited HTML | Visible text, page order, spacing, and layout are correct | Keep if the inspection passes |
| Earlier PDF | It may contain stale content | The previous wording or layout still appears | Retain only as an earlier version |
Worked examples of an HTML-to-PDF rebuild
Before: the HTML contains an outdated role description, while the PDF still displays that wording. After: the source is copied, the HTML is edited, the bundled builder is used according to its instructions, and the new PDF is checked against the revised text.
Before: a correction is made directly in a PDF editor, but the HTML still contains the old version. After: the HTML becomes the source of truth, the PDF is rebuilt locally, and both files are retained so the relationship between source and output remains clear.
Before: the selected design creates an awkward page break after an edit. After: the edited HTML is rebuilt using the intended design, then the PDF is inspected for page order, spacing, readability, and unintended blank areas.
Before: several PDFs have similar filenames and the approved version is unclear. After: the source and output are kept together with clear, descriptive file names and a brief note identifying the version that was inspected.