diff --git a/atst/forms/task_order.py b/atst/forms/task_order.py index e511d53f..4a234701 100644 --- a/atst/forms/task_order.py +++ b/atst/forms/task_order.py @@ -34,12 +34,13 @@ class CLINForm(FlaskForm): label=translate("task_orders.form.clin_number_label"), validators=[Optional()] ) start_date = DateField( - translate("forms.task_order.start_date_label"), + translate("task_orders.form.pop_start"), + description="For example: 07 04 1776", format="%m/%d/%Y", validators=[Optional()], ) end_date = DateField( - translate("forms.task_order.end_date_label"), + translate("task_orders.form.pop_end"), format="%m/%d/%Y", validators=[Optional()], ) diff --git a/styles/elements/_card.scss b/styles/elements/_card.scss index 410a6882..36505dd2 100644 --- a/styles/elements/_card.scss +++ b/styles/elements/_card.scss @@ -16,6 +16,11 @@ } } + &__title { + padding: $gap * 2; + background-color: $color-gray-lightest; + } + &__header h3 { margin-top: 0; } diff --git a/styles/sections/_task_order.scss b/styles/sections/_task_order.scss index d874abd6..a1d1c395 100644 --- a/styles/sections/_task_order.scss +++ b/styles/sections/_task_order.scss @@ -100,7 +100,7 @@ } .form-row { - margin: 0; + margin-top: 0; } select { @@ -243,3 +243,7 @@ display: flex; justify-content: center; } + +.clin-card { + width: 65rem; +} diff --git a/templates/task_orders/step_3.html b/templates/task_orders/step_3.html index daeee6b1..59adf536 100644 --- a/templates/task_orders/step_3.html +++ b/templates/task_orders/step_3.html @@ -24,154 +24,172 @@ v-bind:initial-clin-type="'JEDI_CLIN_1'" {% endif %} inline-template> -
Not sure how to describe your scope? Read some examples to get some inspiration.
' scope_label: Cloud project scope start_date_error: PoP start date must be before end date. - start_date_label: Start of period of performance (PoP) team_experience: built_1: Built, migrated, or consulted on 1-2 applications built_3: Built, migrated, or consulted on 3-5 applications @@ -362,21 +360,21 @@ task_orders: pop_start: PoP Start pop_end: PoP End form: - add_clin: Enter another CLIN + add_clin: Add another CLIN add_to_header: Add your task order add_to_description: Now, refer to your document to find the 13-digit task order number. It should be located at lorem ipsum dolar. From now on we'll refer to this portion of funding by the recorded task order number. - clin_title: Enter CLINs - clin_description: "Continue to refer to your TO to locate your Contract Line Item Numbers (CLINs). You must add CLINs one at a time, and select a corresponding ID/IQ description for each." - base_clin_title: Base CLIN Information - clin_number_label: Enter task order CLIN - clin_type_label: "Select ID/IQ CLIN description" + clin_title: Enter Contract Line Items + clin_description: "Refer to your task order to locate your Contract Line Item Numbers (CLINs)." + base_clin_title: CLIN + clin_number_label: CLIN Number + clin_type_label: Corresponding IDIQ CLIN cloud_funding_header: Add the summary of cloud funding cloud_funding_text: Data must match with what is in your uploaded document. draft_alert_title: Your information has been saved draft_alert_message: You can return to the Task Order Builder to enter missing information. Once you are finished, you’ll be ready to submit this request. - obligated_funds_label: Enter obligated funds for Base CLIN - pop_end: 'Period of Performance (PoP) end date' - pop_start: 'Period of Performance (PoP) start date' + obligated_funds_label: Obligated Funds + pop_end: End Date + pop_start: Start Date review_button: Review task order supporting_docs_header: Upload your supporting documentation supporting_docs_size_limit: Your file may not exceed 64MB