VBA Facility services need to have an alias pattern in the url (e.g., /portland-va-regional-benefit-office/service/portland-va-regional-benefit-office-veterans-pension)
Acceptance Criteria
[ ] A VBA Facility Service follows this pattern: [node:field_office:entity:title]/service/[node:title]
[ ] Creating a facility results in this pattern
[ ] Changing the facility name and resaving the service results in an updated url path
Add the equivalent pattern for VBA Facility service to this example from Vet Centers - Facility Service: [node:field_office:entity:title]/service/[node:title]
Design principles
Veteran-centered
[x] Single source of truth: Increase reliability and consistency of content on VA.gov by providing a single source of truth.
[ ] Accessible, plain language: Provide guardrails and guidelines to ensure content quality.
[x] Purposely structured content: Ensure Content API can deliver content whose meaning matches its structure.
[ ] Content lifecycle governance: Produce tools, processes and policies to maintain content quality throughout its lifecycle.
Editor-centered
[ ] Purpose-driven: Create an opportunity to involve the editor community in VA’s mission and content strategy goals.
[x] Efficient: Remove distractions and create clear, straightforward paths to get the job done.
[ ] Approachable: Offer friendly guidance over authoritative instruction.
[x] Consistent: Reduce user’s mental load by allowing them to fall back on pattern recognition to complete tasks.
[ ] Empowering: Provide clear information to help editors make decisions about their work.
User Story or Problem Statement
VBA Facility services need to have an alias pattern in the url (e.g.,
/portland-va-regional-benefit-office/service/portland-va-regional-benefit-office-veterans-pension
)Acceptance Criteria
Implementation steps
[node:field_office:entity:title]/service/[node:title]
Design principles
Veteran-centered
Single source of truth
: Increase reliability and consistency of content on VA.gov by providing a single source of truth.Accessible, plain language
: Provide guardrails and guidelines to ensure content quality.Purposely structured content
: Ensure Content API can deliver content whose meaning matches its structure.Content lifecycle governance
: Produce tools, processes and policies to maintain content quality throughout its lifecycle.Editor-centered
Purpose-driven
: Create an opportunity to involve the editor community in VA’s mission and content strategy goals.Efficient
: Remove distractions and create clear, straightforward paths to get the job done.Approachable
: Offer friendly guidance over authoritative instruction.Consistent
: Reduce user’s mental load by allowing them to fall back on pattern recognition to complete tasks.Empowering
: Provide clear information to help editors make decisions about their work.