Skip to content

Commit 4dfac84

Browse files
Merge branch 'main' into authed-patterns/aw/185/add-syntax-highlighting-for-markdown-code-blocks
2 parents 7bcce33 + b956337 commit 4dfac84

File tree

3 files changed

+68
-3
lines changed

3 files changed

+68
-3
lines changed

src/_about/updating-this-site.md

+8-2
Original file line numberDiff line numberDiff line change
@@ -15,8 +15,14 @@ The [wiki](https://github.com/department-of-veterans-affairs/vets-design-system-
1515
- [New page templates](https://github.com/department-of-veterans-affairs/vets-design-system-documentation/wiki/Adding-content)
1616
- [HTML snippets](https://github.com/department-of-veterans-affairs/vets-design-system-documentation/wiki/Writing-snippets) for enhanced content presentation
1717

18-
You can make updates directly in GitHub without any expertise in writing code as long as you write with markdown. When you are done with your work, create a new branch and submit a pull request.
18+
You can make updates directly in GitHub without any expertise in writing code as long as you write with markdown. When you are done with your work, create a new branch and submit a pull request.
19+
20+
Watch [this tutorial](https://www.youtube.com/watch?v=kXwhzUg1lKA) if you need to make multiple changes at one time like adding an image to a page. If you try to add an image to a page directly in GitHub you would have to create two pull request. A better option would be to bundle the image and edits to the page into one pull request. An added benefit to bundling your changes is being able to preview all your changes in one place. Follow the instructions below for more information on previewing your pull request.
21+
22+
### Preview your changes
23+
24+
When making updates to documentation you can preview your changes before publishing them to the live site. When you create a pull request or a draft pull request, a preview link is created where you can view the entire documentation site with the changes that you submitted before publishing those changes to the live site. Follow [these instructions](https://github.com/department-of-veterans-affairs/vets-design-system-documentation?tab=readme-ov-file#previewing-pull-requests) or watch this [demo on YouTube (9:41)](https://youtu.be/kXwhzUg1lKA?feature=shared&t=581) to see the preview link in action.
1925

2026
## Updating CSS and this site
2127

22-
For instructions on how to update this site and while making changes to CSS, [see the README](https://github.com/department-of-veterans-affairs/vets-design-system-documentation#vets-design-system-documentation).
28+
For instructions on how to update this site and while making changes to CSS, [see the README](https://github.com/department-of-veterans-affairs/vets-design-system-documentation#vets-design-system-documentation).
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,59 @@
1+
---
2+
layout: content-style-guide
3+
permalink: /content-style-guide/specific-topics-and-programs/claims-and-applications
4+
has-parent: /content-style-guide/specific-topics-and-programs/
5+
title: Claims and applications
6+
intro-text: "The information on this page will help you use consistent language about claims and applications across communication channels."
7+
anchors:
8+
- anchor: Considerations
9+
- anchor: Related terms
10+
- anchor: Resources
11+
---
12+
13+
## Considerations
14+
15+
- We use the terms "claim" and "application" intentionally, and they often aren't interchangeable. We also use other related terms like "request" and "authorization" to refer to other types of VA forms.
16+
- In reusable content that appears in many types of applications, requests, and static pages (like an alert), use the general term "form" instead of "claim," "application," or "request" to avoid confusion.
17+
Like this: "Thank you for submitting your form on VA.gov"
18+
Not this: "Thank you for submitting your application on VA.gov"
19+
- Updated standards can take time to implement across all content on VA.gov pages and interactive forms and tools. Existing content on VA.gov, including the claims status tool, may not always reflect the latest decisions documented here. If you have questions about any content, feel free to ask the content and information architecture (CAIA) team.
20+
21+
**Note:** We're working on style guidance for additional types of VA forms and for how to refer to different people involved in submitting forms, like third-party representatives. Check back soon.
22+
23+
## Related terms
24+
25+
**application** (noun) and **apply** (verb)
26+
: We use this term in the context of someone submitting an initial application for benefits. In general, a Veteran will "apply" for any non-disability benefit (including pension and DIC benefits) and "file a claim" for disability.
27+
28+
**claim** (noun) and **file a claim** (verb)
29+
: In most cases we use this term in the context of someone filing a disability claim. We also use this term in the context of reimbursement and after someone applies for a benefit and has been judged eligible. For example, a Veteran may file a travel reimbursement claim or a life insurance claim. We use this term to reflect that Veterans who are filing for disability-or filing a claim for reimbursement-have a right to that compensation.
30+
31+
**claimant** and **applicant**
32+
: We sometimes use this term to refer to the person with the claim or the person applying for the benefit—especially if the person is not a Veteran, or if they are not the person submitting the form (for example: "I'm signing for the claimant"). Always define the term on the first instance as "person with the claim" or "person applying for this benefit." When possible, use specific plain language instead, like "Veteran's spouse" or "Veteran's child."
33+
34+
Like this: "I'm the spouse, dependent, survivor, or caregiver of a Veteran, and I have an existing claim."
35+
Not this: "I'm a non-Veteran claimant."
36+
37+
**claim exam**
38+
: We use claim exams to determine if a Veteran has a service-connected disability. We also use claim exams to rate that disability.
39+
: - Note: This term is evolving. For now, on first mention on a page, use “VA claim exam (also known as a compensation and pension, or C&P, exam).” After first mention, use “VA claim exam” or “claim exam.”
40+
41+
**file** (noun)
42+
: We use this term to refer to the actual file a Veteran is uploading from their device. These may not be “documents” as in .doc. They could be .pdf, .jpg, .png, or other file types.
43+
: - Note: Button text on file upload screens should say "Upload file," not "Upload document" or "Upload evidence."
44+
45+
**document**
46+
: We use this term to refer to the digital or paper item a Veteran is submitting as evidence.
47+
: - Note: File input screens in form flows should use "document" in the screen header. For example, "Upload your supporting documents."
48+
49+
**evidence**
50+
: We use evidence to refer to all documents and information you submit to support your claim or application. We define evidence as “supporting documents or information.” Supporting documents and other information become evidence when they get attached to a claim or application.
51+
52+
**sponsor**
53+
: We use this word in forms and other content to refer to the Veteran who earned the benefits that a family member may be using. It's OK to use the word sponsor but lead with the plain language definition.
54+
55+
Example: the Veteran you're connected to (called your "sponsor")
56+
57+
## Resources
58+
59+
- [Check your VA claim, decision review, or appeal status](https://www.va.gov/claim-or-appeal-status/)

src/_content-style-guide/specific-topics-and-programs/index.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -6,6 +6,7 @@ intro-text: "Read this page to learn how this style guide section can help you a
66
sub-pages:
77
- sub-page: Payments and debts
88
- sub-page: Sign in and identity verification
9+
- sub-page: Claims and applications
910
---
1011

1112
## How this section helps VA content creators
@@ -44,7 +45,6 @@ We’ll continue to add entries to this section over time.
4445
Entries coming soon:
4546

4647
- Appointments
47-
- Claims
4848
- Medical records
4949
- Messaging
5050
- Prescriptions

0 commit comments

Comments
 (0)