2025
Procore
Procore
Procore
A scalable Product Updates Newsletter template system for recurring launch, feature release, coming-soon, and beta communications.
A scalable Product Updates Newsletter template system for recurring launch, feature release, coming-soon, and beta communications.
A scalable Product Updates Newsletter template system for recurring launch, feature release, coming-soon, and beta communications.
Campaign Design
Web Production
Figma Components
Role
Lead visual designer for the Product Updates Newsletter system, including desktop and mobile layouts, reusable modules, and a visual kit.
Timeline
August 2025
Audience
Procore marketing and product communication teams.
Deliverables
Newsletter templates, reusable release modules, monthly headers, responsive layouts, and content rules.
What changed
What changed
The work turned a recurring campaign into a governed template system that teams could assemble faster without sacrificing clarity, consistency, or responsive behavior.
The work turned a recurring campaign into a governed template system that teams could assemble faster without sacrificing clarity, consistency, or responsive behavior.
16
Monthly header covers
4
Standard release modules
01 / Solution
Turning a campaign into reusable modules
Turning a campaign into reusable modules
Turning a campaign into reusable modules
A centralized component toolkit
I packaged the newsletter into reusable parts — header, release sections, solution blocks, prefooter, footer, and icon set — so each issue could be assembled from governed building blocks.
A centralized component toolkit
I packaged the newsletter into reusable parts — header, release sections, solution blocks, prefooter, footer, and icon set — so each issue could be assembled from governed building blocks.
A centralized component toolkit
I packaged the newsletter into reusable parts — header, release sections, solution blocks, prefooter, footer, and icon set — so each issue could be assembled from governed building blocks.
WHAT TO NOTICE
The toolkit is the system.
The toolkit is the system.
The toolkit is the system.
The solution image shows how one monthly email was broken into governed parts: reusable headers, release sections, solution blocks, footer patterns, and shared icons. The value is not just the visual design — it is the repeatable assembly model.
The solution image shows how one monthly email was broken into governed parts: reusable headers, release sections, solution blocks, footer patterns, and shared icons. The value is not just the visual design — it is the repeatable assembly model.
This is where the campaign becomes a production system instead of a single template.
This is where the campaign becomes a production system instead of a single template.
Brand-consistent campaign patterns
The system translated Procore’s visual language into a scan-first email framework: disciplined type hierarchy, restrained accent usage, consistent CTAs, and repeatable module composition.
Brand-consistent campaign patterns
The system translated Procore’s visual language into a scan-first email framework: disciplined type hierarchy, restrained accent usage, consistent CTAs, and repeatable module composition.
Brand-consistent campaign patterns
The system translated Procore’s visual language into a scan-first email framework: disciplined type hierarchy, restrained accent usage, consistent CTAs, and repeatable module composition.
02 / System Behavior
Designing for real content, not ideal content
Designing for real content, not ideal content
Designing for real content, not ideal content
Responsive by design
Rather than shrinking desktop, I designed parallel compositions: desktop supports comparison and scanning across columns, while mobile stacks content into tap-friendly, readable sequences.
Responsive by design
Rather than shrinking desktop, I designed parallel compositions: desktop supports comparison and scanning across columns, while mobile stacks content into tap-friendly, readable sequences.
Responsive by design
Rather than shrinking desktop, I designed parallel compositions: desktop supports comparison and scanning across columns, while mobile stacks content into tap-friendly, readable sequences.
Rules for missing fields and truncation
Section title
Section title
The system accounted for imperfect inputs — missing copy, missing bullets, missing icons, and over-length content — so modules could collapse cleanly without awkward gaps or broken hierarchy.
Add a concise section description that explains the design decision, artifact, or outcome.
Add a concise section description that explains the design decision, artifact, or outcome.
The system accounted for imperfect inputs — missing copy, missing bullets, missing icons, and over-length content — so modules could collapse cleanly without awkward gaps or broken hierarchy.
Add a concise section description that explains the design decision, artifact, or outcome.
Add a concise section description that explains the design decision, artifact, or outcome.
The system accounted for imperfect inputs — missing copy, missing bullets, missing icons, and over-length content — so modules could collapse cleanly without awkward gaps or broken hierarchy.
Add a concise section description that explains the design decision, artifact, or outcome.
Add a concise section description that explains the design decision, artifact, or outcome.
The system accounted for imperfect inputs — missing copy, missing bullets, missing icons, and over-length content — so modules could collapse cleanly without awkward gaps or broken hierarchy.
Add a concise section description that explains the design decision, artifact, or outcome.
Add a concise section description that explains the design decision, artifact, or outcome.
The system accounted for imperfect inputs — missing copy, missing bullets, missing icons, and over-length content — so modules could collapse cleanly without awkward gaps or broken hierarchy.
Add a concise section description that explains the design decision, artifact, or outcome.
Add a concise section description that explains the design decision, artifact, or outcome.
WHY IT MATTERS
Edge cases protect the layout.
Edge cases protect the layout.
Edge cases protect the layout.
The missing-fields work shows how the template behaves when real campaign inputs are incomplete. By defining collapse rules, truncation points, and fallback behavior, the system stays intentional even when the content is not ideal.
The missing-fields work shows how the template behaves when real campaign inputs are incomplete. By defining collapse rules, truncation points, and fallback behavior, the system stays intentional even when the content is not ideal.
The goal was fewer one-off fixes during monthly production.
The goal was fewer one-off fixes during monthly production.
03 / Outcome
Making monthly production easier to govern
Making monthly production easier to govern
Making monthly production easier to govern
Monthly header library
Monthly header library
Monthly header library
Sixteen prebuilt header covers created a consistent cadence across 2025–2026, giving each issue a fresh entry point without redesigning the hero from scratch.
Sixteen prebuilt header covers created a consistent cadence across 2025–2026, giving each issue a fresh entry point without redesigning the hero from scratch.
Sixteen prebuilt header covers created a consistent cadence across 2025–2026, giving each issue a fresh entry point without redesigning the hero from scratch.
Example issue
Example issue
Example issue
A full desktop example shows how the release modules, hierarchy, CTA patterns, and footer assemble into a complete monthly send.
A full desktop example shows how the release modules, hierarchy, CTA patterns, and footer assemble into a complete monthly send.
A full desktop example shows how the release modules, hierarchy, CTA patterns, and footer assemble into a complete monthly send.
© 2025 Gilad Shahar