topic Re: Traverse Widget 1.0 in Experience Builder Custom Widgets

Traverse Widget 1.0

polkor_mcavoye — Thu, 04 Jun 2026 21:45:23 GMT

Hi there everyone!

We've been working on a traverse widget for a couple of weeks now and figured since it is functional we can now add it to the EXB community. @ncramer11 and I have developed this with some help from ClaudeCode, and we're still in the process of updating it. Big thanks to @TomSellsted for helping us build the original Web AppBuilder widget.

Features still to come:

Cardinal direction simplified entry

course specific units

popup suppression

Re: Traverse Widget 1.0

adamsimple — Thu, 04 Jun 2026 21:30:25 GMT

Looking forward to it!

Re: Traverse Widget 1.0

polkor_mcavoye — Thu, 04 Jun 2026 21:46:16 GMT

its up! Sorry the zip upload got stuck in our firewall!

Re: Traverse Widget 1.0

SunshineLuke90 — Thu, 04 Jun 2026 22:25:43 GMT

@polkor_mcavoye, would you be open to me making some modifications, purely to the UI? I've gotten really good at using the Calcite design system, and would love to take a crack at rebuilding the UI of this widget using Calcite Components, which already come pre-installed with Experience Builder, and will make it so that your widget will conform to the Experience Builder style settings within the theme tab.

Is your widget available on Github, or another version control platform? If so, I can make a pull request to your repository.

Re: Traverse Widget 1.0

SunshineLuke90 — Sat, 06 Jun 2026 18:33:03 GMT

I went ahead and rebuilt the widget with Calcite components, and converted the widget to a functional component, rather than a class component since functional components are the more modern way of doing things. Either way would work just fine, and if you go back in the commit history, I made all of the UI changes before changing to a functional component, so you can still snag the class component version, with all of the UI upgrades.

I highly recommend sharing your widget using the standardization guidelines that I outline in this community post. Especially important is providing a license, as without one, it's difficult for organizations to really use your code in a serious manner. If you use GitHub, or another version control platform, that's even better, since you'll be able to accept suggestions from the community, and collaborate on the same project without juggling a bunch of different zip files.