Here’s How a Former Overwatch Pro Made the Support Hero He Always Wanted


Overwatch’s Reign of Talon season 1 is starting to wind down, and the biggest story has been the five new heroes who joined the roster. A lot of attention has understandably gone to Jetpack Cat, a hero once scrapped in the game’s early design, but resurrected on the cusp of the game’s 10th anniversary. She’s been the subject of bans and memery due to her unique kit that features permanent flight and the ability to fly any other hero through the air with her Lifeline ability.

But another support hero has quietly gone under the radar as one of the most-played characters in the new season: Mizuki.

Mizuki is a complex hero, similar on paper to support heroes Brigitte and Lucio, who mix damage with healing in the radius around them, but with his own unique mechanics. He has a constant healing aura around him, which grows more powerful as he deals damage with his weapon or uses other healing abilities. His main weapon is a projectile that bounces off surfaces. One of his abilities, Katashiro Return, offers a burst of movement, but also the ability to teleport back to your starting point within a few seconds.

That all adds up to a hero design that gives players lots of options but also requires you to carefully strategize to turn the tide of battle. Do you stay with your team to maximize the value of your healing aura? Or do you split from them for a higher-risk, higher-reward play? Do you use your Katashiro Return ability to flank behind an enemy team, or save it to disengage from an unexpected attack?

In this clip, I used Mizuki’s Katashiro Return ability to take a risky flank with a guaranteed escape. Good thing, too, because I didn’t expect to meet a Junkrat in a small room.

Blizzard/Capture by Adam Benjamin/CNET

Despite spending most of my time in Overwatch playing support heroes, including Ana and Kiriko, I found Mizuki challenging early in the season, even as I watched enemy Mizukis pump out damage and secure clutch kills while constantly healing their teams. 

This “unlockable challenge” element was an intentional part of Mizuki’s design, as I was soon to learn from chatting with the hero’s creator, a former Overwatch eSports pro.

By and large, support players have embraced this challenge. An Overwatch spokesperson told me via email that “Mizuki is consistently in the top four for all support picks in Season 1, across every region.” He’s one of several elements powering a revival of the game, along with a new ongoing story, weekly faction missions and the promise of more new heroes every season. People have flocked back into the game since the start of Season 1, with its average player count on Steam more than doubling over the past month.

Mizuki’s design was led by Scott “Custa” Kennedy, a longtime presence in Overwatch’s professional scene as both a player and match analyst, and now an associate hero designer. I spoke with Scott at Blizzard’s spotlight event and also spoke with him and Mizuki’s character artist, Melissa Kelly, in early March to discuss how they created one of the game’s most popular heroes.

Screenshot of two Mizukis dueling in Paraiso

I fought many a Mizuki duel in season 1. I didn’t win them all, but I won this one.

Screenshot by Adam Benjamin/CNET

From professional player to associate designer

After a few years as a professional player and several more as an analyst and caster for the Overwatch League, Kennedy was looking for the next step in his career.

“Overwatch [had] been my life for, like, the last 10 years in many different facets,” he said, but as he reached retirement age in the esports realm, he wanted a change. He spoke with some of the Overwatch developers, including associate game director Alec Dawson, about what it would take to get into game development. 

After doing some QA work and hands-on game development (“I made the world’s hardest 2D cat platformer in three days,” he said), Kennedy secured an associate hero designer opening for Overwatch, which was a perfect fit with his experience. 

When given the task of envisioning the game’s next healer, Kennedy said he didn’t want to make another support designed around “point-and-shoot” mechanics that healed teammates and hurt enemies, like Ana or Juno. 

“I wanted [Mizuki] to be more of an AoE healing aura-type hero because I think that’s something that’s been underrepresented in our heroes,” Kennedy said. Instead, he came up with the area-of-effect healing that’s similar to how Lucio and Brigitte heal, but with the added layer of that healing becoming more powerful the better you play in combat.

Managing that nuance was a learning experience for Kennedy.

