Product Page Template



synopsys new navigation

To look for solutions for updating AEM system to be more user-friendly.






Tool Used

Figma Microsoft Forms Microsoft Powerpoint

Period

2 month
05/03/2022 - 06/30/2022

Target Audience

Page Authors - Internal Users
Customers - Exteral Users

Participation

UX | Case Study
UI | Programming
Strategy | Presentation
Lead Workshop

Process



icon research

Study

Define Users
Survey & Interviews
Result

icon analysis

Analysis

Purpose
Pain Points & Solutions
Existing Product Page Study
Work Process

icon analysis

Design

Concept Proposal
Strategy & Components
Layouts & Fragments
Prototyping

icon analysis

Output

Components Guideline
Q/A

Study

Define Users

I set two different surveys for different target audiences.



user icon

Primary Users


Internal Users
Product Marketers (Page Authors)
Create and Update Product Pages
AEM System Users

user icon

Secondary Users


External Users
Synopsys Customers (Page Visitors)
Real Clients - Chip Industry Expert
Product Users - Engineers

Internal & External Users Surveys

Internal Users Survey

Basic Information About the Survey
22 Qestions
28 Participants
Date: 06/01/2022 - 06/10/2022

Synopsys AEM Page Author Survey

Internal Survey Result

Synopsys AEM Page Author Survey Result

Summary of the Survey

01.
Problem from Training

  • Outdated training assets
  • The component guideline is hard to find online
  • Didn't announce the new components regularly
  • Too much content in documentation
  • Don't know where to get support when studying the components

02.
Issue when using

  • Hard to find a suitable component to use
  • Not easy to restudy the unfamiliar components when trying to use it
  • Many page templates without a clear explanation
  • Forget checking each page elements before publishing
  • Don't know how to find support when having a question
  • Many free options on font size, color, spacing, and so on

External Users Survey

Basic Information About the Survey
14 Questions
10 Participants on survey
13 Participants on Interview Meeting
4 Groups
5 Hours Interviews Totally
Date: 06/01/2022 – 06/10/2022

Synopsys Customer Survey

External Survey Result

Synopsys Customer Survey Result

Summary of the Survey

Intervew Study based on Survey

Primary users: Verification Enginners
Secondary users: Software Developers, Validation Engineers, Design Engineers, Engineer Managers and do on

  • Not a strong marketing strategy
  • Not user-friendly layouts
  • Page structures are inconsistency
  • Lousy SEO, Less use of the keywords
  • Need testimonials to build the trust and relationship
  • Outdated updating with the new content
  • Very wordy
  • The contact function and search function are hard to use

Analysis

The pain points

purpose of redesign

Solutions

To Create a product template

01.
Align the page structures

Reason: Make the site the same branding and consistency. Be accessible for the users to scan the page with the focus.

02.
Pick components for each section to make pages consistent

Reason: UX team will work on the layout style and find the best practice for each section.

03.
Put the essential content types on each page for One Synopsys' marketing strategy

Reason: Use the same strategy on the product pages to align the marketing strategy.

04.
Create a demo page template for the page authors

Reason: Page authors can see the page visually and understand the thinking process of the strategy.

05.
Reduce the work process/time for the product team

Reason: Page authors only need to replace the placeholder content with actual content and delete the useless sections on the page.

06.
Use component fragments for some sections on the page

Reason: Update once and show on different pages to keep the easy updating. Never miss updates on every page.

dashboard before
Click to the page
dashboard before
Click to the page
dashboard before
Click to the page
dashboard before
Click to the page

Existing Product Page Study

Studied over 30+ product pages under 3 BUs. The studied pages included top product page, and product page tier 2, 3, 4 as sub-product pages.

Some examples below.

Product Page example
Product Page example
Product Page example
Product Page example

Click to see the detail

Work Process

Product Page template Survey Thumbnail Image

Step 1 Survey & Interviews

Understand the product team’s request (Persona/users Study Survey & Interviews).
Product Page template page study Thumbnail Image

Step 2 Study the current product pages

According to the current product page study, I get to know the types of sections that may need to include on the page template.
Product Page template demo page Thumbnail Image

