Importing and exporting a theme

Exporting a theme gives you the backup and the version history the editor does not have. Do it before every change.

Exporting a theme gives you the backup and the version history the editor does not have. Do it before every change.

Export

1. Open the themes list in Knowledge.
2. Choose the theme and export it.
3. Save the file somewhere your team can find it, named with the date.

Import

1. Add a theme and import the file.
2. It arrives unpublished, so nothing changes for readers yet.
3. Preview it.
4. Publish when you are satisfied.

Why this is the backup that matters

The code editor saves over what was there. There is no history to step back through and no undo after the fact. An exported file from before the change is the entire safety net.

Name the files properly

Date and what changed. Three files called theme.zip in a downloads folder are worth roughly one file. The point of a backup is being able to identify which one to restore.

Moving a theme between accounts

Export from one, import into the other. Settings come along; content does not, and neither do any images you uploaded through the editor rather than into the theme's own assets.

Check images first after an import, because that is where the gaps show up.

Keep one known-good copy

Separate from the working exports: the last version everybody agreed looked right. That is what you restore to when a change goes wrong on a Friday.

See also

• Editing a theme's code
• How themes work
• My theme change is not showing