“One of the biggest things that I learned is how complexity can be really cool on paper, but when you’re making a hero how quickly that snowballs into making a player overwhelmed,” Kennedy said. But he feels the team ultimately found a good balance, where inexperienced players can still contribute with him, while more experienced and skilled players can benefit even more.

Concept art of Mizuki

Mizuki’s concept art adds a distinct edge to his design, but still distinguishes him as a support.

Blizzard

Kelly added that Mizuki was a complicated hero on the design side, too. 

“One of the issues is that he was looking kind of like a [damage hero],” she said. “He looked very aggressive for a healer. So we were just trying to soften him up.” Kelly pointed out that Mizuki’s weapon is a mix of a priest’s staff and a sickle, which also blurs the lines a bit between support and damage heroes. 

That nuance seems to be a big part of Mizuki’s appeal. Even though I generally prefer the kind of “point-and-shoot” healing hero Kennedy said he wanted to avoid, I’ve found Mizuki to be one of the most interesting additions to the roster, especially among support heroes. His Binding Chain ability, which roots an enemy hit by the chain into place, rewards good aim and timely use, while his Healing Kasa and Katashiro Return abilities let my brain ponder over creative escapes and ambushes. 

When I play Mizuki, I’m always thinking while I fight, and I enjoy feeling that kind of active engagement with the game. 

Here my Katashiro Return ability lets me flip the map against the enemy team and give allies the protection of my Kekkai Sanctuary ultimate. 

Blizzard/Capture by Adam Benjamin/CNET

Mizuki’s reception and prospects for pro play

Kennedy worried that players would be turned off by how complex the hero is — wondering, “Are players going to try him, not understand him and then be like… ‘I’m just gonna play the cat?'” (The cat, of course, is Jetpack Cat, who was released alongside Mizuki in season 1 and immediately became one of the most popular and most-banned heroes. She has a more intuitive, point-and-heal design, although her launch state also allows for particularly aggressive gameplay.)

Instead, Kennedy has enjoyed watching players stick with Mizuki and later post about how they’ve “unlocked” the hero by figuring out the formula to succeed with him. Kennedy said it’s rewarding to see players grasp his original concept for the hero as it plays out in-game. After that initial, somewhat disastrous first game I played, I started clicking with Mizuki, too.

Players still struggled with parts of Mizuki’s kit, and Kennedy noted some initial frustrations with “intentional design limitations” he and the team placed on the hero. Players seemed to want to use his Katashiro Return ability to go on aggressive flanks, but found it didn’t last long enough to successfully move behind enemy teams. That kind of larger repositioning would go against the design team’s vision for the hero, who is meant to stay near his team and use the ability to return to them quickly.

Now, Kennedy said, “players seem to understand the limitations of the hero, and that’s been cool to see.”

Concept art of Mizuki and his Spirit Glaive weapon

MIzuki’s Spirit Glaive is a unique weapon, especially among the support roster.

Blizzard

Mizuki has had a strong launch, and has been sitting around a 54% win rate in competitive modes since the start of the season. That’s quite high, ranking just behind last season’s top performer: the damage hero Vendetta. I asked Kennedy how he reads that data — whether Mizuki is overtuned or just a good fit among this season’s most-played heroes.

Kennedy said Mizuki was in a “pretty healthy” spot, but could get pulled down a bit in future seasons. “The numbers that he can put out in terms of healing and damage output are things that really put him above everyone else at this point. So it’s definitely something we’re keeping an eye on.”

But that power won’t necessarily translate to Mizuki being picked up in professional play, at least based on last month’s Overwatch Championship Series Bootcamp. Kennedy said the hero’s kit isn’t as good for staying alive and executing plays as heroes such as Lucio and Kiriko, who have long been must-picks in pro play. 

“I could see Mizuki getting more playtime in a world in which we start playing more rush metas [centered around tanks like Ramattra or Orisa],” he said, “but with how fast the game is being played at the highest level, it can be difficult for Mizuki to keep up.”

