Glossary
  • Updated on 21 Dec 2019
  • 1 minute to read
  • Print
  • Share
  • Dark
    Light

Glossary

  • Print
  • Share
  • Dark
    Light

The Glossary section in the Back Office is mostly used by administrators when a new locale for a store needs to be set up. In case no new locale needs to be set up, the Marketing Content Manager or Spryker Admin can use this section in order to improve the existing content (translations).

Standardized flow of actions for a DevOps
Flow of actions for DevOps

This is how the DevOps interacts with the Development Team and uses the Back Office to set up a new locale for a store.

A glossary consists of

  • a glossary key (which is used in the templates contained in the shop application)
  • a glossary value for each locale defined in the online store

You can manage the translations, however, when creating or updating a glossary key, the changes are persisted in the back-end database. The changes are available in the online store after the client data storage is updated (either by manually running the update storage command or after the cronjob that does this update was executed. That is why interaction with the Development Team is needed.


What's next?
To know how the translations are managed, see Managing Glossary.

Was this article helpful?