SALESFORCE · WEB & EDITORIAL SYSTEM

Inside Salesforce

Inside Salesforce

Inside Salesforce

One web system had to support news, evergreen resources, and four distinct microsites. I redesigned the information architecture, responsive navigation, and reusable WordPress templates—giving editors a clearer publishing model and 70K+ employees a more consistent way to find stories and resources.

One web system had to support news, evergreen resources, and four distinct microsites. I redesigned the information architecture, responsive navigation, and reusable WordPress templates—giving editors a clearer publishing model and 70K+ employees a more consistent way to find stories and resources.

One web system had to support news, evergreen resources, and four distinct microsites. I redesigned the information architecture, responsive navigation, and reusable WordPress templates—giving editors a clearer publishing model and 70K+ employees a more consistent way to find stories and resources.

Web Design

Responsive Systems

CMS Templates

Inside Salesforce internal content hub shown across desktop and mobile.

Role

Led information architecture, responsive navigation, page-template design, usability testing, and implementation review—from Figma through WordPress.

Collaborators

Developers, editors, and content owners

Audience

70K+ Salesforce employees, plus the editors and content owners publishing the site.

Deliverables

Responsive page templates, navigation patterns, reusable content modules, publishing guidance, and developer-ready specifications.

What changed

What changed

Four microsites launched from one publishing model. The system became the starting point for dozens of pages and average landing-page engagement time increased by 30%.

Four microsites launched from one publishing model. The system became the starting point for dozens of pages and average landing-page engagement time increased by 30%.

+30%

Average time on the landing page

4

Microsites launched with the new model

70K+

Employees served by the internal hub

01 / IMPACT

Four microsites, one recognizable system

Four microsites, one recognizable system

Four microsites, one recognizable system

The editorial team used the same navigation, layout, and content patterns across four microsites and dozens of pages. Employees encountered a more consistent experience, while editors gained clearer starting points for new stories and resources.

The editorial team used the same navigation, layout, and content patterns across four microsites and dozens of pages. Employees encountered a more consistent experience, while editors gained clearer starting points for new stories and resources.

Before

Before

Reusable page and component patterns for Inside Salesforce.

After

After

Inside Salesforce interface exploration and template documentation.

02 / THE BRIEF

One site had to support news, resources, and four different microsites

One site had to support news, resources, and four different microsites

One site had to support news, resources, and four different microsites

Three groups needed the system to work

Employees needed to find information without losing context. Editors needed flexible templates they could use without a designer. Developers and content owners needed clear specifications, behaviors, and publishing rules.

Three groups needed the system to work

Employees needed to find information without losing context. Editors needed flexible templates they could use without a designer. Developers and content owners needed clear specifications, behaviors, and publishing rules.

Three groups needed the system to work

Employees needed to find information without losing context. Editors needed flexible templates they could use without a designer. Developers and content owners needed clear specifications, behaviors, and publishing rules.

03 / THE DESIGN BRIEF

The audit revealed a publishing problem—not only a page-design problem

The audit revealed a publishing problem—not only a page-design problem

The audit revealed a publishing problem—not only a page-design problem

The same decisions were being remade on every page

Working sessions, a site audit, and a review of comparable platforms showed recurring issues: navigation changed between sections, editors rebuilt common layouts, and ownership rules were unclear. I turned those findings into requirements for navigation, page patterns, responsive behavior, and governance.

The same decisions were being remade on every page

Working sessions, a site audit, and a review of comparable platforms showed recurring issues: navigation changed between sections, editors rebuilt common layouts, and ownership rules were unclear. I turned those findings into requirements for navigation, page patterns, responsive behavior, and governance.

The same decisions were being remade on every page

Working sessions, a site audit, and a review of comparable platforms showed recurring issues: navigation changed between sections, editors rebuilt common layouts, and ownership rules were unclear. I turned those findings into requirements for navigation, page patterns, responsive behavior, and governance.

FROM FINDINGS TO DIRECTION

Make the publishing model clearer.

Make the publishing model clearer.

Make the publishing model clearer.

The system needed to preserve a recognizable Salesforce experience while giving each microsite enough flexibility for its own stories and resources.

