Imagine a studio in Bağlarbaşı, Maltepe, preparing a project page for a client who has agreed to publication without its name. The text calls it a local retailer, but a screenshot includes its logo in a browser tab. Review the assets a visitor can actually open as part of the same editorial check.
Record the publication agreement in plain language
List the facts the client agreed to share, such as the type of shop, the problem and the scope of work. Give the team a short inventory of details that reveal the identity, including a customer domain, a logo or a named dashboard user. Make the inventory available to the person approving the public files.
Export the screenshots and attachments again
Use sample data or blank out identifying details where they do not affect the story. Check the exported picture at full size, including windows and tabs. Open the generated PDF, search for the original client name and view its document properties. Review any thumbnail, image filename and download link that the CMS creates.
Open the preview the way a visitor would
Use a signed-out browser to open the project page. Follow every public link on it and inspect the downloads, source images and social sharing preview. Ask someone who did not create the portfolio piece to compare what they can see with the agreed inventory. Check the same assets from both language versions.
Limit new uploads to the approved copies
Put the approved exports in the publication folder and keep the original work files in the project area with their existing access controls. Write down the names of the approved files and the last review date. Repeat the asset check when replacing a screenshot or adding a translated download.
Checklist before publishing
- Publication agreement includes the details allowed
- Full size images and PDFs reviewed
- Signed-out links checked in both languages
- Approved exports identified for future editors