Step 3 Create a product template

After I understand the users and the current page content strategy, I start to build the product template.

Design

Concept Proposal

There are several updates I will make on the design and workflow

01. Reduce the steps when the users create a new page

Multiple-template will not solve the problem for the users. They will confuse the users, especially the beginner. Suppose we know this page will be under the product list. In that case, We can only provide one product page template to avoid chaos because the other templates like generic company information, solution, and event templates will not work with the products page.

Suggest

02. Create a product template page with placeholder content

The users will have a basic thinking guideline about the marketing strategy with the existing page structure and layouts. They only need to think about the content, replace the placeholder content with the actual content and then delete the unused components/sections. This idea will benefit the page authors' work efficiency and be perfect for keeping the pages consistent.

Suggest

03. Link an icon for each component and link it to the component guideline page

It will be helpful for the users to learn how to use this component, either long-term or beginner users.

Suggest

04. Add a "How-to" demo video on each component guideline page

Instead of reading the documentation, the users like the video more. Video saves time and teaches how to build a section with the component from beginning to end.

Suggest

05. Add a check step before publishing the page

The users may forget to check the links, spellings, SEO, accessibility, image sizes, how it looks on different devices, and many details. I noticed those problems when I did testing with those pages. The step will remind the page authors to check the page details before publishing.

The first checklist UI proposal I made

Suggest

The scond option from Dev team - Siteimprove Plugin

Process of Building Product Page Template

This is the plan for the work process.

Strategy & Components

strategy icon

Strategy of content

  • Page Banner
  • Overview/Intro
  • Table of Content
  • SEO Breadcrumb
  • Challenges
  • News
  • Sub-products
  • Benefits
  • Contact Us
  • Feature
  • Promotion Ads
  • Related Products/Solutions
  • Additional Resources
  • Testimonial
  • Scroll Up
  • Social Media
  • Page Review Process Bar

component icon

Posible components list

  • banner
  • breadcrumb
  • Text & CTA
  • anchor
  • Richtexteditor
  • Column
  • image
  • contentcarousel
  • Cards
  • BoxLink Container
  • boxLink
  • Media Text CTA
  • floatingtabs
  • HTML

Layouts & Fragments

strategy icon

Layouts

  • Process Bar - HTML
  • Banner - banner
  • Table of Content - HTML
  • SEO Breadcrumb - breadcrumb
  • Overview/Intro - Text & CTA
  • Challenges - anchor, richtexteditor, Text & CTA, and column
  • Benefits - richtexteditor, Text & CTA, and column
  • News - anchor, richtexteditor, Text & CTA, contentcarousel, and cards
  • Sub-Products - anchor, richtexteditor, Text & CTA, boxLinkContainer, and boxLink
  • Promotion Ads - Media Text CTA, and HTML
  • Feature - anchor, richtexteditor, Text & CTA, and HTML
  • Related Products/Solutions - anchor, richtexteditor, Text & CTA, floatingtabs and HTML
  • Testimonal - Media Text CTA, and HTML
  • Quote - HTML
  • Additional Resources - anchor, richtexteditor, Text & CTA, Contentcarousel, and HTML
  • Contact Us - HTML , and Marketo embed form id
  • Scroll up - HTML
  • Social Media - HTML

component icon

Experience Fragments


If an author wants to re-use parts (a fragment of an experience) of a page, they need to copy and paste that fragment. Creating and maintaining these copy/paste experiences is time-consuming and prone to user errors. Experience Fragments eliminate the need for copy/paste.

  • Table of Content
  • News
  • Promoiton Ads
  • Testimonial
  • Additional Resources
  • Contact Us
  • Scroll up
  • Social Media

Prototyping

Page Template Editor Version

Synopsys product template page editor version

Page Template Published verson

Synopsys product template page published version

Product Page Template Demo Page

Table of Content & Progress Bar

Table of Content will help users jump to the target information, and the Process Bar will remind them how much content for the rest of the page.

Social Share

Social Share can scroll with the page. It helps the users jump to the contact us section and share the page link on social media.

Output

Components Guideline

There are several sections using HTML component(customer code). They need to convert to components for the page authors without a tech background.

