Quick answer
Use the CMS's normal content model for content and its supported extension system for code. Editing rendered HTML or database rows directly can bypass revisions, sanitization, relationships, and cache behavior. Choose the layer that owns the change rather than the first file an assistant finds.
Apply this guidance to your website task
- Choose the WordPress content owner
- Choose the Joomla content owner
- Choose a code-level WordPress operation
Before you start
Identify the CMS, page builder, theme, plugins, and where the affected element is actually stored. Keep a backup and development copy, especially when a site uses serialized settings, commerce records, or custom integrations.
What to do
- Inspect the relevant page or template through the CMS and determine whether the item is content, theme presentation, plugin functionality, or external data.
- For text and media, prefer the editor or supported API. For presentation, use the intended theme or child-theme mechanism. For behavior, use a maintained extension path.
- Avoid direct database edits unless the CMS-supported method cannot perform the task and a qualified developer has a specific migration and rollback plan.
- Review the change in staging, including other pages that share the same template or global setting, before publication.
Check the result
Confirm that the result remains editable in the normal CMS and survives cache clearing or a normal update. Test the shared template and mobile presentation, not only the original page.
If something does not work
If an assistant proposes editing generated cache files or doing a broad SQL replacement, ask it to trace the authoritative source first. Do not let a quick visual fix corrupt the content model.
Related help
- Find the correct editor for a WordPress page
- Keep WordPress theme customizations separate from parent theme updates
- Import a website database without overwriting the wrong data
Official references
Reviewed October 31, 2026. Interfaces, vendor availability, and account features can change. Check your current account before making changes.
AI editing guidance and linked workflow documentation reviewed November 2, 2026. Existing video and earlier review history retained.
