ADVANCED COMPOSITING & RETOUCHING - Chapter 4, Exercise 3
Updating a Logo Everywhere at Once with a Linked Smart Object
====================================================================================

QUESTION:
A logo appears in twelve different composite files, and the client asks for
its color to be updated everywhere at once. Explain how a linked Smart Object
would solve this in Photoshop, and what the practical downside of using one
is.

SOLUTION / EXPLANATION:

If the logo had been placed into all twelve files as a LINKED Smart Object -
referencing one external logo file on disk, rather than twelve separate
embedded copies of the artwork baked individually into each PSD - then
updating the color would only require editing that one external source
file once. Because a linked Smart Object doesn't store its own independent
copy of the artwork, but instead displays whatever the external file
currently contains, every one of the twelve composite files would
automatically reflect the updated color the next time each file is opened
(or immediately, if already open and the link is refreshed) - with no need
to manually open and re-edit all twelve individually.

This is precisely the scenario a linked Smart Object is designed for: the
same asset reused across many files, needing a single point of update
instead of scattered, error-prone repeated edits.

The practical downside named in this chapter: because a linked Smart Object
references an external file rather than storing the artwork inside the PSD
itself, the PSD is no longer fully self-contained. If that external logo
file is moved, renamed, or deleted - or if the twelve composite files are
copied to a different computer or folder structure without also bringing
the linked source file along, correctly preserving its relative path - the
link breaks, and each affected file will show a missing or outdated
placeholder instead of the logo. Anyone handling these files afterward needs
to know the external dependency exists and keep it intact, which an
embedded Smart Object (fully self-contained, but requiring twelve separate
manual updates instead of one) would not require.

--------------------------------------------------------------------------
WHY THIS WORKS AS AN ANSWER:
It explains specifically why a linked Smart Object solves the "update
everywhere at once" requirement (one external source, referenced rather
than duplicated), and then names the concrete, practical cost of that
approach (file-path fragility, loss of self-containment) rather than
presenting linked Smart Objects as a strictly better option with no
tradeoff.