Adding context through Help button#8556
Conversation
Adapting the "Help" generic copy button to give more contextual information to the user. Matching scope with button copy.
Fixing URL when button "About Events" gets pressed.
Remove unused `isRelativePathToDocumentationRoot` import and the `instructionMetadata` / `instructionHelpPage` variables that were left behind after the HelpButton was switched to a hardcoded `/events` path. These triggered ESLint `no-unused-vars` warnings which failed CI under the project's zero-tolerance `--max-warnings=0` rule.
Changed scopeName="Extension" to scopeName={t\Extension`}` so the string is properly picked up by Lingui and available for translators.
Going back to contextual "Help" button for selected actions / conditions rather than "learn more" button under the short description.
LuniMoon
force-pushed
the
In-app-Help-management
branch
from
0c6a8f3 to
b6909a9
Compare
Pointing to possible broken 404 destinations (example: Scene > Does scene exist -> opens 404 on Wiki)
Replicating the Event Sheet UI pattern (have a contextual Help button) in the Object dialog.
|
Changes + 404 error (documentation link) |
LuniMoon
changed the title
LuniMoon
changed the title
| "res/conditions/depart24.png", | ||
| "res/conditions/depart.png") | ||
| .SetHelpPath("/interface/scene-editor/events") | ||
| .SetHelpPath("/interface/events-editor/") |
There was a problem hiding this comment.
It seems that the old link was dead. Should we add a redirection?
There was a problem hiding this comment.
I think that would be a good idea?
There was a problem hiding this comment.
I've added a redirection (GDevelopApp/GDevelop-documentation@7ff9543)
Updating to correct URL suggested by Davy Co-authored-by: D8H <Davy.Helard@gmail.com>
Fixing the past URLs.
…elop into In-app-Help-management
|
@LuniMoon you need to have "scopeName" translated (right now it's a hardcoded english string), using probably "the I'm still a bit afraid this will make a long text in some languages (typically french) which would eat screen estate. It's better than none precise links, but still... 🤔 (so don't remove scopeName, just make sure it's translate. Worst case we can remove how it's displayed but still keep it for a tooltip) |
- Removing the word "About this" and replacing it with "See..." to make translations shorter for existent action/conditions. - Remove the word "About this..." from the rest of the modals to make the
That's fair. Tho I was looking at the web version and it seems like it has a reasonable way to manage responsiveness (line break) for narrower windows. However, I will go from "About X" copy to "See X" copy so the translation goes from "À propos de X" to "Voir X" (which might not be PERFECT verb to use, but will make translations shorter). |
…ame and I18n wrappers from branch alongside master's structural changes (layersContainer, editEventsFunctionParameter, renamed variable props) Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Adding the rules to object groups modals
3 participants
Context:
Having a discreet "Help" button, always available in the interface maintains the door open so the user interacts with the learning content only when they feel stuck or when they need it. <- Good UI pattern.
The issues:
Observations:
Changes:
Note:
For multiple events 'helpPath' leads to the parent page rather than taking the user to the related anchor. The "Helpaths_audit" google sheet (GDrive) has been created to document these UX issues to fix them in the future (next polishing step).