Kennedy brought up one of Overwatch’s biggest and most inevitable challenges over its decade-long tenure: balancing heroes for both the pro level and the rest of the game, and how the difficulty lies in the fact that certain resources — such as speed boosts, mobility and burst damage — are more valuable at the highest levels of coordinated play. The design team is always working to make sure heroes are never totally out of balance at either skill level, he said. 

That work has been on display since the launch of Season 1, with balance patches coming out virtually every week up through the midseason patch on March 10. Those updates mostly focused on the five new heroes but also included some changes to Vendetta, who continues to terrorize the game with a very strong win rate and the ability to cut someone down almost out of nowhere, leaving opponents very little time to react. 

Still, the season overall has been a win for the game, thanks largely to the influx of new heroes and the different playstyles they add to the game.

“[I’m] definitely a little overwhelmed with how positive everyone has been with Mizuki — and honestly, the five heroes in general,” Kennedy said. “I think the reception’s been awesome. We couldn’t have asked for anything better.”





Source link

Leave a Reply

Subscribe to Our Newsletter

Get our latest articles delivered straight to your inbox. No spam, we promise.

Recent Reviews


Salesforce Training

  • Master Your Craft
  • Lifetime LMS & Faculty Access
  • 24/7 online expert support
  • Real-world & Project Based Learning

Who can use the Salesforce Lightning Design System?

The Salesforce Lightning Design System gives you everything you need to develop user interfaces that follow Salesforce Lightning’s concepts, design style, and practice guidelines. Developers may concentrate on app logic instead of pixels, whereas developers could concentrate on customer experience, interfaces, and workflows. The website offers a variety of services for developers and designers, including:

  • Component markup that is both meaningful and accessible.
  • CSS that is cross-browser compatible.
  • Design guidelines, icons, and fonts

The three users are as follows:

Developers

  • Make sure you’re familiar with the ones that follow:
  • Have a quick rundown of the Markup and Style rules, along with the CSS class naming practices.
  • Examine the Components; for each offers semantically valid and readily available markup and documentation.

Take a look at the platform-specific setup instructions beneath.

Designers 
Begin with the following:

  • Learn about the Salesforce product development patterns and concepts by looking through the Guidelines.
  • Examine the Components section to become familiar with the current components that you can use in your projects.

Design Guidelines

The Lightning Design System is based on the Salesforce product’s designs and components. While creating applications and solutions inside the Salesforce ecosystem, such designs and elements could provide specific language and uniform appearance and experience.

Design Concepts:

When we make design choices at Salesforce, we always keep those key points into consideration, and also inspire you to do the same.

  • Clarity: Get rid of any ambiguity. Allow individuals to confidently perceive, comprehend, and act.
  • Efficiencies: Simplify and improve workflows. Predict requirements wisely to help individuals perform better, wiser, and quicker.
  • Employing the very same approach to a certain situation creates familiarity and strengthens instinct.
  • Beauty: By deliberate and exquisite craftsmanship, show respect for a person’s attention and time.

Lightning

In Lightning, begin using the Lightning Design System. Kindly give particular attention to the criteria for such Lightning technology you’re using:

  • Stand-alone Lightning app
  • Salesforce1 
  • Visualforce Lightning Components
  • Lightning Experience
  • Lightning Out component.

Want to gain knowledge in Design Patterns? Then visit here to learn Design Patterns Training!

What are the lightning components in Salesforce? 

There’s a great deal of discussion nowadays about Salesforce Lightning Components being used in Salesforce App solutions. Salesforce administrators use such components to build mono web apps that have an end-to-end encounter for just a variety of roles on the system. It’s important to keep in mind that:

  • Lightning components has end .cmp extensions.
  • Web components seem to be the foundation for Lightning components.
  • The Salesforce lightning application is installed with Apex, HTML,  JavaScript, and CSS.

Salesforce Lightning and Lightning Components were developed in response to the growing demand for mobile devices and fully responsive website development. There are three different types of Lightning Components you should know about. They are – 

 

