Happy Friday Everyone!
Your Community product team wrapped up another release earlier this week and wanted to briefly share key highlights of what we released.
We fixed an issue where Japan and Korea community links on Creative Cloud Home were redirecting to a non-localized page. Localization presents a great opportunity for our platform to become more inclusive and attract more international creative customers to Community. By fixing issues like these, we unblock access to our localized communities and capture this opportunity.
We fixed an issue where users couldn't translate non-English posts containing code formatting. By doing this, we improve the machine translation experience by extending it to another use case. Now, our fantastic Community Professionals, Employees, and general Community Members don't have to separately split out text from posts with code to an external translation service -- saving everyone some time and mouse clicks.
We fixed an issue for new users whose username edit strip wasn't visible while drafting a response to a Bug or Idea post. Identity is a critical element of leading Community platforms. By fixing this issue, we remind new users that they have an identity when replying to a post.
As a part of our efforts to improve email notifications, we dropped the word "Discussions" from the subject line of all Community email templates. Community Professionals are power users of our email features and are a critical piece of our engagement loop; by pushing updates like these, we improve their quality of life and reduce clutter -- allowing them to focus more on helping our awesome customers.
We fixed several bugs that we came across while implementing a custom CSS skin for our home page. Sustained investments like these make the experience better for our users by reducing the time it takes to load the page.
And that's a wrap for our update!
Reach out if you've got any questions or feedback/ideas.
Your Community Product Team
Thank you for 2 - 4 updates, but first is rather opposite to the goal...
Regarding Japan and Korea communities if I'm right you mean distinct forums (which not everyone visit) for these nations, so not just with translated interface but entirely dedicated to use particular languages. At least it was like it so far, but maybe it has changed? If not, I'd say we become more exclusive, while such separation can't be seen too atractive for everyone. Don't you think we should share same space by default to have more chance to meet other members than divide us into 'reserved' sections?
[post edited by moderator - please refrain from using offensive words]
Thank you for providing your honest opinion.
These are not "reserved" sections for our users. The JP & KR community forum is open to everyone in the Global Community and vice versa.
We've created language support forums to better serve our customers by providing them with the choice to get help in their native language and connect with peers. Our objective here is to help unblock our customers, so that they can accomplish their creative goals. And customers have told us, the more we can help them in their native language, the better experience they have with us.
Hope this helps and thank you for sharing your feedback.
PS: We edited your comment because it contained nouns that were inappropriate, especially when put side by side. While I appreciate you adhering to #4 of our Community Guidelines (Be Authentic) by being honest with us, I would also remind you about Guideline #1 (Be Respectful) by avoiding the use of inappropriate language.
When is the updat that will make Creative Cloud processes stop taking up so much CPU percentage? With no Adobe programs open, I can't imagine why, nearly 24 hours a day, Creative Cloud is using 40% or more of my laptop's CPU. I see this problem all over the forums (for YEARS) and it still persists.