pk/atst
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Merge branch 'master' into title-error-message

Browse Source
This commit is contained in:
rachel-dtr
2019-02-14 10:53:47 -05:00
committed by GitHub
parent e1c93173ec 6cf0423397
commit 942b557067
108 changed files with 4803 additions and 2121 deletions
Download Patch File Download Diff File Expand all files Collapse all files

110
translations.yaml
View File

@@ -7,7 +7,6 @@
# `{{ "login.title" | translate | safe }}`
audit_log:
events:
default:
@@ -20,7 +19,9 @@ base_public:
login: Log in
title_tag: JEDI Cloud
common:
back: Back
save_and_continue: Save & Continue
sign: Sign
components:
modal:
close: Close
@@ -76,7 +77,7 @@ forms:
date_latest_training_label: Latest Information Assurance (IA) Training Completion Date
designation_description: What is your designation within the DoD?
designation_label: Designation of Person
email_description: Enter your preferred contact e-mail address
email_description: Enter your preferred e-mail address
email_label: E-mail Address
first_name_label: First Name
last_name_label: Last Name
@@ -173,7 +174,7 @@ forms:
environment_names_label: Environment Name
environment_names_required_validation_message: Provide at least one environment name.
environment_names_unique_validation_message: Environment names must be unique.
name_label: Application Name
name_label: Name
task_order:
portfolio_name_label: Organization Portfolio Name
portfolio_name_description: The name of your office or organization. You can add multiple applications to your portfolio. Your task orders are used to pay for these applications and their environments.
@@ -182,15 +183,15 @@ forms:
defense_component_label: Department of Defense Component
app_migration:
label: App Migration
description: Do you plan to migrate existing application(s) to the cloud?
description: Do you plan to migrate one or more existing application(s) to the cloud?
on_premise: Yes, migrating from an <strong>on-premise data center</strong>
cloud: Yes, migrating from <strong>another cloud provider</strong>
both: Yes, migrating from an <strong>on-premise data center</strong> and <strong>another cloud provider</strong>
none: Not planning to migrate any applications
not_sure: "Not Sure"
not_sure: "Not sure"
native_apps:
label: Native Apps
description: Do you plan to develop application(s) natively in the cloud?
description: Do you plan to develop any applications natively in the cloud?
'yes': Yes, planning to develop natively in the cloud
'no': No, not planning to develop natively in the cloud
not_sure: Not sure, unsure if planning to develop natively in the cloud
@@ -202,12 +203,12 @@ forms:
conus: CONUS Access
oconus: OCONUS Access
tactical_edge: Tactical Edge Access
not_sure: Not Sure
not_sure: Not sure
other: Other
complexity_other_label: Project Complexity Other
dev_team:
label: Development Team
description: Which people or teams will be completing the development work for your cloud applications? Select all that apply.
description: Who will be completing the development work for your cloud application(s)? Select all that apply.
civilians: Government Civilians
military: Military
contractor: Contractor
@@ -218,8 +219,8 @@ forms:
description: How much experience does your team have with development in the cloud?
none: No previous experience
planned: Researched or planned a cloud build or migration
built_1: Built or Migrated 1-2 applications
built_3: Built or Migrated 3-5 applications
built_1: Built or migrated 1-2 applications
built_3: Built or migrated 3-5 applications
built_many: Built or migrated many applications, or consulted on several such projects
performance_length:
label: Period of Performance length
@@ -244,7 +245,7 @@ forms:
cor_invite_label: Invite COR to Task Order Builder
so_invite_label: Invite Security Officer to Task Order Builder
skip_invite_description: |
<i>You may choose to skip this for now and invite them later.</i>
<i>An invitation won't actually be sent until you click Done on the Review page. You can skip this for now and invite them later.</i>
validators:
is_number_message: Please enter a valid number.
list_item_required_message: Please provide at least one.
@@ -255,10 +256,13 @@ forms:
portfolio:
name_label: Portfolio Name
name_length_validation_message: Portfolio names can be between 4-100 characters
officers:
contracting_officer_invite: Invite KO to Task Order Builder
contracting_officer_representative_invite: Invite COR to Task Order Builder
security_officer_invite: Invite SO to Task Order Builder
fragments:
edit_application_form:
existing_application_title: 'Edit {application_name} application'
explain: 'AT-AT allows you to organize your portfolio into multiple applications, each of which may have environments.'
explain: 'AT-AT allows you to create multiple applications within a portfolio. Each application can then be broken down into its own customizable environments.'
new_application_title: Add a new application
edit_user_form:
date_last_training_tooltip: When was the last time you completed the IA training? <br> Information Assurance (IA) training is an important step in cyber awareness.
@@ -274,11 +278,11 @@ fragments:
learn_more_link_text: Learn more about the JEDI Cloud Task Order and the Financial Verification process.
paragraph_1: 'The next step is to create a Task Order associated with JEDI Cloud. Please contact a Contracting Officer (KO), Contracting Officer Representative (COR), or a Financial Manager to help with this step.'
paragraph_2: 'Once the Task Order has been created, you will be asked to provide details about the task order in the Financial Verification step.'
ko_review_alert:
make_sure: Make sure to take a moment to
bullet_1: Verify that all information is accurate and up-to-date
ko_review_message:
title: Steps
bullet_1: Make sure the information below matches the final task order and is accurate and up-to-date
bullet_2: Upload your Task Order (TO) document
bullet_3: Add both the Task Order (TO) and Lines of Accounting (LOA)
bullet_3: Add both the Task Order (TO) and Line(s) of Accounting (LOA) numbers
login:
ccpo_logo_alt_text: Cloud Computing Program Office Logo
certificate_selection:
@@ -305,6 +309,11 @@ navigation:
applications: Applications
portfolio_funding: Funding
portfolio_settings: Portfolio Settings
portfolio_admin: Portfolio Administration
breadcrumbs:
admin: Admin
funding: Funding
reports: Reports
requests:
_new:
new_request: New Request
@@ -394,26 +403,43 @@ requests:
questions_title_text: Questions related to JEDI Cloud migration
rationalization_software_systems_tooltip: Rationalization is the DoD process to determine whether the application should move to the cloud.
task_orders:
sign:
digital_signature_description: I acknowledge that I have read and fully understand the DoD CCPO JEDI agreements and completed all the necessary steps, as detailed in the FAR (Federal Acquisition Regulation).
digital_signature_label: Digital Signature
level_of_warrant_description: This is a dollar value indicating that you have permission to sign any Task Order under this max value.
level_of_warrant_label: Level of Warrant
task_order_builder_title: Task Order Builder
title: Sign Task Order
unlimited_level_of_warrant_description: Unlimited Level of Warrant funds
verify_warrant_level_paragraph: Verify your level of warrant and provide your digital signature to authorize this Task Order.
view:
whats_next: Here are the remaining tasks to get your Task Order approved.
steps:
draft: '<strong>Primary Point of contact ({contact})</strong> completes initial Task Order form.'
security: '<strong>IA Security Officer ({security_officer})</strong> completes a Security Requirements Document. <a href="#">Send a reminder</a>'
record: '<strong>Contracting Officer ({contracting_officer}) or Contracting Officer Representative ({contracting_officer_representative})</strong> records Task Order information. <a href="#">Send a reminder</a>'
record_description: Obtain a funding document and file a Task Order in the appropriate system of record. Once this is complete, come back here and record the task order information.
sign: '<strong>Contracting Officer ({contracting_officer})</strong> verifies funding to unlock cloud services.'
new:
app_info:
section_title: "What You're Making"
basic_info_title: Basic information
basic_info_title: Basic Information
sample_scope: |
Not sure how to describe your scope? <a href="#">Read some Sample Scopes</a> to get an idea of what is appropriate.
project_title: About your project
team_title: About your team
Not sure how to describe your scope? <a href="#">Read some examples</a> to get some inspiration.
project_title: About Your Project
team_title: About Your Team
market_research_title: Market Research
market_research_paragraph: 'The JEDI Cloud Computing Program Office (CCPO) has completed the market research requirements for all related task orders. The Department of Defense CIO has approved this research.<br /><a href="#">View JEDI Market Research Memo</a>'
funding:
section_title: Funding
performance_period_title: Period of Performance
performance_period_description: Choose the length of time your task order will cover.
performance_period_paragraph: Because your funds will be lost if you don’t use them, we strongly recommend submitting small, short-duration task orders, usually a three month period. We’ll notify you when your period of performance is nearing the end so you can request your next set of funds with a new task order.
performance_period_paragraph: Be aware that your funds will be lost if you don’t use them. Because of this, we strongly recommend submitting small, short-duration task orders, usually around a three month period. We’ll notify you when your period of performance is nearing its end so you can request your next set of funds with a new task order.
estimate_usage_title: Estimate Your Cloud Usage
estimate_usage_description: Calculate how much your cloud usage will cost. A technical representative from your team should help you complete this calculation. These calculations will become your CLINs.
estimate_usage_paragraph: This is only an estimation tool to help you make an informed evaluation of what you expect to use. While you're tied to the dollar amount you specify in your task order, you're not obligated by the resources you indicate in the calculator.
cloud_calculations_title: Cloud Usage Calculations
cloud_calculations_paragraph: Enter the results of your cloud usage calculations.
cloud_calculations_paragraph: Enter the results of your cloud usage calculations below.
cloud_offerings_title: Cloud Offerings
cloud_offerings_paragraph: Infrastructure as a Service (IaaS) and Platform as a Service (PaaS) offerings
support_assistance_title: Cloud Support and Assistance
@@ -422,8 +448,9 @@ task_orders:
oversight:
section_title: Oversight
ko_info_title: Contracting Officer (KO) Information
ko_info_paragraph: Your KO will need to approve funding for this Task Order by logging into the JEDI Cloud Portal, submitting the Task Order documents within their official system of record, and electronically signing. You might want to work with your program Financial Manager to get your TO documents moving in the right dirction.
ko_info_paragraph: Your KO will need to approve funding for this Task Order by logging into the JEDI Cloud Portal, submitting the Task Order documents within their official system of record, and then finally providing a digital signature. It might be helpful to work with your program's Financial Manager to get your TO documents moving.
skip_ko_label: "Skip for now (We'll remind you to enter one later)"
dod_id_tooltip: "The DoD ID is needed to verify the identity of the indicated officer or representative."
cor_info_title: Contracting Officer Representative (COR) Information
cor_info_paragraph: Your COR may assist in submitting the Task Order documents within their official system of record. They may also be invited to log in and manage the Task Order entry within the JEDI Cloud portal.
so_info_title: Security Officer Information
@@ -438,7 +465,7 @@ task_orders:
complexity: Project Complexity
team: Development Team
funding: Funding
performance_period: Period of Performance length
performance_period: Period of Performance
usage_est_link: View Usage Estimate
to_value: Task Order Value
clin_1: 'CLIN #1: Unclassified Cloud'
@@ -454,28 +481,55 @@ task_orders:
invited: Invited
not_invited: Not Yet Invited
not_uploaded: Not Uploaded
pending_to: Pending TO Completion
invitations:
dod_id_label: DoD ID
edit_text: A new invitation e-mail will be sent when new information is saved.
contracting_officer:
title: Contracting Officer (KO) Information
description: You'll need a signature from your KO. You might want to work with your program Financial Manager to get your TO documents moving in the right direction.
add_button_text: Add / Invite KO
invite_button_text: Invite KO
edit_title: Edit KO
contracting_officer_representative:
title: Contracting Officer Representative (COR) Information
description: Your COR may assist in submitting the Task Order documents within their official system of record.
add_button_text: Add / Invite COR
invite_button_text: Invite COR
edit_title: Edit COR
security_officer:
title: IA Security Officer Information
description: Your Security Officer will need to answer some security configuration questions in order to generate a DD-254 document, then digitally sign.
add_button_text: Add / Invite Security Officer
invite_button_text: Invite Security Officer
edit_title: Edit SO
ko_review:
alert_title: Verify Your Info
title: Task Order Builder
submitted_by: Below is an overview of the projected portfolio submitted by {name}
title: Verify Task Order Information
message: Grant your team access to the cloud by verifying the Task Order info below.
review_title: Task Order Builder
task_order_information: Task Order Information
portfolios:
index:
empty:
title: You have no apps yet
start_button: Start a New JEDI Portfolio
applications:
add_application_text: Add A New Application
app_settings_text: App Settings
team_text: Team
csp_console_text: CSP Console
existing_application_title: '{application_name} Application Settings'
new_application_title: New Application
settings_heading: Application Settings
environments_heading: Environments
environments_description: Each environment created within an application is logically separated from one another for easier management and security.
update_button_text: Save Changes
create_button_text: Create Application
team_management:
title: '{application_name} Team Management'
subheading: Team Management
admin:
activity_log_title: Activity Log
testing:
example_string: Hello World
example_with_variables: 'Hello, {name}!'