Standard Lighting Components: 

These are pre-installed in the templates of the salesforce object pages. You could prefer to cover them or not use them, however, you can’t take advantage of them. It’s for this reason that they’re known as Standard Lighting Components. Each edition has been added to the list of Standard Lightning Components. The types accessible in Salesforce’s Lightning App Builder are determined by the Page Type and Object you choose. An App Page, for example, has the fewest Standard Lightning Components whereas a Record Page has the most. Certain Standard Components, like Tabs and linked Lists, serve as containers for many other Page Components.

Custom Developed Lighting Components: 

All of those are advanced lightning components that are created to meet the organization’s specific requirements. Custom Lightning Components can be developed by somebody with development expertise. This enables us to search and format information in Salesforce in new ways, draw information from external platforms for presentation, and develop custom functions in a system. Designers test and validate Components in a Sandbox or a Developer Org. When the Component is ready, a programmer elevates it to Production so it can be used in a Lightning Page.

AppExchange Lightning Components:

Most of the elements you’ll require may already be constructed and accessible on the AppExchange platform. All you have to do now is install them and then drag – and – drop them into the area where you wish to use them. Custom Managed Lightning Components can be created by Salesforce and its partners. These components are available for download and installation on Salesforce’s AppExchange. There are about 200 Components accessible on the AppExchange until this type, with 160 of them being free. Catalogs, grid layouts for Related Lists, or maps are common among some of the free ones. There are indeed several that give you access to third-party systems like Box, Vidyard,  DocuSign, TaskRay, and others. Whereas the paid listing of Lightning Components remains currently limited, it will keep growing as Lightning becomes more widely adopted. Here’s an example of a free component named USA Heatmap included in an account page.

 , Cloud Computings, salesforce-lightning-design-system-description-0, Cloud Computings, salesforce-lightning-design-system-description-0, , Cloud Computings, salesforce-lightning-design-system-description-0, AppExchange Lightning Components, Cloud Computings, salesforce-lightning-design-system-description-1, Cloud Computings, salesforce-lightning-design-system-description-1

Considerations for Components

Lightning Components have diverse attributes and could be rendered conditionally displayed on the page, which are two crucial concerns. Tap on an item in the Lightning App Builder to view its Data from an existing to the right. Filters can also be applied to control the component’s presentation related to data contents in the Record. As example, we could opt to reveal the Component solely to clients while hiding it from buyers and partners. To do the same, go to Set Component Visibility and select Add Filter. The Account Type element is then used to declare that the Component should only be visible to Customers.  Additional thing to keep in mind is that many Components could be placed in the same Lightning page template slot.

, Cloud Computings, salesforce-lightning-design-system-description-0, Cloud Computings, salesforce-lightning-design-system-description-0, , Cloud Computings, salesforce-lightning-design-system-description-0, AppExchange Lightning Components, Cloud Computings, salesforce-lightning-design-system-description-1, Cloud Computings, salesforce-lightning-design-system-description-1, , Cloud Computings, salesforce-lightning-design-system-description-0, AppExchange Lightning Components, Cloud Computings, salesforce-lightning-design-system-description-1, Considerations for Components, Cloud Computings, salesforce-lightning-design-system-description-2, Cloud Computings, salesforce-lightning-design-system-description-2

Click here to get frequently asked Salesforce interview questions & answers

, Cloud Computings, salesforce-lightning-design-system-description-0, Cloud Computings, salesforce-lightning-design-system-description-0, , Cloud Computings, salesforce-lightning-design-system-description-0, AppExchange Lightning Components, Cloud Computings, salesforce-lightning-design-system-description-1, Cloud Computings, salesforce-lightning-design-system-description-1, , Cloud Computings, salesforce-lightning-design-system-description-0, AppExchange Lightning Components, Cloud Computings, salesforce-lightning-design-system-description-1, Considerations for Components, Cloud Computings, salesforce-lightning-design-system-description-2, Cloud Computings, salesforce-lightning-design-system-description-2, , Cloud Computings, salesforce-lightning-design-system-description-0, AppExchange Lightning Components, Cloud Computings, salesforce-lightning-design-system-description-1, Considerations for Components, Cloud Computings, salesforce-lightning-design-system-description-2, , Cloud Computings, salesforce-lightning-design-system-description-3, Cloud Computings, salesforce-lightning-design-system-description-3

