2023
Inside Salesforce
Inside Salesforce
Inside Salesforce
Inside Salesforce had to publish evergreen resources, timely updates, and microsite-style sections in WordPress. I redesigned its information structure, navigation, and page templates, then documented the work for the developers, editors, and content owners who would maintain it.
Inside Salesforce had to publish evergreen resources, timely updates, and microsite-style sections in WordPress. I redesigned its information structure, navigation, and page templates, then documented the work for the developers, editors, and content owners who would maintain it.
Inside Salesforce had to publish evergreen resources, timely updates, and microsite-style sections in WordPress. I redesigned its information structure, navigation, and page templates, then documented the work for the developers, editors, and content owners who would maintain it.
Editorial Design
Information Architecture
WordPress Templates
Role
Led the information architecture, navigation, page templates, and usability testing.
Timeline
February–June 2023
Audience
Salesforce employees and the internal teams publishing the site.
Deliverables
Information architecture, WordPress page templates, reusable content blocks, style guide, and implementation notes.
What changed
What changed
Four microsites launched with the new publishing model for an internal audience of 70K+ employees. +30% average time on the landing page.
Four microsites launched with the new publishing model for an internal audience of 70K+ employees. +30% average time on the landing page.
+30%
Average time on the landing page
4
Microsites launched with the new model
70K+
Employees served by the internal hub
01 / Outcome
Four microsites launched from the same set of patterns
Four microsites launched from the same set of patterns
Four microsites launched from the same set of patterns
The new model gave the editorial team a shared set of page patterns for publishing stories and resources across four microsites. Those patterns became the starting point for dozens of pages. +30% average time on the landing page.
The new model gave the editorial team a shared set of page patterns for publishing stories and resources across four microsites. Those patterns became the starting point for dozens of pages. +30% average time on the landing page.
Before
Before
After
After
02 / What was happening
Editors needed one site to handle very different kinds of content
Editors needed one site to handle very different kinds of content
Editors needed one site to handle very different kinds of content
What needed to change
Inside Salesforce had to support evergreen resources, timely updates, and microsite-style sections in WordPress. Non-designers needed a clearer way to publish and maintain pages with consistent navigation and structure.
What needed to change
Inside Salesforce had to support evergreen resources, timely updates, and microsite-style sections in WordPress. Non-designers needed a clearer way to publish and maintain pages with consistent navigation and structure.
What needed to change
Inside Salesforce had to support evergreen resources, timely updates, and microsite-style sections in WordPress. Non-designers needed a clearer way to publish and maintain pages with consistent navigation and structure.
03 / What I reviewed
I looked for the decisions teams were making repeatedly
I looked for the decisions teams were making repeatedly
I looked for the decisions teams were making repeatedly
What the review showed
I combined working sessions with the people involved, an audit of the current site, and a review of comparable sites. The same problems kept appearing: employees lost context in navigation and categories; editors repeated layout decisions; and ownership and publishing rules were unclear.
What the review showed
I combined working sessions with the people involved, an audit of the current site, and a review of comparable sites. The same problems kept appearing: employees lost context in navigation and categories; editors repeated layout decisions; and ownership and publishing rules were unclear.
What the review showed
I combined working sessions with the people involved, an audit of the current site, and a review of comparable sites. The same problems kept appearing: employees lost context in navigation and categories; editors repeated layout decisions; and ownership and publishing rules were unclear.
FROM FINDINGS TO REQUIREMENTS
The audit became a practical design brief.
The audit became a practical design brief.
The audit became a practical design brief.
I grouped the findings into four areas the new model had to address: navigation, category structure, repeatable page patterns, and publishing ownership.
I grouped the findings into four areas the new model had to address: navigation, category structure, repeatable page patterns, and publishing ownership.
That shifted the brief from “redesign the site” to “make the publishing model clearer.”
That shifted the brief from “redesign the site” to “make the publishing model clearer.”
04 / What I changed
A smaller set of page patterns covered the common publishing needs
A smaller set of page patterns covered the common publishing needs
A smaller set of page patterns covered the common publishing needs
Reusable components in Figma
Reusable components in Figma
Reusable components in Figma
I turned the findings into patterns for the pages the team made most often: flexible introductions, story grids, and content modules. Editors had reliable starting points without forcing every page into the same layout.
Secondary navigation
Secondary navigation
Secondary navigation
I designed secondary navigation that kept employees oriented as they moved between the main Inside Salesforce site and its individual microsites.
05 / What testing changed
Testing challenged the proposed navigation model
Testing challenged the proposed navigation model
Testing challenged the proposed navigation model
Checking whether people could stay oriented
Checking whether people could stay oriented
Checking whether people could stay oriented
Usability testing asked whether participants could tell where they were and move between Inside Salesforce and the microsites. The results challenged the proposed model and informed the final direction.
Usability testing asked whether participants could tell where they were and move between Inside Salesforce and the microsites. The results challenged the proposed model and informed the final direction.
Usability testing asked whether participants could tell where they were and move between Inside Salesforce and the microsites. The results challenged the proposed model and informed the final direction.
06 / Handoff
The system had to work after the project team stepped away
The system had to work after the project team stepped away
The system had to work after the project team stepped away
Documentation for developers and editors
The final documentation connected Figma specifications, WordPress-ready components, visual guidance, and editorial rules. Developers could see how to build each pattern; editors and content owners could see when and how to use it.
Documentation for developers and editors
The final documentation connected Figma specifications, WordPress-ready components, visual guidance, and editorial rules. Developers could see how to build each pattern; editors and content owners could see when and how to use it.
Documentation for developers and editors
The final documentation connected Figma specifications, WordPress-ready components, visual guidance, and editorial rules. Developers could see how to build each pattern; editors and content owners could see when and how to use it.
WHY IT MATTERS
The handoff was part of the design.
The handoff was part of the design.
The handoff was part of the design.
A shared source of truth gave each group what it needed: specifications for developers, publishing rules for editors, and a clear record of the decisions for content owners.
A shared source of truth gave each group what it needed: specifications for developers, publishing rules for editors, and a clear record of the decisions for content owners.
The goal was for the site to keep working without depending on one designer.
The goal was for the site to keep working without depending on one designer.
Style guidance for future pages
Style guidance for future pages
Style guidance for future pages
The style guide covered typography, CTA states, filters, and small interface patterns so new pages could stay consistent without being redesigned from scratch.
The style guide covered typography, CTA states, filters, and small interface patterns so new pages could stay consistent without being redesigned from scratch.
The style guide covered typography, CTA states, filters, and small interface patterns so new pages could stay consistent without being redesigned from scratch.
Instructions for WordPress editors
Instructions for WordPress editors
Instructions for WordPress editors
A shared content-block spreadsheet translated the Figma work into practical instructions for WordPress editors and implementation partners.
A shared content-block spreadsheet translated the Figma work into practical instructions for WordPress editors and implementation partners.
A shared content-block spreadsheet translated the Figma work into practical instructions for WordPress editors and implementation partners.
WHAT I’D CARRY FORWARD
Reusable components only last when the rules and ownership are clear.
The components were only part of the work. The model became maintainable when navigation rules, editorial guidance, documentation, and ownership were defined alongside the page designs.
© 2026 Gilad Shahar