-
Notifications
You must be signed in to change notification settings - Fork 100
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feedback - Improve the lesson preview CTA banner #2864
Comments
This came up in Slack, linking here for full context. |
Oh, interesting. Thanks for calling attention to this @Clorith. I do see what you mean. Some questions that came up for me:
|
@thetinyl See #2829 for an issue related to the "preview" wording!
I do think it's preferable if people register for the course rather than just preview its lessons. It allows us to gather feedback when they complete the course, and gives them a record of having taken the course on their WordPress.org profile. It also allows them to get all the benefits of going through the course sequentially, including the interactive exercises like quizzes. The previews are a nice-to-have option that we offer, but overall it's a better experience for everyone if they register. |
So I've been noodling over this one. As @Clorith points out, I think there's value in being descriptive to provide clarity on what added benefit logging in/registering provides. I also think there's a balance we need to strike with the Training team's goals and staying true to the complete Learn experience. Is it fair to claim that, while someone can see almost all the lesson content in "preview mode" (pulling language from @fcoveram's proposal in #2869)... they can't actually complete the lesson without logging in (they can't track and they'll be missing quizzes and other interactive bits)? If this is the case, my suggestion for updating the language would be something like:
|
Question to @thetinyl
Is it ok to swap "register" with the "log in" words to match the design? Here is a screenshot of how it would look like on the page. On the other hand, after users log in to the WordPress site, they need to "take the lesson" to see the content and start tracking the progress. What could be a good copy for both the message heading and the CTA? Here is a screenshot from the design page in Figma. If you compare this screen with the previous one, this one has the admin bar showing the user info. |
@fcoveram Absolutely! As for the other message... that's a tricky one. Especially if a logged in user is just previewing the lesson content (which I assume works the same way for both user states?) Maybe something like:
|
Yes. Logged and not logged in users will land on a page with the message and no visible content related to the lesson. The copy suggested works well. I will update the content 🙂 |
Type of feedback
// dev
Description
Users may think they are required to have an account on WordPress.org to take a lot of the lessons right now, due ot the wording of the banner when previewing lessons.
Being signed in should only be a requirement if you wish to track your progress, or take the quizzes associated with a course.
By updating the text from "Register or sign in to take this lesson." to something a bit more descriptive such as "Register or sign in to track your progress, and participate in lesson quizzes." we can avoid confusion, and reduce unnecessary signups on WordPress.org.
I included a secondary alternative, although I think it adds a bit too much text and can be a bit more confusing, I think it's an interesting idea to just get a conversation going on a potential second iteration perhaps. This adds in a byline to make it explicitly clear that an account is not needed with the wording "This is a public lesson, you do not need an account to access this course."
Screenshots or screen recording (optional)
The current banner indicates you need to register or sign in to take this lesson.
The banner with the proposed new text.
This is merely a concept proposal on making it more explicit that an account isn't needed, but this may as noted add some confusion?
The text was updated successfully, but these errors were encountered: