Changing Knowledge Base Source Locale

/* * These styles apply ONLY to the header and footer assets. */ * { padding: 0; margin: 0; box-sizing: border-box; } .footer { background: #f5f5f6; color: #555a62; font-size: 14px; line-height: 1.5; padding: 18px 0; } .footer-wrap { padding-left: 18px; padding-right: 18px; max-width: 1236px; margin: 0 auto; } .footer a { color: #0291db; } .footer a:hover { color: #0276b3; } .footer-row { display: flex; flex-wrap: wrap; justify-content: space-between; align-items: center; margin: -3px; } .footer-col { padding: 0 3px; } .footer-col-copyRight { justify-content: flex-start; } .footer-col-logo { justify-content: flex-end; } .footer-col-copyRight, .footer-col-logo { flex: 1; display: flex; } .logo { width: 120px; height: 28px; opacity: 0.6; } @media screen and (max-width: 768px) { .footer-row { display: block; } .footer-col { width: 100%; text-align: center; margin: 6px 0; } .footer-col:first-child { margin-top: 0; } .footer-col:last-child { margin-bottom: 0; } .footer-col-copyRight, .footer-col-logo { justify-content: center; } .logo { margin: 0 auto; } } /*# sourceMappingURL=styles.css.map */

Changing Knowledge Base Source Locale - Vanilla Success

Changing your source locale can lead to articles disappearing and is not recommended. If you want to change the source locale, you should ensure the following:

You will need to edit the knowledge base name and description to make sure they are in the new source locale.
If the knowledge base has categories defined then you will have some editing to do to change the names into the new source locale.
If you have articles in the knowledge base then you should make sure that they are 100% translated before changing the source locale or else you will be left with some orphaned records.

In general, the source locale of a knowledge base is a fairly major decision so take care when creating a knowledge base in a multilingual environment.