Skip to main content

I'm a Salesforce consultant. Every project I've worked on started the same way: a Figma or grey-box wireframe that the client signs off, then a build that surprises them, because a picture of a Lightning page is not a Lightning page. Hover cards, path chevrons, related lists, the way a quick action opens: none of it is in the mock-up, and the review meeting turns into "is this what Salesforce looks like?" instead of "is this the requirement?". 

 

What I've been doing instead is building the page itself in the real Lightning Design System from the user story, in both the SLDS 1 and SLDS 2 looks, then clicking through it with the client and reading the acceptance criteria back off the page. It has changed our review meetings, but I'd like to know what others in this group use: 

 

Do you prototype in the SLDS Figma kit, or straight in App Builder in a sandbox? 

How do you show interaction (quick actions, screen flows, popups) without building it for real? 

How do you handle the SLDS 2 transition when the client's org still shows the classic look? 

Full disclosure: I built the tool I use for this (

sfproto.com, free to try, nothing connects to an org). That's not the point of the question, but I'd rather say so than not.

답변 5개
  1. 9월 30일 오후 4:00

    I'm a pretty big fan of simply defining a beta app inside the production org and creating a lightning record or app page, preferably by copying the existing page as foundation. Add that record page as the Default page in the new beta app. Now make whatever changes you plan to make. If it's a big production change that will take a lot of work, place a rich text element describing what you're going to do in Mockup.  If you're going to design a custom component, add a component very similar to what you plan to do, use it but add rich text above it explaining the difference. If you plan to add custom buttons, you can mock those up with a rich text element also or even other things more button like. Now you can show the page to whomever needs to give feedback.

     

    I actually roll out new pages this way. I developed the fully functional page inside the beta app and tell people there's a better way if they want to give it a try by switching to the beta app and then when everything stable, we just change the the default page (org wide if applicable) over to the new page and it's done. 

     

    Another nice thing for users is to have a little rich tech somewhere down at the bottom or your production pages that actually list the revisions made to the page. You can include hints, too, since change is usually aimed at better effeiciency or process. 

0/9000