Explanation:

The design that the UX Designer at Cloud Kicks should use to make the website size and content adapt to the screen size, platform and orientation is responsive. Responsive web design is a web design approach that uses HTML and CSS to automatically resize, hide, shrink, or enlarge, a website, to make it look good on all devices (desktops, tablets, and phones) 1. Responsive web design is not a program or a JavaScript, but a set of best practices that include using media queries, flexible grids, fluid images, and breakpoints to create a layout that can respond to any device being used to view the content 2. Responsive web design is one of the learning objectives for the Salesforce User Experience Designer certification 3.

References: [Responsive Web Design Introduction], [Responsive design -Learn web development], [Salesforce Certified User Experience Designer Exam Guide]https://www.w3schools.com/html/html_responsive.asp
https://www.w3schools.com/Css/css_rwd_intro.asp

Explanation:

Compact display density is a global user interface setting that allows users to view more content on every screen by reducing the amount of space between page elements and aligning the field labels to the left of the fields. Compact display density is suitable for text information-rich Salesforce orgs, such as Cloud Kicks, that want to maximize the use of limited screen space on laptops. Compact display density can be set as the default for the org by the system admins, or chosen by individual users from their profile menu1.

Comfy display density is another global user interface setting that provides a spacious view with labels on the top of fields and more space between page elements. Comfy display density is suitable for orgs that want to emphasize readability and clarity, or that have more complex or interactive fields. Comfy display density is not the best option for Cloud Kicks, as it would reduce the amount of content that can be displayed on each screen1.

Enable collapsible sections is a feature that allows users to collapse or expand sections on a record page layout. Collapsible sections can help users focus on the most relevant information and reduce scrolling. However, collapsible sections are not a global user interface setting, but a page layout option that can be configured by the admins. Collapsible sections can be used in combination with either comfy or compact display density, but they do not affect the alignment of the field labels or the spacing between the page elements2.

References: 1: Personalize Lightning Experience Display 2: Collapsible Sections in Lightning Experience Record Pages

Explanation:

The Salesforce app allows administrators to customize the brand color and the loading page logo to match the company’s branding. The brand color affects the key user interface elements such as the header, buttons, and search bar. The loading page logo is the image that appears after a mobile user logs in. These elements can be customized from Setup by entering Salesforce Branding in the Quick Find box, then selecting Salesforce Branding. The other elements, such as the search bar layout, the background image, and the focus link color, are not customizable in the Salesforce app.

References:

Customize Salesforce Mobile App Branding
How Salesforce App Branding Works

Explanation:

According to the Web Content Accessibility Guidelines (WCAG), which are the leading international standards for accessible web design, perceivable content is content that can be presented to users in ways they can perceive. This means that the content should be available tothe senses (vision, touch, and hearing) either through the browser or through assistive technologies like screen readers, screen enlargers, and others1. Therefore, the content should only be visible is the correct answer, as it implies that the content can be seen by users who rely on vision to access the web. The other options are incorrect, as they suggest that the content is not perceivable to all users.

References:

Web Accessibility For Beginners | DigitalOcean, Perceivable: Content on the web should be perceivable.

Explanation:

User interface planning is an essential part of the Einstein Bot implementation process, as it involves designing the bot’s appearance, behavior, and interactions with the customers. User interface planning can affect the bot’s effectiveness and customer satisfaction, as it can influence the clarity, efficiency, consistency, and beauty of the bot’s experience. User interface planning includes1:

Choosing a bot avatar and name that match the brand and tone of the company
Configuring the bot greeting and fallback messages that set the expectations and boundaries of the bot’s capabilities
Designing the bot dialogues and menus that guide the customers through the conversation and provide relevant options and information
Testing and iterating the bot user interface based on user feedback and analytics References: Einstein Bots Project Planning | Salesforce Trailhead

Explanation:

Q Tabs are a type of SLDS component that can be used to organize and consolidate content on a record page. Q Tabs are a variant of the Tabs component that are designed for use in the Lightning App Builder. Q Tabs allow users to switch between different views of related information within the same context. Q Tabs can also be nested to create subtabs within a tab. Q Tabs can help UX designers to create content-rich record pages that are easy to navigate and consume. Q Tabs can also help to reduce clutter and scrolling on a record page by grouping related content into tabs. Q Tabs can be customized with different icons, labels, and badges to indicate the type and status of the content in each tab. Q Tabs can also be configured to load content dynamically or on demand, which can improve the performance and user experience of the record page.

References: Q Tabs Component Blueprint | Lightning Design System, Tabs Component Blueprint | Lightning Design System, Tabs | Lightning Web Components Developer Guide | Salesforce Developers

Explanation:

A Community Manager is a Salesforce persona who is responsible for creating, managing, and moderating online communities that connect customers, partners, and employees. They spend most of their time engaging with community members, enforcing community standards, and providing member support. A Community Manager aligns with the user who performs similar tasks in moderating forums.

References: : Salesforce Personas : Community Manager Roles and Responsibilities

Explanation:

