...
To translate ArchivesSpace using files directly from GitHub, you will need to translate the following five en.yml filesin the following five directories. These five files (public, common, enums, frontend, and frontend_help) create all the labels and other text in the interface.
common (for many labels shared across the application): https://github.com/archivesspace/archivesspace/tree/master/common/locales
enums (for controlled value lists entries) https://github.com/archivesspace/archivesspace/tree/master/common/locales/enums
frontend (for many labels and messages in the staff interface) https://github.com/archivesspace/archivesspace/tree/master/frontend/config/locales
frontend help (for context-sensitive help link labels and tooltips) https://github.com/archivesspace/archivesspace/tree/master/frontend/config/locales/help
public (for many labels and messages in the public interface) https://github.com/archivesspace/archivesspace/tree/master/public/config/locales
...
Create a branch of your own, copying what’s in the en.yml files to a new file title. Title the file using an the abbreviation of the language you are translating the English (en) files into.
Translate as many of the entries in the files as you can.
Submit a pull request with the translations to Github when you’re ready to contribute the translation to the application.
...