I have some requirement to build vertical menu in user digital experience page.
I've followed https://trailhead.salesforce.com/content/learn/projects/communities_theme_layout/nav_menu
to build complete custom layout to nail that. That's ok, it works. Our client wants also certain icons for each menu entry. So right now it is as follows:
<aura:iteration items="{!v.menuItems"} var="item">
...
<aura:renderIf isTrue="{!item.label == 'Name'}">
<lightning:icon iconName="utility:groups"/>
</aura:renderIf>
And I find it not appropriate for further development. I know this is narrow topic of Salesforce and not so many of devs have ever encountered such task but maybe someone has...
What's the better viable solution?
Related
Apologies if I don't explain this well, but I've seen something like this on certain websites (unfortunately can't think of an example right now).
Sometimes if I visit a website for the first time, the site will guide me through the entire document and highlight certain sections e.g., "Use this button here to add a new item" while the rest of the page is greyed out, and then you click Next step which takes you to the next feature, and so on.
It'll be somewhat similar to this (but styled nicer) :
Is there a way (or package) to do this with React?
I believe this feature is called Product Tours
This library can help you - https://github.com/gilbarbara/react-joyride
Also, I found an article using this library on Smashing Magazine - https://www.smashingmagazine.com/2020/08/guide-product-tours-react-apps/
We have some buttons on our contact page that via javascript update a handful of hidden fields on the object. We are moving to the lightning UI and I understand these are not supported, but am struggling to decipher the documentation on the best replacement. Can someone help point me in the right direction.
Requirement is to update several fields on the contact that is currently on the screen... nothing more, other than we don't use chatter so nothing with the feed please.
The Winter 17 release included the ability to create Actions based on Lightning Components. This is most likely the way you will want to go to convert your existing JavaScript buttons. I would suggest you check out this new Trailhead that was just released which is specifically about Lightning Alternatives to JavaScript buttons.
I am also working on a course for Pluralsight about Lightning development and this is one of the areas I plan on covering since it is so applicable to a lot of people right now. I am not sure if you realize this but by next year, any JavaScript buttons you have will no longer work (even in classic). It is part of a 3 phased approach that Salesforce is implementing to phase them out for security reasons.
Good luck in your conversion. I wish I could say it will be easy, but at least now it is possible.
Best.
Sara
Looking for advice on this - please give your opinion on which is best and the pros and cons.
I've got a site I'm working on that will be catering to basically three types of devices. Desktop/Laptop, Tablet, Phone. It is a responsive site so it looks great on all three.
BUT!
For the tablet and the phone there are a couple of features we will be including that will not be available for Desktop. There are links that will be included just for these and there will be a whole new menu that will sit snugly along the bottom of the site.
AND!
For the phone there will be even more features that will be in that bottom menu (like a "phone" icon to quick call from any page - not on the tablet).
We've got a WURFL setup telling us the device capabilities (is_smartphone, is_tablet, neither) - just want to know what you think is the best way to implement this?
a) set theme based on capability?
b) show/hide certain menus in the CSS based on capability?
c) something else?
Since you are using server side detection you can deliver specific sets of css and html depending on what type of hardware is creating the httpd request. The benefit of this over using media queries is you are able to decrease load times. The issue of doing display none is they are still getting loaded and not displayed. I would recommend to use the RESS technique.
I'm a Ui/Ux designer, and I've been asked to give some advice on the architecture of an iPhone app, the said app implies a section called 'Help and guides' for the users to know how to properly enter their data in the app. While analyzing the app, I was going to recommand that it may be interesting to put that part in the settings, and I was challenged about the reason I would do that. All I could come up with was that it was kind of a habit to put it there. But indeed, why would we put the help in the settings?
While doing some research, it appears that the help and the FAQs are often placed in the settings of the apps, and I was wondering why. Even though it seems obvisous to me that this has evolve into a known pattern to the user, I was wondering if there was a proper justification for this practice. Any ideas or clues?
From my research into this as I am currently designing Android and IOS Apps. The reason to group both these items under the one menu is to keep the screen as clutter less as possible. Due to the screen size of a mobile phone, the need for space is high so removing the buttons by grouping them under the one menu helps greatly.
I would suggest possibly making a Menu button with the options to access help & settings as subheadings personally.
I want to know how to design a website. The website is shown normal on the web and mobile, but I need to know which one is better?
Design two different templates (one template for mobile and the other one for a normal monitor).
Check online through the user's device to see if its using a mobile device so I can change the stylesheet.
Is this correct? If there are any ideas, please tell me.
Thanks
I would go for 1. Normally you don't want to show as much content on your mobile website as your "normal" desktop website. But include a link to your normal website from your mobile website.
I would go for one, as axelios suggested, I would include a link.
I, as a user, find extremely annoying websites that refuse to display the full site because they "recognised my browser as a mobile browser". Several newssites do that, which has eventually diminished the number of news I read, and some shops did so, which means I don't visit their sites anymore... so I strongly discourage the second solution.