Because I was stuck trying to get JS integrated into the other component I was working on, I decided to try one that did not use any JS code.
I have successfully created a full-blown Back to Top button component that allows complete control of all the critical aspects of this type of component.
Here is what it looks like.
And here are some of the settings.
I built this as a DevPack so I could learn more about the process, and even did icons for it. Although @dan is probably not going to like my coloring of the icon, as it is a lot brighter than the ones used in Elements. I made a conscious choice to use this coloring because I’m a visual person, so I remember things through the iconography. I find the Elements component icons almost impossible to recognize in dark mode, where I’m forced to rely on the title to identify a component. So I wanted icons that would help me identify the element without having to read the title text. This works for me and makes it easier for me to identify my components among the core ones.
This was a very satisfying endeavour and once again reinforced just how great Elements is as a web development platform. If you don’t have something you need, just create it. Working on a DevPack was an incredible experience due to the tight integration between the code you are editing and the visual aspects. Edit a property in the code, and the change appears in the editor the moment you save it. Amazing!
I now consider myself an official expert in assembling component properties. I have spent a lot of time going back and forth between the documents and my properties. Fun learning experience.
The only takeaway that I have from this experience is that it would be extremely helpful if the RW team could provide a complete list of all the property icons they use from SF Symbols. It was excruciatingly painful looking through all those icons, trying to identify the ones that corresponded to those used by Elements. And no search was useless for this task. I was trying hard to match my icons to those used by Elements, so it would be easier for someone to recognize what the settings were used for.
Everyone should try this at least once to gain a better appreciation for just what the Elements team has built. I think there is a lack of understanding of just how powerful this piece of software is and how far it has come in the last year.
It has certainly inspired me to dust off my programming skills and start creating things for myself.
It’s truly a thrill to hear about people using the Elements API and finding it a joy to work with!