Blog Post

Release Notes
2 MIN READ

Khoros Community Classic 23.3 Release

AshaC's avatar
AshaC
Khoros Staff
2 years ago

Developer Experience


Dark Mode has arrived at the Developer Doc Portal!

According to a 2020 survey, 70% of software engineers prefer dark mode over traditional brighter user experiences. When you're browsing through API documentation to find the endpoint(s) you need to get the job done, a bright white screen may not be the best option for you.

This new experience is now standard across our entire Developer Documentation Portal for anyone that has dark mode set as their operating system's default. You can also toggle dark mode on and off using the sun/moon icon in the upper-right corner of the site.

You found it! We fixed it!

General bug fixes

  • Previously, in communities with multiple instances, when you added new keywords to filter content (under Admin > Mod Tools > Content Filters > Manage Filters), only the instance in which the keywords were added reflected the change. This issue is now fixed. Now, in multi-instance communities, filter keywords are copied successfully to all community instances.  

  • The issue where member’s online status intermittently showed them offline when they were signed in to the community is fixed.

  • Previously, in a multi-node community, when you moved a board to another category, the changes were reflected only on that node where the movement was made. This issue is fixed. Now, in multi-node communities, when you move a board to another category, the changes are reflected on all nodes of the community.

  • The issue where @mentioned members of a blog post that was scheduled for publication were notified and emailed multiple times when published is fixed. 

  • The issue where @mentioned members of the draft of blog posts received multiple notifications in their feed is fixed.

  • Previously, when admins enabled product catalog sync and scheduled the sync, the product catalog sync failed to run and threw an unexpected error. This issue is fixed. Now, the product catalog sync runs successfully in the scheduled time. 

Accessibility fixes

  • The issue where unnecessary heading tags were added on the FAQ pages of the community is fixed. 

 

 

Updated 6 months ago
Version 4.0
communities classic
release notes
AshaC's avatar
Khoros Staff
Joined October 22, 2019
View Profile
Node avatar for Release Notes
Release Notes

Review release notes and updates for all of our products! Select a tag to browse by product or resource type.

  • tyw's avatar
    tyw
    Boss
    2 years ago

    AshaC , yay for dark mode and the content filter fix - thank you! 

    Since the docs team might be looking for feedback I noticed that the site doesn't appear to be mobile friendly, showing a giant 'before you begin' notice that doesn't disappear, taking up 60% of the page (screenshot) (link show in screenshot). To reproduce, use Chrome Inspect Mode and set it a mobile device of your choosing. 

  • keithkelly's avatar
    keithkelly
    Leader
    2 years ago

    tyw  nailed it  🔨

    I hope functional things (such as mobile unusability / obnoxiousicity) are on the Khoros radar.

    Khoros:  We painted the party bus!

    Us:  But it still. won't. turn. left.

    That being said, the new paint job is seriously impressive. Pleasing and not too stark.  It's awesome & I'm excited to see a "Developer Experience" category showing up in the release notes.  Thanks Khoros for this upgrade.

  • RyanPi's avatar
    RyanPi
    Khoros Staff
    2 years ago

    @tyw and @keithkelly 

    We certainly share your frustrations with the mobile-friendliness of the developer docs site. However, we decided early in the redesign to focus on desktop support.

    This is due to a couple of factors:

    • The mobile browser usage on the developer docs has historically been in the fractions of a percentage of the total traffic.
    • The third-party platform we use to host our developer documentation doesn't have existing mobile browser support.
    • Adding mobile support to the documentation would require significant development time for the number of users that fit the use case.

    We have this on the list of items we want to tackle in future development cycles and have requested our third-party vendors to prioritize this support in the base platform.

    We definitely want to improve the range of devices we support on the documentation and recognize that this is a pain point for folks that prefer to view the docs from a mobile device.

    I'll share your feedback with the team and see how I can bump the priority of this work up the list. Thank you so much for your patience on this.

     

     

  • keithkelly's avatar
    keithkelly
    Leader
    2 years ago

    RyanPiCan you try just decreasing the height of the header?  Perhaps that will go a long way towards helping make it reasonable even if it's not perfect. 

    Just, a lot of the screen is wasted on the non-content stuff, making it hard to read the content.