Key takeaways

In this module, you learned how to:

• Folder names follow a specific convention that differs from the display title. The folder title is the human-readable label you see in the interface — it can have spaces, capitalization, and special characters. The name (which becomes part of the URL and repository path) is auto-generated as all lowercase with dashes replacing spaces and special characters. This is the SEO-friendly naming convention used throughout AEM's content repository, so it's worth understanding rather than fighting it.
• "Append mode" in bulk metadata updates adds to existing values rather than replacing them. This matters specifically for multi-value fields like tags. Without append mode, a bulk update overwrites all existing tags on the selected assets. With append mode enabled, the new tags are added alongside whatever was already there — making it safe to enrich metadata without accidentally erasing prior work.
• Renditions are automatically generated alternate versions of an asset, not version history. When an asset is uploaded or reprocessed, AEM's microservices automatically create renditions — resized or reformatted copies used in different contexts within the interface and downstream channels. These are distinct from saved versions in the timeline, which represent earlier states of the same asset for rollback purposes.
• When a filename conflict occurs on upload, "Create a Version" is almost always the right choice. AEM gives you three options: Replace (overwrites the asset entirely, losing all metadata and history), Keep Both (renames the new file and keeps both), and Create a Version (updates the binary while preserving all existing metadata, tags, and version history). Create a Version is the recommended option when you want to maintain continuity of an asset's lifecycle.
• Check an asset's References tab before requesting deletion. When AEM deletes an asset from the author instance, it automatically deactivates the corresponding content on the publish instance — which means any live web page that references that asset will break. Checking References first tells you exactly which pages are affected, so you can update or remove those references before proceeding with deletion.