Table of Content

TOC

Original UI


TOC

Hover & Active UI

TOC

Original Code

Rules for Table of Content

  • Explained
    • A table of contents, headed simply contents and abbreviated informally as TOC, is a list, usually found on a page before the start of a full-page, of its chapter or section titles or brief descriptions with their commencing page title.
  • UI
    • Background color: Synopsys dark purple(#5a2a82).
    • Font color: white & font size: 18px.
    • Left line color: synopsys light purple (#80539c)
    • Responsive Web & Big Tablet: 100% Width;
    • Small Tablet & mobile: overflow scroll horizontal.
    • Removing or adding text will not change the style.
    • Text links on TOC will separate the 100% width of the page on responsive web & big tablets.
    • Sticky to top navigation when page scrolls.
    • Hover and active effect - background color changes to synopsys light purple (#80539c).
    • The arrow function is to scroll the page up, and each TOC content will link to each section's tag anchor.
    • Arrow (Before using TOC function): Opacity(0.2) & Arrow (After using TOC function): Opacity(1).
  • Best Practice
    • Work with Anchor Component or anything code/section with a unique ID name.
    • Make sure the each text link on TOC match the anchor unique Id name.
  • Authoring Guide
    • Remove the text link on TOC if it is unnecessary.
    • Add the text link on TOC if necessary, and add the anchor component to match it.

Progress Bar

TOC

Process Bar In Process UI


TOC

Process Bar End UI

TOC

Original Code

Rules for Progress Bar

  • Explained
    • A progress bar is a graphical control element used to visualize the progression of an extended computer operation, such as a download, file transfer, installation, and read. Sometimes, the graphic is accompanied by a textual representation of the progress in a percent format.
  • UI
    • Before scrolling the page: The progress bar background color is white (The same as the top navigation background color).
    • During scrolling the page: The progress bar is Synopsys orange branding color (#e07c05).
    • Left line color: Synopsys light purple (#80539c)
    • Height: 5px; width:1170px;
    • Stick to the top navigation.
  • Best Practice
    • Work with long content pages.
    • Work with scroll-up function.
  • Authoring Guide
    • Build it on the page without any actions.

Floating Tab

Rules for Floating Tab

  • Explained
    • Floating Tab have commonly been used to create entire website layouts featuring multiple columns of information floated so they sit alongside one another (the default behavior would be for the columns/rows to sit below/next to one another in the same order as they appear in the source).
  • UI
    • Responsive Web: Font color(#111c24) & Opacity(0.5) & Font size(18px).
    • Responsive Web: The left side is a floating list & right side is the content/details.
    • Responsive Web (Hover & active effect): Font color changes to Synopsys dark purple(#5a2a82).
    • Tablet & Mobile: Font color(#111c24) & Font size(15px).
    • Tablet & Mobile: The top is a floating list & below is the content/details. Overflow scroll horizontal.
    • Tablet & Mobile (Hover & active effect): Background color(#5a2a82) & Font color(white).
  • Best Practice
    • Work with all components (right/below).
    • The limited number of the list (Max: 5-6).
    • The list title should use keywords (Better not too long).
    • Make sure the left and right side height almost equal (Responsive Web).
  • Authoring Guide
    • Add the text on the list.
    • Add the content on the content side.

Little Category

Rules for Little Category

  • Explained
    • Little Category is the style for showing the category with an icon, keywords title, and a summary. It uses on benefits, related products, related solutions, and other simple assets.
  • UI
    • Icon and title: Synopsys dark purple brand color (#5a2a82).
    • Paragraph: color(#111c24), line-height(1.4em) & font size (15px).
    • Hover effect: icon and title have a link. Title color changes to gold brand color (#fcaf1a).
  • Best Practice
    • Work with Column Component.
    • Limit 3 - 4 columns on the Column Component.
    • The title should be shorter than 34 characters
  • Authoring Guide
    • Add the Column component first and set the number of the columns.
    • Add the content on the content side.

Contact Us

This section works with Marketo. I added a customer CSS code on Marketo and a customer code with HTML component.

TOC

Responsive Web UI

TOC

Tablet UI

TOC

Marketo customer Code

TOC

Original AEM Code

Rules for Contact Us

  • Explained
    • Forms 2.0 empowers Marketers to create beautiful, stable, and flexible web forms without programming knowledge. Forms can reside on Marketo landing pages and also be embedded on any page of your website. The core functionality of a Marketo web form can be extended using Forms 2.0 JavaScript API.
  • UI
    • Background image with overlay linear-gradient.
    • Font Size, Color, CTA hover effect and so on style follow the Synopsys web branding.
    • Responsive web: Left side (5/12) is content including Title and Subtitle. Text is left align.
    • Responsive web: Right Side (7/12) is content including two columns Marketo Form. Form and CTA are left align.
    • Tablet: Top content text is center.
    • Tablet: Below Marketo Form is two columns center. CTA is center.
    • Mobile: Top content text is center the same as Tablet.
    • Tablet: Below Marketo Form is one column center. CTA is center.
  • Best Practice
    • Use the same Marketo Customer code on each Marketo.
    • Use the same AEM code but replace the Marketo form id each time.
    • Use an additional HTML component to add a background image.
  • Authoring Guide
    • Work with Marketo Team to create a marketo form case by case.
    • Replace the placeholder Marketo id with the new Marketo form id number.

Social Share

TOC

Original UI

TOC

Original Code

Rules for Social Share

  • Explained
    • The social sharing is known as social media users broadcasting web content on multiple social platforms to their connections, groups, or specific individuals.
  • UI
    • It is located on the middle left edge of the page.
    • Social Media: Twitter(#3AAFD6), Linkedin(#0e76a8), Facebook(#3b5999), YouTube(#BD081C), Contact Us(#80539c) and Close/Open(#fcaf1a).
    • Social Media before hover: box with background color(45px x 45px), color(white), font size(15px), text align(center) and line height(45px)
    • Social Media first box hover: box width(60px) and border radius(0 5px 0 0).
    • Social Media last box hover: box width(60px) and border radius(0 0 5px 0).
    • Social Media between boxes hover: box width(60px) and border radius(0 20px 20px 0).
    • Social Media Open(after close): box (45px x 45px) and border radius(0 30px 30px 0).
    • Social Media Open(after close) hover: box width(60px) and border radius(0 30px 30px 0).
    • Social Media Open(after close) - Mobile: box width(60px), border radius(0 30px 30px 0), Opacity(0.25).
  • Best Practice
    • The function can be used on any pages.
    • Highly Recommendation: Add it to Product Pages, Glossary Pages, Event Pages, and Campaign Pages.
  • Authoring Guide
    • Before converting to a component, the shared link needs to add to each social media icon.

Back To Top

TOC

Responsive Web & Tablet UI

TOC

Mobile UI

Rules for Back To Top

  • Explained
    • Back to Top links help users navigate to the top of long pages. Other techniques may be more appropriate on some sites depending on users' needs.
  • UI
    • It is located at the bottom of the page and the right space is 50px to the page edge.
    • Button background color(#fcaf1a), icon color(black) & border radius(7px 7px 0 0).
    • Hover effect: Cursor(pointer)
    • Responsive Web & Tablet: Opacity(1)
    • Mobile: Opacity(0.25) & the right space is 15px to the page edge.
    • Mobile hover: Opacity(1)
  • Best Practice
    • The function can be used on all the pages, especially the long content pages.
  • Authoring Guide
    • Use it directly after convert to a component.

Q/A

The product template page has been published for Q/A with Page Authors and the entire marketing team.
It only can be checked by the internal employees with a VPN connection.

Download the Full Case study Report

Summary

This project lasted about two months. I took the ownership and leadership on this project while working with the marketing team, the engineering team, and another UX designer. I read the survey carefully and brought many questions based on their surveys during the interview meetings. I quickly figured out the problem from their feedback and started looking for solutions. Talking to the users is the best and quickest way to understand their pain points.

Here is what I learned:

Hearing what the users say about the product and the feedback is very useful.
Bring the solutions and follow up to present the key in and out of the team.
Think about multiple situations when creating a component.
Propose the solutions to experienced persons first and hear their thoughts before working on them.