10 / Long-term care
Updates, translation & maintenance
Keep your customizations portable and your store understandable after updates.
Update the theme
- Back up both the database and files and test on a staging copy.
- Review the new release notes and any data migration instructions.
- Install the new theme ZIP through your approved update workflow. If replacing an installed theme manually, confirm the name/version before replacing it.
- Inspect saved Site Editor template overrides: a customized template can continue to take precedence over updated theme files. Back it up before selectively resetting it.
- Check header/navigation, a product, account screens, cart and checkout. Publish the tested update when your store’s workflow allows it.
Keep your own changes
Use the Site Editor and page/product editors for normal content changes. For PHP/CSS code changes, use a child theme or an appropriate custom plugin so an update does not overwrite the files you edited. Keep a record of additional CSS and the template/part each change affects. Purlia is a block theme; there is no separate theme-options framework to maintain.
Translate the store
- Choose the WordPress site language under Settings → General.
- For theme interface strings, use a translation tool that supports the text domain
purlia. The source catalog islanguages/purlia.pot. - Store custom translation files in the location recommended by your translation tool so updates retain them.
- Translate sample pages, product descriptions, Navigation labels and form content separately in their editors.
- Preview long translations on mobile, including buttons, notices, product titles and submenu items.
WordPress/WooCommerce/plugin translations are separate from theme translations. Changing the site language does not rewrite English demo content you imported.
Maintain images and caching
- Upload sensibly sized, compressed images and confirm Media thumbnails are generated by the host.
- Use the native image ID rather than pasting theme-file URLs into page HTML.
- Let WordPress or your chosen optimization plugin handle responsive image delivery. Purlia retains Media metadata.
- Cache public pages appropriately for your host, while excluding personalized Cart, Checkout, My Account and cart API responses.
- After optimization changes, test variation selection, AJAX add to cart, the drawer and checkout. Do not treat one Lighthouse run as a guaranteed score for every store.
Review after design changes
- Keep text readable against its background and do not remove visible keyboard focus.
- Use meaningful headings, link text, field labels and image alternative text.
- Check menu, Search and the cart drawer using Tab, Shift+Tab and Escape.
- Preview content at narrow widths and with enlarged text.
- Use real, readable error messages and confirm controls can be reached without a mouse.
If you need to roll back
Use the matched database/files backup from before the update, or restore only the specific content/template revision when the issue is isolated. A previous theme ZIP does not reverse a content migration by itself. Keep staging and the public store clearly separated while investigating.