Subscribe to our YouTube channel to get new updates..!

Components 

Components seem to be the application’s self-contained, replaceable units. These are reusable pieces of the user interface that can be as small as a single line of text or as large as a full app. A collection of prebuilt components is incorporated within the framework. Inside an application, you could combine and adjust components to create new ones. Components are displayed in the browser to create HTML DOM elements. HTML, CSS, JavaScript, or other Web-enabled code could be included in a component. This allows you to create apps with advanced user interfaces. The specifics of a component are contained. This lets the component’s user to concentrate on developing their application, whereas the author of the component can experiment and implement modifications without disrupting users. The named properties that components reveal in their definition are used to configure them. Responding to or broadcasting events allows components to interact with their surroundings.

Lightning Component Framework

The Lightning Component framework’s functional units are called components. A component is a flexible and presumably reusable UI piece that can be as small as a single line of text or as large as an entire program. This is a Lightning Platform framework for creating single-page apps with a flexible, adaptable User Interface. 

Creating Components

  • In the Developer Console, build Lightning Components.

The Developer Console is a built-in tool that allows you to create new Lightning components and other packages as well as edit existing ones.

Component resources include a.cmp suffix and contain markup. The markup might include text or links to certain other components, as well as provide metadata for the component.

A component bundle is a collection of resources that includes a component or an application.

Component IDs  In JavaScript, you can obtain a component by using its local ID. A universal ID could be beneficial for debugging or distinguishing between several instances of a component.

The framework treats an HTML tag as a first-class component. Each HTML tag is converted into a component, giving the same liberties and facilities as other components.

CSS is used to style the components.

In Apex, component attributes are similar to member variables on a class. They are specified fields that are established on a particular example of a component and could be retrieved through the use of an expression syntax from inside component’s HTML. You can use attributes to create elements more flexible.

  • Composition of components

You may create highly intriguing components and apps by combining perfectly alright components in a bigger component.  Every component’s root-level tag is called the component body. 

Any Aura attribute is referred to as a facet.

  • Component[]. A facet is something like the body attribute.
  • Conditional Markup Best Practices

To conditionally show markup, use the tag. You can also use JavaScript logic to dynamically modify markup. While designing components, keep in mind the cost of functionality and also the manageability of the code. Your optimal design option is determined by your use case.

Component versioning allows you to express dependencies on certain revisions of a managed package that has been installed.

  • Putting Expressions to Work

Within component markup, phrases attempt to perform computations and retrieve property prices and other data. Use expressions to generate dynamic output or to send values to components via attributes.

The Label is a text which displays data about the user interface in places like the headers (1), input boxes (2), and buttons (3). (3). While you can define labels using text variables in components markup, you could also use the $Label worldwide value providers in expression syntax to obtain labels maintained beyond your code.

In input and output components, the framework supports client-side localization.

  •  Versioning of individual components

You can indicate dependencies on individual components by using component versioning. Documentation for your components aids others in comprehending and using them.

The Lightning Component framework is depicted in the diagram below. There are three parts to this:

  • Client-side: JavaScript is in charge of this.
  • Salesforce Cloud is used to link both the server and the client.
  • Apex Controller is in charge of this on the server-side.

