Final Revision Set

You have probably accumulated a long list of possible improvements.

Do not redesign the whole site two steps before the defense.

Prioritize.

Sort findings

P0 — broken/public-risk

Examples:

• credential/private data exposure;
• site does not build/deploy;
• major navigation path broken;
• inaccessible critical interaction.

Fix before release.

P1 — meaningful quality problem

Examples:

• inconsistent responsive layout;
• broken/misleading metadata;
• unclear project content model;
• dependency with unexplained compatibility risk;
• important image too large.

Fix if reasonably bounded.

P2 — polish

Examples:

• minor spacing tweaks;
• optional animation;
• extra project category;
• decorative redesign.

Do not let these destabilize the project.

Revision discipline

For each selected revision:

Finding:
Evidence:
Source owner:
Change:
Expected result:
Observed result:
Commit:

Keep scope coherent

Make small commits grouped by problem.

A final everything commit containing CSS, content, deployment, and config makes review harder.

Freeze point

After P0/P1 revisions pass verification, declare a review candidate commit.

Record its SHA.

Stop casually editing it while preparing the defense.

Checkpoint

Produce your final P0/P1/P2 table and identify the exact commit you consider the review candidate.