The Path component is a Salesforce Lightning Design System (SLDS) component that can be used to represent stages for opportunities within the sales process. The Path component displays the stages as a horizontal bar with icons and labels, and highlights the current stage with a blue background. The Path component also allows users to move opportunities to different stages, view and edit key fields for each stage, and access guidance and tips for each stage. The Path component can be added to any object that has a picklist field with values that represent stages, such as the Stage field on the Opportunity object12.

References:

Path Component
Set Up a Path for Your Sales Team

Explanation:

Human-centered design is a practice where designers focus on people and their context, and seek to understand and solve the right problems for them. Human-centered design involves the following elements1:

Empathy. Designers need to genuinely care about the people they design for, and build empathy by immersing themselves in the community that will use their products or services. Creativity. Designers need to find creative ways to solve users’ problems, and generate multiple ideas and prototypes that can be tested and refined.

Business needs. Designers need to make their products or services commercially successful, and align them with the goals and values of the organization.

To incorporate human-centered design across its organization, Cloud Kicks should adopt the following two practices:

Observing user behavior. Designers should conduct user research and communicate with their users regularly, to understand their needs, motivations, challenges, and goals. Observing user behavior can help designers to identify the pain points and opportunities for improvement, and to validate their assumptions and hypotheses.

Putting oneself in the situation of the end user. Designers should empathize with their users, and try to see the world from their perspective. Putting oneself in the situation of the end user can help designers to create products or services that are relevant, useful, and desirable for them. The following two practices are not aligned with human-centered design, and should be avoided:

Including innovative ideas to showcase technology. Designers should not prioritize technology over people, and should not include features or functions that are not necessary or beneficial for the users. Including innovative ideas to showcase technology can lead to products or services that are complex, confusing, or frustrating for the users.

Creating requirements based on business leaders’ priorities. Designers should not ignore the voice of the users, and should not create products or services that only satisfy the business needs. Creating requirements based on business leaders’ priorities can lead to products or services that are irrelevant, useless, or undesirable for the users.

References: Human-Centered Design: An Introduction, Practices, and Principles - Shopify

Explanation:

The accessibility guideline of distinguishable means that the information and user interface components must be presented to users in ways that are perceptible. This includes using sufficient contrast between text and background colors, providing text alternatives for non-text content, and making it easier for users to see and hear content. When choosing a color for the text and the background of the buttons, the UX Designer should consider the contrast ratio between them, which should be at least 4.5:1 for normal text and 3:1 for large text. This will ensure that the buttons are visible and readable for users with different visual abilities.

References:

[1]: Web Content Accessibility Guidelines (WCAG) 2.1, Principle 1: Perceivable

[2]: Web Content Accessibility Guidelines (WCAG) 2.1, Success Criterion 1.4.3 Contrast

(Minimum)

Explanation:

An Empathy Map is a tool used in UX design to synthesize and articulate what a design team knows about a user group. It helps in creating a shared understanding of user needs within an organization. The key features of an Empathy Map include:

User Insights:It captures what users say, think, do, and feel, providing a holistic view of their experiences and perspectives. This helps in understanding users at a deeper level. Shared Understanding:By visualizing user attitudes and behaviors, an Empathy Map facilitates a common understanding among team members and stakeholders, ensuring that design decisions are aligned with user needs.

An Executive Summary (option A) provides a high-level overview of project objectives and outcomes but does not delve into user-centric insights. Prioritizing a Backlog (option C) is more about organizing and prioritizing tasks and features rather than synthesizing user research findings.

References:For guidelines on creating and using Empathy Maps, UX design resources such as the Nielsen Norman Group and the Interaction Design Foundation offer articles and guides on this andother UX research synthesis tools. These resources explain how to effectively use Empathy Maps to gain insights into user needs and foster empathy within design teams.

Explanation:

The best option to simplify working with SLDS in Lightning Components is to install SLDS Validator extension for VS Code. This extension (salesforcedx-vscode-slds) scans the markup of the components, validates it against the SLDS documentation, and provides suggestions onhow to improve the code1. It also offers syntax highlighting, code completion, and context awareness for SLDS tokens and utility classes1. By using this extension, the development team can avoid CSS conflicts, follow SLDS best practices, and create consistent and accessible components2.

Installing SLDS creator from AppExchange is not a valid option, as there is no such app available on the AppExchange. The AppExchange is a marketplace for Salesforce apps, components, and consulting services, not for VS Code extensions3.

Installing Lightning Design System Plugin for Sketch is also not a valid option, as it is not related to VS Code or Lightning Components. Sketch is a design tool that allows users to create wireframes, mockups, and prototypes4. The Lightning Design System Plugin for Sketch is a plugin that provides SLDS components, icons, and styles for Sketch users. It can help designers to create consistent and compatible designs, but it cannot help developers to work with SLDS in VS Code.

References:

SLDS Validator - Visual Studio Marketplace

SLDS Validator for VS Code - Lightning Design System

AppExchange: Salesforce’s Leading Enterprise Cloud Marketplace

Sketch — The digital design toolkit

[Lightning Design System Plugin for Sketch]