---
title: Design Sync Notes — Diddy Project Status
type: article
created: '2025-11-17'
updated: '2025-11-17'
source_docs:
- raw/2025-11-17-design-team-sync-102079497.md
tags:
- diddy
- design
- wordpress
- email-marketing
- linkedin
- client-blockers
- meeting-notes
layer: 2
client_source: Didion Milling
industry_context: food-beverage
transferable: false
---

# Design Sync Notes — Diddy Project Status

Notes from the [[wiki/meetings/2025-11-17-design-team-sync|Design Team Sync — 2025-11-17]] covering active blockers, immediate fixes, and upcoming campaign work for the Diddy project.

## Overview

The Diddy project is progressing but faces a significant technical blocker: the client's existing WordPress site uses a restrictive page builder that the team does not control and did not configure. This limits what can be implemented relative to the approved designs. Several immediate fixes and upcoming campaign deliverables were discussed.

## Active Blockers

### WordPress Builder Limitations

The development team (Ishak) is working within a WordPress environment owned and configured by the client. The page builder in use is not one the team selected, and it imposes constraints on layout implementation — particularly around overlapping elements and header behavior. This has caused frustration and is slowing implementation of the approved designs.

> *"I know he's struggling with, like, I bet you he can't overlap it… he's having a hard time figuring it out."* — Melissa Cusumano

The header and footer also need to be updated to match the existing site's styling, adding additional complexity outside the team's direct control.

## Immediate Action Items

| Owner | Task | Notes |
|-------|------|-------|
| Michał | Fix header image (wrong photo on hover) | Spec was in the brief but missed; should show tortilla image on hover for the second Diddy link |
| Michał | Organize project assets | Move unused files into an "Unused" subfolder so approved images are clearly separated |
| Mylene | Build LinkedIn Organic Campaign | Use Michał's organized/approved assets; includes hashtag research and scheduling recommendations |
| Melissa | Create tasks for two new email marketing campaigns | Phase 2 drip/direct mail campaigns; focus on these two for the coming week |

### Header Image Fix — Detail

Michał used a photo that appears correctly in the design file, but when a user hovers over the second Diddy link on the page, it displays the wrong image. The spec called for a tortilla image in that context. This was a missed detail in the brief rather than a design error.

### Asset Organization — Detail

All gathered assets currently live in a single folder, including images that were collected but not used in final designs. Michał will create an "Unused" subfolder to isolate those, ensuring Mylene (and future team members) only pull from approved, in-use imagery for campaign work.

## Upcoming Campaign Work

### LinkedIn Organic Campaign

Assigned to Mylene. She will:
- Use approved assets from Michał's organized folder
- Conduct hashtag research
- Recommend a posting schedule

Michał may need to design additional assets if Mylene identifies gaps after reviewing what's available.

### Email Marketing Campaigns (Phase 2)

Two drip/direct mail email campaigns are the next deliverables. Melissa noted that content was requested from the client as far back as November 5th with no response. The team may need to move forward with internally drafted copy. Melissa will create formal tasks for these.

## Context & Background

- The Diddy project has undergone naming and product-definition changes during its lifecycle, which has complicated content development.
- The client's slow content turnaround is a recurring pattern on this account.
- The LinkedIn campaign was originally considered for Michał but reassigned to Mylene given his existing workload (Financial Utesk designs, Diddy fixes).

## Related

- [[wiki/clients/current/didion/_index|Diddy Client Overview]]
- [[wiki/meetings/2025-11-17-design-team-sync|Design Team Sync — 2025-11-17]]
- [[wiki/knowledge/client-blockers/unresponsive-clients|Handling Unresponsive Clients]]
- [[wiki/knowledge/wordpress/builder-limitations|WordPress Builder Constraints]]