Editing Openai/69511b0e-1e28-8006-850e-6bed4d5690a8 (section)

==== Key things to watch out for (important) ====

===== 1. Browser caching (this is the big one) =====

Browsers may cache images aggressively.

Mitigations:
* Configure the server to send: </code>`<code> Cache-Control: max-age=0, must-revalidate </code>`<code> or
* Add a query string in Elements if supported: </code>`<code> hero.jpg?v=1 </code>`<code> (then increment manually when needed)

If you don’t do this, some users may not see the updated image immediately.

===== 2. File dimensions must remain compatible =====

Because Elements layouts are static:
* Keep image dimensions and aspect ratios consistent
* Otherwise you risk: - Layout shifts - Cropping issues - Unexpected scaling

Best practice:
* Create a template image spec for each asset: - Width - Height - Format - Color profile

===== 3. Permissions & security =====

Make sure:
* Only authenticated users can upload
* Uploads are restricted to: - File type (jpg/png/webp) - Max size
* No executable files allowed

If RWC allows it, disable directory browsing for /resources/.

===== 4. Backup strategy (highly recommended) =====

Because you’re overwriting files:
* Keep a backup copy: </code>`<code> /resources_backup/ <syntaxhighlight>- Or version files before replace: </syntaxhighlight> hero_2025-01-12.jpg <syntaxhighlight>
This gives you rollback capability without republishing.

==== Nice refinements you could add ====
* Naming convention </syntaxhighlight> hero_home.jpg hero_about.jpg gallery_featured_01.jpg </code>`` Makes admin usage safer and clearer.
* Image optimization on upload - Compress on upload (if RWC supports it) - Prevents performance regressions
* Role separation - One CMS page only for images - No access to text or layout