You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
At the end of the Developer Site landing page, I suggest it could be helpful to add a text link to https://learn.wordpress.org/. This could provide another source of information to folks who may land on this page, but are not development-focused. (it is called out in the footer but as a list of links, not directly)
Maybe something to the effect of:
Looking to learn more about how to use WordPress? Check out [learn.wordpress.org](https://learn.wordpress.org/) for more resources, including user-focused tutorials.
Note: Could also be in a footer. (We could also link to the Developer site from Learn, though that may already be in place.)
The text was updated successfully, but these errors were encountered:
I wonder if we should replace the two links in the "Related" section in the dark banner with a single link to Learn. Both links take you to handbook pages that are also linked from the "Core Contributor Handbook" one on the left. I might be missing context, but at first sight, this looks unnecessarily redundant.
Yeah I think this is a great idea. The Related links do feel redundant. They were brought over from the current landing page, but highlighting is likely more impactful here.
At the end of the Developer Site landing page, I suggest it could be helpful to add a text link to https://learn.wordpress.org/. This could provide another source of information to folks who may land on this page, but are not development-focused. (it is called out in the footer but as a list of links, not directly)
Maybe something to the effect of:
Looking to learn more about how to use WordPress? Check out [learn.wordpress.org](https://learn.wordpress.org/) for more resources, including user-focused tutorials.
Note: Could also be in a footer. (We could also link to the Developer site from Learn, though that may already be in place.)
The text was updated successfully, but these errors were encountered: