We've launched a beta version of the Developer Center's UI at https://developer-beta.genesys.cloud/! We're inviting the community to check it out and participate in a bug hunt before the main site is cut over to the new architecture.
Please use the feedback/bug report form at the bottom of each page if you find anything out of place.
Note: The dev forum is not included in this beta and the /forum/ route will not work on the beta URL. Please continue to use the dev forum via the main site's URL.
Change Category
Infrastructure, Informational
Change Context
The beta site has the same content, look, and feel as the existing Developer Center, but it's running on a new backend architecture. This new architecture will allow faster and more frequent content updates as well as providing the backbone for several upcoming new Developer Center features. Keep an eye out for announcements about those features in the coming months!
After the bug hunt is complete, the main site will be cut over to the new infrastructure and the beta site will be taken down. Please continue to use https://developer.genesys.cloud/ for all bookmarks and saved links as the beta site's URL will not be redirected when it is taken down. This announcement will be updated when that happens.
I would report this on the page itself, but due to the nature of the issue, I can't. When I navigate to Genesys Cloud Developer Center, the page enters a refresh loop. I have tested this in other browsers (Chrome and Edge) as well as incognito.
Does this architecture change provide performance improvement to API Explorer? Sometimes I find that it locks the page up while loading, if a response is beyond a certain size.
That specific performance issue is a client-side concern. The new and old UI apps are the same code in that case. The cause of that performance issue is the syntax highlighter on the API response payload. The tipping point of when that performance becomes a problem is highly dependent on your computer's specs. There is a limit in place that disables the syntax highlighter above a certain payload size, but we can consider lowering it if this is a common issue for you.
Would you mind creating a new post with some details so we can take a look? I'd like to know more about your OS, browser, hardware specs, and what the size of the response payload is when you have the issue (the browser's network console will show you this).
I'm not sure what you're referring to. Could you share a screenshot showing where you're seeing a "paper clip thingy"?
Have you tried moving your mouse cursor off of the menu to allow it to collapse? As long as your mouse is hovering over the menu it will stay open so you can use it. That behavior is unchanged from the old site. Please reply back with further details if that's not the behavior you're reporting.
Yes, if you move off, it does collapse which is very different behavior to all other UI. I always assume if I click something, I shouldn't have to do something else. As you can see, when you click the middle panel shifts to the left, but the left panel stays open.
Ah, that's the link icon. It's meant to look like a chain link. It's the same icon that's used on link-able headings on the site. In API Explorer, if you click on the words it will expand the category. If you click on the anchor link icon it will scroll to that heading at the top of the page and place the fragment in the URL so you can link directly to a category in API Explorer.
As far as going to a random location in the list, it shouldn't be random. It should scroll the link you just clicked on to the top of the page, the same behavior as other headings. Are you seeing behavior different than this:
I wanted to follow up on this, I totally forgot we added a setting to allow you to control the syntax highlighting limit, or disable it entirely. If you open the toolbox in the bottom right of your screen on the dev center, go to Settings > Developer Applications and there are options to lower the max payload size for highlighting or disable it entirely.
Unfortunately, this setting isn't documented in the Using API Explorer guide, but I'll make sure it gets added.
