Skip to content
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

WordPress Filter Hooks #2081

Closed
Tracked by #1984
jonathanbossenger opened this issue Dec 5, 2023 · 7 comments
Closed
Tracked by #1984

WordPress Filter Hooks #2081

jonathanbossenger opened this issue Dec 5, 2023 · 7 comments
Assignees
Labels
[Content] Published Marks closed issues as content that was actually published.

Comments

@jonathanbossenger
Copy link
Collaborator

jonathanbossenger commented Dec 5, 2023

Details

  • Content type (Course, Tutorial, Online Workshop, or Lesson Plan): Lesson
  • Content title: WordPress Filter Hooks
  • Topic description: Explain the concept of filter hooks, how they work, and how to use them.
  • Audience (User, Developer, Designer, Contributor, etc.): Developer
  • Experience Level (Beginner, Intermediate, Advanced, Any): Any

Learning Objectives

  • Identify what filter hooks are
  • Describe how filter hooks work
  • Explain how to use filter hooks with an example

Related Resources and Other Notes

Automation Code

@jonathanbossenger
Copy link
Collaborator Author

jonathanbossenger commented Feb 11, 2024

Lesson creation checklist

  • Gather any relevant links to Support, Docs, or related material
  • Description and Objectives finalized
  • Lesson created and announced to the team for Q/A review
  • Lesson submitted and published to WPTV
  • Lesson transferred to YouTube
  • Lesson reviewed and ready to publish
  • Lesson published to Learn.WordPress.org

@jonathanbossenger jonathanbossenger self-assigned this Feb 11, 2024
@jonathanbossenger
Copy link
Collaborator Author

Video for review:

03-WordPress.Filter.Hooks.mp4

@JunebackpocketACE
Copy link

I watched Hooks, Action Hooks, I might as well finish with Filter Hooks. :)
I had playback issues with this video at around the 3-minute mark. I refreshed and rewatched it from the beginning.

  • [ x] Learning outcomes/objectives are clear.
  • [ x] Technical concepts introduced in the content are accurate.
  • [ x] The speed of demonstrations is easy to follow.
  • [ x] The narration audio matches what is shown visually.
  • [ x] Spelling and grammar are correct.
  • [ x] Sound quality is consistent throughout the video.
  • [ x] [Brand Usage Guidelines] and [Promotional Guidelines] are being followed.
  • [ x] Media assets are all in the public domain ([CC0].

@ironnysh
Copy link

ironnysh commented Mar 4, 2024

Tutorial/Lessons Review Checklist

  • Learning outcomes/objectives are clear.
  • Technical concepts introduced in the content are accurate.
  • The speed of demonstrations are easy to follow.
  • The narration audio matches what is shown visually.
  • Spelling and grammar are correct.
  • Sound quality is consistent throughout the video.
  • Brand Usage Guidelines and Promotional Guidelines are being followed.
  • Media assets are all in the public domain (CC0).

Same here, @JunebackpocketACE :-))

After watching all three, I wonder if it would make sense to show the snippets from the other lessons on screen, so people can better orient themselves inside the functions.php file. On the other hand, in the first tutorial (Hooks) you demonstrate the functionality using a plugin, which means going back to record a new section.

@jonathanbossenger
Copy link
Collaborator Author

After watching all three, I wonder if it would make sense to show the snippets from the other lessons on screen, so people can better orient themselves inside the functions.php file. On the other hand, in the first tutorial (Hooks) you demonstrate the functionality using a plugin, which means going back to record a new section.

Yeah, this one I struggle with a lot, especially in the context of learning pathway lessons vs stand-alone tutorials. How much is too much/how little is too little.

I'm going to make a note of this, but publish the lesson as is anyway. If we get feedback from learners that it's confusing, I can always add the extra bits.

@jonathanbossenger
Copy link
Collaborator Author

@bsanevans bsanevans added the [Content] Published Marks closed issues as content that was actually published. label May 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
[Content] Published Marks closed issues as content that was actually published.
Projects
Status: 📜 Published or Closed
Development

No branches or pull requests

4 participants