, Cloud Computings, salesforce-lightning-design-system-description-0, Cloud Computings, salesforce-lightning-design-system-description-0, , Cloud Computings, salesforce-lightning-design-system-description-0, AppExchange Lightning Components, Cloud Computings, salesforce-lightning-design-system-description-1, Cloud Computings, salesforce-lightning-design-system-description-1, , Cloud Computings, salesforce-lightning-design-system-description-0, AppExchange Lightning Components, Cloud Computings, salesforce-lightning-design-system-description-1, Considerations for Components, Cloud Computings, salesforce-lightning-design-system-description-2, Cloud Computings, salesforce-lightning-design-system-description-2, , Cloud Computings, salesforce-lightning-design-system-description-0, AppExchange Lightning Components, Cloud Computings, salesforce-lightning-design-system-description-1, Considerations for Components, Cloud Computings, salesforce-lightning-design-system-description-2, , Cloud Computings, salesforce-lightning-design-system-description-3, Cloud Computings, salesforce-lightning-design-system-description-3, , Cloud Computings, salesforce-lightning-design-system-description-0, AppExchange Lightning Components, Cloud Computings, salesforce-lightning-design-system-description-1, Considerations for Components, Cloud Computings, salesforce-lightning-design-system-description-2, , Cloud Computings, salesforce-lightning-design-system-description-3, Lightning Component Framework, Cloud Computings, salesforce-lightning-design-system-description-4, Cloud Computings, salesforce-lightning-design-system-description-4

Salesforce Lightning Component is based on the Aura Component, which allows for the creation of dynamic web pages with just a scalable lifecycle to facilitate the development of growth-oriented apps. Aura Components are customizable UI parts represented by reusable components. Aura Components can be used in anything from a single statement to a full application. Aura Component is the foundation for Salesforce Lightning Component. Aura Component allows for the creation of dynamic web pages using a scalable lifetime to serve growth-oriented applications. The client and browser are linked through a multi-tier divided component in Aura Component. It features a responsive web design because it is built on the Aura framework. The lightning component in this way utilizes the very same code for all computers, mobile devices, and tablets, however, display based on the screen.

Lightning strikes quickly and will not replicate its sequence in real life; similarly, the Salesforce lightning design methodology is easy to use and isn’t using a similar model with different service customers. It allows you to deliver customer service, technical expertise, and varied instances all in one place.

Lightning Component Structure

In a word, Lightning Web Components have customized HTML objects created on the front end utilizing JavaScript, HTML, and CSS, with the potential to link to Apex as a console on the backend. The best part is that you can use both Lightning Web Components & Aura Components on a very similar page. The lighting component is adaptable, dynamic, and aids in focusing on the business visualization. Both the client and server sides of the lightning component employ separate technologies: the client-side uses JavaScript and the server-side uses Apex. When you start using the lightning component framework, you’ll discover that it will have a lot of benefits. 

  • The Salesforce Lightning framework makes it easier to create and develop apps. 
  • Many Salesforce users can access and use these components.
  • All browser technologies, including CSS, HTML5, and others, are enabled by the Lightning framework.
  • It allows for more engagement between users.
  • Data was exchanged between customer and server via JSON.
  • It has reusability, as well as adaptive and appealing designs.
  • It has an appealing user interface.
  • The framework aids in the development of various apps for mobile and desktop platforms.
  • It aids in the rapid performance of applications.

How to start building lighting components?

  • To make Salesforce Lightning Components, you’ll need to do the following:
  • Go to Developer Console after logging into the Salesforce developer account.
  • Then select File, then New, after that choose Lightning Component from the File menu.
  • Give the lightning component a name and a description that you like. and then press the Save button.
  • Configure the new component with component configurations. Inside the Component Configuration section, you could choose quite as many parameters as you want.
  • To develop the component, click Submit.

Where can you use Lightning Components?

Lightning is a CRM solution that responds to customer requests for a quicker, easier application development method and more efficient cycles in between business, IT, and client. Lightning components can be used to personalize your Salesforce organization in a variety of ways. It could be used to develop self-contained applications that are shared on Salesforce. You’ll gain a better understanding of Salesforce once you learn how to use Lightning Components. 

Why we should be using the Lightning Component Framework?