The system needed to preserve a recognizable Salesforce experience while giving each microsite enough flexibility for its own stories and resources.

That became the design principle: shared brand and structural anchors, with controlled variation at the page and content level.

That became the design principle: shared brand and structural anchors, with controlled variation at the page and content level.

04 / THE WEB SYSTEM

A smaller set of branded patterns covered the common publishing needs

A smaller set of branded patterns covered the common publishing needs

A smaller set of branded patterns covered the common publishing needs

Brand and page patterns in Figma

Brand and page patterns in Figma

Brand and page patterns in Figma

I translated the direction into reusable introductions, story grids, navigation states, CTA treatments, and content modules. Typography, spacing, color, and interaction rules stayed consistent while editors could choose the structure that best fit each story.

Responsive navigation that kept people oriented

Responsive navigation that kept people oriented

Responsive navigation that kept people oriented

The navigation preserved the relationship between the main Inside Salesforce hub and each microsite, while adapting the hierarchy for smaller screens.

Animated secondary navigation showing context preserved between Salesforce microsites.

05 / VALIDATION

Testing challenged the first navigation model

Testing challenged the first navigation model

Testing challenged the first navigation model

Could people tell where they were—and where to go next?

Could people tell where they were—and where to go next?

Could people tell where they were—and where to go next?

Usability testing focused on orientation between the main hub and individual microsites. The first proposal looked organized, but participants lost context. I revised the active states, labels, and hierarchy, then documented the final behavior for implementation.

Usability testing focused on orientation between the main hub and individual microsites. The first proposal looked organized, but participants lost context. I revised the active states, labels, and hierarchy, then documented the final behavior for implementation.

Usability testing focused on orientation between the main hub and individual microsites. The first proposal looked organized, but participants lost context. I revised the active states, labels, and hierarchy, then documented the final behavior for implementation.

06 / FROM FIGMA TO WORDPRESS

The handoff connected design, development, and editorial work

The handoff connected design, development, and editorial work

The handoff connected design, development, and editorial work

One source of truth for three kinds of decisions

The documentation connected Figma specifications, WordPress components, brand guidance, and editorial rules. Developers could see how each pattern behaved; editors knew when to use it; content owners had a record of the decisions behind the system.

One source of truth for three kinds of decisions

The documentation connected Figma specifications, WordPress components, brand guidance, and editorial rules. Developers could see how each pattern behaved; editors knew when to use it; content owners had a record of the decisions behind the system.

One source of truth for three kinds of decisions

The documentation connected Figma specifications, WordPress components, brand guidance, and editorial rules. Developers could see how each pattern behaved; editors knew when to use it; content owners had a record of the decisions behind the system.

WHY IT MATTERS

The system had to work without the project team.

The system had to work without the project team.

The system had to work without the project team.

A reusable web system is more than a component library. It needs clear rules for implementation, publishing, and ownership.

A reusable web system is more than a component library. It needs clear rules for implementation, publishing, and ownership.

The goal was consistency without making every page look identical—or requiring a designer for every update.

The goal was consistency without making every page look identical—or requiring a designer for every update.

Brand guidance for future pages

Brand guidance for future pages

Brand guidance for future pages

The guide covered typography, CTA states, filters, navigation, and interface details so new pages could feel recognizably Inside Salesforce.

The guide covered typography, CTA states, filters, navigation, and interface details so new pages could feel recognizably Inside Salesforce.

The guide covered typography, CTA states, filters, navigation, and interface details so new pages could feel recognizably Inside Salesforce.

Instructions for WordPress editors

Instructions for WordPress editors

Instructions for WordPress editors

A shared content-block reference translated the Figma system into practical publishing guidance for editors and implementation partners.

A shared content-block reference translated the Figma system into practical publishing guidance for editors and implementation partners.

A shared content-block reference translated the Figma system into practical publishing guidance for editors and implementation partners.

OUTCOME

A clearer employee experience and a repeatable way to publish

Four microsites launched from the same model, serving 70K+ employees and increasing average landing-page engagement time by 30%. The lasting result was a system that connected brand, interface, content, and implementation—not just a set of templates.

gilad.ux@gmail.com

© 2026 Gilad Shahar