Design: Reword the versioning on the modal

[ExperimentsInHonesty]

Overview

We need to reword the versioning of the Guidelines Version modals to reduce confusion for admins between current state and future state of the project they want to change.

Details

The following dropdowns contain:

• changes requested
• screenshots of current modals (before changes)
• text blocks (before and after changes)

The examples assume a project where the admin wants to change the version from the current Program Guidelines Version (1.0.1) to a previous Program Guidelines Version (1.0.0).

---

Modal 1

Modal 1 Changes

• Indicate to admin the current Guidelines version this project is using by changing the below text
  From

  Current Program Guidelines Version:
  

  To

  This Project's Current Program Guidelines Version:
  

• Add a period to the sentence "The selected version's rules will be applied to this draft"
• Add the following new item after the revised "This project's current version number"

  Current Published Program Guidelines Version:
  

• Change dropdown text
  From

  Program Guidelines Version:
  

  To

  Change This Project's Program Guidelines Version To:
  

Before

Modal 1 Screenshot Before

Modal 1 Text Before

[Centered]**Change Program Guidelines Version**

**Date Draft Created:** YYY-MM-DD

**Date Program Guidelines Last Updated:** YYY-MM-DD

**Current Program Guidelines Version:** 1.0.1

Select the Program Guidelines Version from the dropdown below. The selected version's rules will be applied to this draft

**Program Guidelines Version:** Version 1.0.1 (YYYY-MM-DD - Present)

I want to proceed with changing the applicable Program Guidelines version.

CANCEL  SUBMIT

After

Modal 1 Text After

[Centered]**Change Program Guidelines Version**

**Date Draft Created:** YYY-MM-DD

**Date Program Guidelines Last Updated:** YYY-MM-DD

**This Project's Current Program Guidelines Version:** 1.0.1

**Current Published Program Guidelines Version:** 1.0.1

Select the Program Guidelines Version from the dropdown below. The selected version's rules will be applied to this draft.

**Change This Project's Program Guidelines Version To:** Version 1.0.0 (2026-12-01 - 2027-11-15)

I want to proceed with changing the applicable Program Guidelines version.

CANCEL  SUBMIT

---

Modal 2

Modal 2 Changes

• Add the field names for "Name" and "Address" of the project as indicated in the following example. Only the field name should be in bold, not the values.

  From

  Lorna St. Apts
  5454 Lorna St.

  To

  Name: Lorna St. Apts
  Address: 5454 Lorna St.

• Make only the field names bold for "Alternate Number", "DRO" and "Date Draft Created". The values should not be bold.

  From

  Alternate Number: (none)
  DRO: (unassigned)
  Date Draft Created: YYY-MM-DD

  To

  Alternate Number: (none)
  DRO: (unassigned)
  Date Draft Created: YYY-MM-DD

• Indicate to admin the Guidelines version that they are changing from by rewording the below text, and make only the field name bold. The value should not be bold.

  From

  Previous Program Guidelines Version: 1.0.1

  To

  Change Program Guidelines Version From: 1.0.1

• Indicate to admin the Guidelines version that they are changing to by rewording the below text, and make only the field name bold. The value should not be bold.

  From

  New Program Guidelines Version: 1.0.0

  To

  Change Program Guidelines Version To: 1.0.0

Before

Modal 2 Screenshot Before

Modal 2 Text Before

[Centered]**Change Program Guidelines Version**

**Name**

**Address**

**Alternate Number: (none)**

**DRO: (unassigned)**

**Date Draft Created: YYY-MM-DD**

**Previous Program Guidelines Version: 1.0.1**

**New Program Guidelines Version: 1.0.0**

The selected version's rules will be applied to this draft after you confirm. This will affect project compliance requirements.

Are you sure you want to proceed?

CANCEL  CONFIRM

After

Modal 2 Text After

[Centered]**Change Program Guidelines Version**

**Name:**

**Address:**

**Alternate Number:** (none)

**DRO:** (unassigned)

**Date Draft Created:** YYY-MM-DD

**Change Program Guidelines Version From:** 1.0.1

**Change Program Guidelines Version To:** 1.0.0

The selected version's rules will be applied to this draft after you confirm. This will affect project compliance requirements.

