Enhance: Add a link to the Beginner User Learning Pathway in the block editor Welcome Guide

[Mayank-Tripathi32]

resolve #67219

What?

This PR proposes updating the final card of the Block Editor's Welcome Guide to include a link directing users to free courses provided by the official WordPress Training Team on Learn WordPress.

Why?

This update aims to bring more attention to Learn WordPress by adding a link to its free courses in the Block Editor's Welcome Guide. Currently, the guide only links to a resource about using the block editor, missing a chance to showcase other learning materials. By including this link, we can help new users access more educational content and improve their WordPress experience.

How?

Updated the final card in the Block Editor's Welcome Guide to include a link to free courses on Learn WordPress, alongside the existing link to the block editor guide. Ensure the new text fits well and keeps the guide's design clear and user-friendly.

Testing Instructions

1. Open the Block Editor Welcome Guide:

   • Log in to WordPress and open a new post or page.
   • Ensure the Welcome Guide appears (if it doesn't, reset user preferences).
     Check the Final Card:

2. Go to the last card in the Welcome Guide.

   • Verify that the new text and link to Learn WordPress are added.

3. Test the Links:

   • Click the "Here's a detailed guide" link to confirm it opens the block editor guide.
   • Click the "f free courses offered by the official WordPress Training Team.↗" link to ensure it leads to Learn WordPress.

4. Review Layout:

   • Check that the new text and links are properly formatted and visually aligned.

5. Test Across Devices:

   • Open the Welcome Guide on desktop, tablet, and mobile to confirm it looks good on all screens.

6. Confirm Accessibility:

   • Use a screen reader or accessibility tool to ensure the new content is accessible to all users.

Screenshots

[github-actions]

👋 Thanks for your first Pull Request and for helping build the future of Gutenberg and WordPress, @Mayank-Tripathi32! In case you missed it, we'd love to have you join us in our Slack community.

If you want to learn more about WordPress development in general, check out the Core Handbook full of helpful information.

[github-actions]

Warning: Type of PR label mismatch

To merge this PR, it requires exactly 1 label indicating the type of PR. Other labels are optional and not being checked here.

• Type-related labels to choose from: [Type] Automated Testing, [Type] Breaking Change, [Type] Bug, [Type] Build Tooling, [Type] Code Quality, [Type] Copy, [Type] Developer Documentation, [Type] Enhancement, [Type] Experimental, [Type] Feature, [Type] New API, [Type] Task, [Type] Technical Prototype, [Type] Performance, [Type] Project Management, [Type] Regression, [Type] Security, [Type] WP Core Ticket, Backport from WordPress Core, Gutenberg Plugin.
• Labels found: First-time Contributor.

Read more about Type labels in Gutenberg. Don't worry if you don't have the required permissions to add labels; the PR reviewer should be able to help with the task.

[github-actions]

The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the props-bot label.

If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message.

Co-authored-by: Mayank-Tripathi32 <[email protected]>
Co-authored-by: annezazu <[email protected]>
Co-authored-by: jasmussen <[email protected]>
Co-authored-by: kaitohm <[email protected]>
Co-authored-by: t-hamano <[email protected]>
Co-authored-by: ndiego <[email protected]>

To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook.

[annezazu]

Thanks for kicking this off! For starters, the text on the fourth slide is way longer. I also noticed we have some widows in the current screens and opened an issue for that here #67601 Ideally, this PR could handle both :) As is either way, the copy is way longer for the fourth item compared to the others and we should shorten. Here's my recommendation to do so:

Current:

Learn how to use the block editor
New to the block editor? Want to learn more about using it? Here's a detailed guide.↗

You can explore these free courses offered by the official WordPress Training Team.↗

Proposed:

Learn more
Explore these free courses from the WordPress Training Team↗ and check out a detailed guide↗ to grow your knowledge.

[jasmussen]

Thanks for contributing!

There are padding improvements to the welcome card itself that need improvement, i.e. why is the bottom padding lower than the left/right padding? I trust that's separate to this PR.

But as far as adding link(s), I think it's possible to do so, however in order for the link to discoverable, legible, actually clicked by users in need, we need to be rather careful about the phrasing too. Anne above alludes to this as well: if there's too much text, people probably won't read it. I'd add, same with links: if there are too many links people just won't click them. So I would challenge this effort to add a single link, instead of two, then see how that goes and performs. More wood behind fewer arrows.

I recognize this PR just adds the links proposed on the issue, so I will relay my comment there too!

[Mayank-Tripathi32]

#67224 (comment)

@annezazu Regarding this, I understand that it’s a bit longer, but I believe users are more likely to notice links when they are placed in a separate paragraph rather than combining them into one. I also think we can further explore improving the onboarding experience as suggested in #67219 (comment)

As for the padding changes, I can address them here if needed, but it seems like #67654 is already open for it.

[kaitohm]

Thanks for starting on this, @Mayank-Tripathi32 . The conversation in #67219 now looks like we'll be redesigning the modal completely. Shall we close this issue and create a new pull request once discussions there have completed?

[Mayank-Tripathi32]

@kaitohm Sure! Lets me close this. We can work on new PR for new modal once the discussions have concluded.