The .mil means it’s official.
Federal government websites often end in .gov or .mil. Before sharing sensitive information, make sure you’re on a federal government site.
The site is secure.
The https:// ensures that you are connecting to the official website and that any information you provide is encrypted and transmitted securely.
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 built_many: Built, migrated, or consulted on more than 5 applications description: How much combined experience does your team have with development in the cloud? label: Team experience none: No previous experience planned: Researched or planned a cloud build or migration validators: is_number_message: Please enter a valid number. is_required: This field is required. list_item_required_message: Please provide at least one. list_items_unique_message: Items must be unique name_message: 'This field accepts letters, numbers, commas, apostrophes, hyphens, and periods.' phone_number_message: Please enter a valid 5 or 10 digit phone number. file_length: Your file may not exceed 50 MB. fragments: delete_portfolio: title: Deactivate Portfolio subtitle: Portfolio deactivation is available only if there are no applications in the portfolio. edit_application_form: explain: AT-AT allows you to create multiple applications within a portfolio. Each application can then be broken down into its own customizable environments. edit_environment_team_form: delete_environment_title: Are you sure you want to delete this environment? add_new_member_text: Need to add someone new to the team? add_new_member_link: Jump to Team Settings unassigned_title: Unassigned (No Access) no_members: Currently no members are in this role no_access: No Access edit_user_form: save_details_button: Save portfolio_admin: none: Not Selected ppoc: alert: message: Selecting a new PPoC gives that member full access to the portfolio and removes your ability to manage the PPoC role. The rest of your permissions will remain untouched. Please be sure you want to proceed. title: Warning! assign_user_button_text: Assign member confirm_alert: title: 'Once you assign a new PPoC, you will no longer be able to request portfolio deactivation or manage the PPoC role.' subtitle: The PPoC has the ability to edit all aspects of a portfolio and is the only one who can manage the PPoC role. title: Primary point of contact (PPoC) update_btn: Update update_ppoc_confirmation_title: Confirmation update_ppoc_title: Update primary point of contact login: ccpo_logo_alt_text: Cloud Computing Program Office Logo certificate_selection: learn_more: Learn more message: 'When you are prompted to select a certificate, please select Email Certificate from the provided choices.' title: Certificate Selection csp_disclaimer: This is one of two sites being used for both Azure and AWS integration. The URLs and hosting environments are being managed without knowledge of or input to the JEDI source selection and should not be considered an endorsement of any cloud vendor. h1_title: Access the JEDI cloud login_button: Sign in with CAC title_tag: Sign in | JEDI cloud navigation: portfolio_navigation: breadcrumbs: admin: Admin funding: Funding reports: Reports applications: Applications topbar: jedi_cloud_link_text: JEDI logout_link_title: Log out of JEDI cloud portfolios: admin: activity_log_title: Activity log add_new_member: Add a new member alert_header: Are you sure you want to delete this member? alert_message: 'The member will be removed from the portfolio, but their log history will be retained.' alert_title: Warning! You are about to delete a member from the portfolio. no_members: There are currently no members in this portfolio. permissions_info: Learn more about these permissions portfolio_members_subheading: These members have different levels of access to the portfolio. portfolio_members_title: Portfolio members settings_info: Learn more about these settings portfolio_name: Portfolio name applications: add_application_text: Add a new application add_environment: Add new environment add_another_environment: Add another environment app_settings_text: App settings create_button_text: Create create_new_env: Create a new environment. create_new_env_info: Creating an environment gives you access to the Cloud Service Provider. This environment will function within the constraints of the task order, and any costs will be billed against the portfolio. csp_console_text: CSP console remove_member: alert: message: '{user_name} will no longer be able to access this application or any of its environments' button: Remove member header: Are you sure you want to remove this team member? delete: alert: message: You will lose access to this application and all environments will be removed from the CSP. Your reporting and activity will still be accessible. button: Delete application header: Are you sure you want to delete this application? enter_env_name: "Enter environment name:" environments: name: Name delete: button: Delete environment edit_name: Edit name environments_description: Each environment created within an application is logically separated from one another for easier management and security. environments_heading: Application environments existing_application_title: '{application_name} Application Settings' new_application_title: New Application settings_heading: Application Settings team_settings: blank_slate: action_label: Invite a new team member sub_message: Please contact your JEDI Cloud portfolio administrator to invite new members. title: There are currently no team members for this application. environments: Environments section: table: delete_access: Delete Access environment_management: Environment Management team_management: Team Management title: '{application_name} Team' subheading: Team Settings title: '{application_name} Team Settings' add_to_environment: Add to existing environment team_text: Team update_button_text: Save members: new: assign_roles: Assign Member Environments and Roles learn_more: Learn more about these roles manage_perms: 'Manage permissions for {application_name}' manage_envs: 'Allow member to add and rename environments within the application.' delete_envs: 'Allow member to delete environments within the application.' manage_team: 'Allow member to add, update, and remove members from the application team.' index: empty: start_button: Start a new JEDI portfolio title: You have no apps yet members: archive_button: Delete member permissions: app_mgmt: App management edit_access: Edit funding: Funding name: Name portfolio_mgmt: Portfolio management reporting: Reporting task_orders: review: pdf_title: Approved Task Order review_your_task_order: Review your task order funding_summary: Task Order Summary task_order_number: Task Order Number check_paragraph: Check to make sure the information you entered is correct. After submission, you will confirm this task order was signed by a contracting officer. Thereafter, you will be informed as soon as CCPO completes their review. supporting_document: title: Supporting document clins: amount: Amount obligated: Obligated pop_start: PoP Start pop_end: PoP End loa: LOA form: add_clin: Enter another CLIN add_loa: Enter another line of accounting 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" 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. loa_label: 'Enter line of accounting (43 characters)' 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' review_button: Review task order supporting_docs_header: Upload your supporting documentation supporting_docs_size_limit: Your file may not exceed 1MB supporting_docs_text: Upload a single PDF containing all relevant information. step_5: title: Confirm Signature description: Finally, plase confirm that your uploaded document representing the information you've entered contains the required signature from your Contracting Officer. You will be informed as soon as CCPO completes their review. alert_message: All task orders require a Contracting Officer signature. next_button: 'Next: Confirm & Submit' sticky_header_text: 'Add Funding ({step} of 5)' new: form_help_text: Before you can begin work in the cloud, you'll need to complete the information below and upload your approved task order for reference by the CCPO. app_info: project_title: Project details subtitle: Who will be involved in the work funded by this task order? team_title: Your team sign: digital_signature_description: I acknowledge that the uploaded task order contains the required KO signature. JEDICLINType: JEDI_CLIN_1: 'Base CLIN 0001: Unclassified IaaS and PaaS' JEDI_CLIN_2: 'CLIN 2: Classified Cloud Services - 0002' JEDI_CLIN_3: 'CLIN 3:' JEDI_CLIN_4: 'CLIN 4:' testing: example_string: Hello World example_with_variables: 'Hello, {name}!' nested: example: Hello nested example