An out-of-the-box set of characteristics, event-driven design, and a performance-optimized framework are among the advantages.

The following are some reasons to use the Lightning component.

Comes with a pre-installed collection of components to get you started designing apps right away. You won’t have to waste time customizing your applications for various devices because the components will do it for you.

  • The ecology in use is made up of several different elements. Develop business-ready components for Lightning Experience, Salesforce1, and Communities and give them access. The navigation menu allows Salesforce1 consumers to connect your components. Drag-and-drop components on such a Lightning Page inside the Lightning App Builder or even use Community Builder to personalize the Lightning Experiences or Communities. The AppExchange has more elements for your organization. You could also share and distribute your components with certain other users.
  • Faster and more effective performance. Provides a domain-specific consumer and stateless server architecture to handle Ui metadata and app data on the consumer side, relying on JavaScript. The user only communicates with the server when it becomes absolutely essential, such as to obtain additional metadata or information. To enhance productivity and effectiveness, the server simply provides data that the user requires. The framework communicates information between both the client and the server using JSON. It uses the server, browsers, gadgets, and networking smartly so you can concentrate just on the structure and interactivity of your apps.
  • Architecture that is based on events. For improved dissociation between components, it employs an event-driven architecture. Every component that really can observe an application event or a component event could subscribe to it.
  • Design that is both responsive and reusable. Allows members to work more quickly with out-of-the-box parts working on both desktop and mobile platforms. Using components to build an app allows for parallel design, which enhances overall production efficiency. Components are wrapped, and its internal components are kept private, but its public form is available to component users. Such tight separation allows component authors to modify core details of the implementation while shielding component users from them.
  • Cross-benefits browsability’s, Apps are designed to be responsive and give a pleasant user experience. The Lightning Component framework is compatible with the most up-to-date browser technology, including  CSS3, HTML5, and tap events.
  • The user interface is stunning.
  • Visualization is compelled.
  • More user-interactive features.

Benefits of SLDS :

SLDS offers a variety of tools to construct applications that follow Lightning Experience’s concepts, design language, & methodologies. The following are some of the advantages that could create SLDS so beneficial:

  • By enhancing existing functionality or combining it with peripheral devices, it gives a seamless experience and simplified workflows.
  • Padding and margins are not over-enforced by default.
  • It is updated frequently. Till you’re utilizing the most recent edition of SLDS, the pages will be Lightning Experience compliant.
  • The CSS foundation contains accessibility.
  • It is compatible with various CSS frameworks, such as Bootstrap.

Using SLDS to Create Visualforce Pages

Visualforce pages which could mimic the appearance of the Salesforce application can be created with the Lightning Design System (SLDS). For using SLDS, you’ll need to make a few changes to the code and memorize a few points. Visualforce programming which employs SLDS, in the most portion, functions without a hitch.

In Visualforce, utilize SLDS Icons.

The actions, customized, doctype, basic, and utility logos are available in PNG and SVG (individual and sprite map) formats in the Lightning Design System (SLDS).

Using SLDS, construct a Visualforce page for the Salesforce Mobile App.

Now let us add a Visualforce page to the mobile navigation bar which shows your frequently accessed profiles and is designed using the Lightning Design System (SLDS).

SLDS for Responsive Page Design

Responsive design is indeed a website design technique that aims to create digital user interfaces that deliver the best visual experience possible, incorporating simple reading and navigation, on such a variety of devices.

Top 20 frequently asked Design Thinking Interview Questions !

Salesforce Training

Weekday / Weekend Batches

Conclusion:

Lightning Components are simple to generate, divide, and combine with some other parts, allowing you to make extremely customizable pages. Designers can expand lightning web components, encouraging different components to be created on top of existing ones, rather than constructing distinct components all across the app.  Salesforce’s lightning component architecture benefits from the usage of HTML, CSS, Java, and other internet techniques to provide a complex user experience. This article would be helpful in making you familiar with the Lightning components and their benefits to some extent.

Related articles :



Source link