cityofaustin / cityofaustin/techstack
Non-translatable fields
- Dominant language
- No language data
- Stars
- 11
- Forks
- 3
- PR merge metrics
- No merged PRs in 30d
Description
We have fields that are global across languages (aka we don't want folks to translate them).
**Acceptance criteria**
- [ ] Global fields are present when editing in Spanish
- [ ] Design matches mock below
- [ ] Lock icon to the right of a non-editable field
- [ ] Tool tip when hovering over icon says "Translation not required"
- [ ] global fields are not editable when editing in Spanish
Where this needs to happen
- [ ] Department page
- [ ] Name (to find this field: 1. Scroll down to "Department Directors" 2. Click "Add department directors" 3. See "Name" field)
- [ ] ~~Official document list page~~
- [ ] ~~Link to Document (URL) (to find this field: 1. Scroll down to "Entries will be listed by document date (newest first)." 2. Click "Add documents" 3. See "Link to Document (URL)" field)~~

https://material.io/resources/icons/?search=lock&icon=lock&style=baseline
----------
**Background**
See #2744.
Screengrab of currently implementation—the "name" field is global (carries over from English to Spanish) but the "title" field is a translatable field.

Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.