Are you sure you want to proceed?

CANCEL  CONFIRM

---

Modal 3

Modal 3 Changes

• Add a space after the first sentence "The Program Guidelines version for the project has been updated. The rules corresponding to the selected version will now apply to the project."

• Add the field names for "Name" and "Address" of the project as indicated in the following example. Only the field name should be in bold, not the values.
  From

  Lorna St. Apts
  5454 Lorna St.

  To

  Name: Lorna St. Apts
  Address: 5454 Lorna St.

• Make only the field names bold for "Alternate Number", "DRO" and "Date Draft Created". The values should not be bold.
  From

  Alternate Number: (none)
  DRO: (unassigned)
  Date Draft Created: YYY-MM-DD

  To

  Alternate Number: (none)
  DRO: (unassigned)
  Date Draft Created: YYY-MM-DD

• Indicate to admin the Guidelines version changed from by rewording the below text, and make only the field name bold. The value should not be bold.
  From

  Previous Program Guidelines Version: 1.0.1

  To

  Changed Guidelines Version from: 1.0.1

• Indicate to admin the Guidelines version changed to by rewording the below text, and make only the field name bold. The value should not be bold.
  From

  New Program Guidelines Version: 1.0.0

  To

  Changed Guidelines Version to: 1.0.0

Before

Modal 3 Before Screenshot

Modal 3 Text Before

**Program Guidelines Updated**

The Program Guidelines version for the project has been updated. The rules corresponding to the selected version will now apply to the project.
**ADDRESS**

**ADDRESS**

**Alternate Number: (none)**

**DRO: (unassigned)**

**Date Draft Created: YYY-MM-DD**

**Previous Program Guidelines Version: 1.0.1**

**New Program Guidelines Version: 1.0.0**

Please notify the applicant that the Program Guidelines version that applies to this project has been changed.

CLOSE

After

Modal 3 Text After

**Program Guidelines Updated**

The Program Guidelines version for the project has been updated. The rules corresponding to the selected version will now apply to the project.

**Name:**

**Address:**

**Alternate Number:** (none)

**DRO:** (unassigned)

**Date Draft Created:** YYY-MM-DD

**Changed Guidelines Version from:** 1.0.1

**Changed Guidelines Version to:** 1.0.0

Please notify the applicant that the Program Guidelines version that applies to this project has been changed.

CLOSE

---

Action Items

• Assign yourself to this issue.
• Move the issue from Prioritized Backlog to In Progress.
• In Figma, move a blank page to the Design section.
• Change the Figma page's title to have the format "#Issue Number | Title | Assignee Name".
• Copy contents from the Figma Template page to this issue's Figma page.
• Include a link to this issue's Figma page in the Figma section below.
• Use the Figma page to design solutions for this issue.
• Once this issue is ready to be reviewed:
  • Add a comment tagging the team design lead that explains the design.
  • Move it to the Visual Review column.
  • Add the "ready for Design lead" label.
  • Once you have received feedback from the team lead, implement feedback as necessary.
• Use presentation structure to review proposed designs with the design director. Implement feedback as necessary.
• Use presentation structure to review proposed designs with the product, development, and research teams. Implement feedback as necessary.
• Create a new slide (or edit one if it already exists) in staging and add images and appropriate text
• Receive design approval from stakeholders. Implement feedback as necessary.
• Add any annotations to the Figma design that would help the developer with implementation.
• Create a Ready for Dev section around the final designs on the Figma page.
• Update the Figma Design System with changes resulting from the issue's final design, if applicable.
• Update the Style Guide Presentation, if applicable.
• Add a comment to the issue that references the final design and adds any annotations that would help the developer with implementation.
• Create a development handoff issue that references the comment.
• Move the Figma page to the Development section of the Figma file.
• Add the development issue's number in parentheses at the beginning of the title of the Figma page.
• Include the development handoff issue number in the GitHub section below.
• Reassign any previous assignees to this issue.
• Close this issue.

Resources

GitHub

Figma

Dev Site

Staging and Release decks

• Staging Deck
  • Staging slide, 2934
• Release Deck
  • 2025-MM-DD Release deck, slide 2934