Opened 6 years ago

Closed 3 years ago

#3644 closed task (blessed) (fixed)

Remake of the site

Reported by: juliekuehl's profile juliekuehl Owned by:
Milestone: Priority: normal
Component: Learn ( Keywords: dev-feedback ui-feedback ux-feedback


The Training Team has a dream and would like to ask for help with the (aka Learn) site. We have progressed far enough with updating our infrastructure and processes to want to begin thinking about the final location for our lesson plans once they are completed.

We imagine that the use case of the site would be as a place for people who are planning meetups and workshops to go to and search for ideas and resources for their event. For example:

  • Meetup organizer: “I have a one-hour meetup coming up where we’d like to talk about site backups”
  • Workshop organizer: “I have a half day where we want to help onboard people new to WordPress”

It is thought that they will have a few things in mind when the come to the page:

  • an audience (users, designers, developers, speakers, etc.)
  • a duration (time constraint)
  • a topic, even if very general
  • possibly an teaching strategy (e.g., lecture, demonstration, hands-on exercises, etc.)
  • others?

Therefore would would like to be able to help them search and filter resources by those criteria.

We have requested help from the Design Team ( but took the liberty of creating a first draft of wireframes, which are attached. We offer them up as a starting place for further discussion.

We do not yet have fully vetted material to publish on the site. It was thought that we should work with the Design Team and the Meta Team before that point as we would be happy to make adaptations for a better design and user experience.

Our lesson plans are currently being worked on in GitHub ( and we are managing our work on a Trello board (

A couple of pieces of the dream are that it would be possible to:

  • Push a big red button and send a completed lesson plan from GitHub to the Learn site.
  • Have one theme for all the lesson plan slides. That might require a place for “master” CSS and JS files. (Each lesson plan would have the HTML file.)
  • Bundle those CSS/JS/HTML file for downloading for offline use

Can you help us think this through, let us know what is possible, and help build it out?

Attachments (3)

WordPress Training Team Learn Site.pdf (409.1 KB) - added by juliekuehl 6 years ago.
Draft wireframes for for discussion
learn_org.pdf (4.5 MB) - added by batcatforever 6 years ago.
learning_theme_specificiations.pdf (4.4 MB) - added by batcatforever 5 years ago.
Annotations relating to functionality & theme structure

Change History (17)

6 years ago

Draft wireframes for for discussion

#1 @netweb
6 years ago

Welcome to Meta Trac Julie and thanks for creating the ticket :)

I've spoken to Julie in Slack in regard to the above proposal and my suggestion was to use the "GitHub Markdown importer" currently being used for the wp-cli and REST-API docs hosted at

The training team currently have ~100 lesson plans hosted on GitHub, each repo is its own lesson plan, each lesson plan has a standardised structure:

images (image assets folder)
slides (slides folder)
LICENSE (The lesson plan)

Looking at how the above tool would address the teams dreams:

Push a big red button and send a completed lesson plan from GitHub to the Learn site.

The training team would maintain a manifest.json containing the lesson plans that would be required to be sync'd to by the "GitHub Markdown importer". Each time a new lesson plan is ready for deployment adding a new entry to the manifest.json file would be that "big read button" and would then be automaticly sync'd to

Have one theme for all the lesson plan slides. That might require a place for “master” CSS and JS files. (Each lesson plan would have the HTML file.)

A new theme for site can be created or adapted from any of the existing themes such as wporg-developer or Gutenberg themes once feedback from the Design team has been received.

Bundle those CSS/JS/HTML file for downloading for offline use

This would be part of the above theme functionality, possibly also supporting Markdown and PDF exports


  • #3593 to "Centralize GitHub Markdown Importer" as a couple of variations of this tool currently exist.
  • #3377 Sync Coding Standards content from GitHub to DevHub

This ticket was mentioned in Slack in #design by michelemiz. View the logs.

6 years ago

6 years ago


#3 @batcatforever
6 years ago

Research attached. Showing some current learning organization methods in WP and from other learning websites

#4 @juliekuehl
5 years ago

The mockups created by @batcatforever and the Design Team can be found at:

#5 @juliekuehl
5 years ago

Training Team's Trello card:

Design Team's Trello card:

Marketing Team's Trello card:

#6 @ocean90
5 years ago

#4014 was marked as a duplicate.

#7 @juliekuehl
5 years ago

  • Keywords needs-design removed

The design mockups are complete. We are now making changes to our GitHub organization to place all the lesson plans within the repo.

#8 @juliekuehl
5 years ago

The "master" repo ( has now been set up with the information for all of our lesson plans in one place.

I believe we are now ready to move forward with development of the site.

This ticket was mentioned in Slack in #meta by juliekuehl. View the logs.

5 years ago

5 years ago

Annotations relating to functionality & theme structure

#11 @jonoaldersonwp
4 years ago

Is this project dead? If so, I'd like to remove the current site for SEO + marketing reasons.

#12 @juliekuehl
4 years ago

Absolutely not! We have been working for over a year to get it moving forward and could use some help getting it in place.

#13 @jonoaldersonwp
4 years ago

Ah, good news!

#14 @dd32
3 years ago

  • Resolution set to fixed
  • Status changed from new to closed

I'm going to close this as fixed, although many parts may not have been implemented as suggested.

The site has had a major overhaul recently, if others would like to make specific contributions is the new home for tracking issues.

Note: See TracTickets for help on using tickets.