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

Plugin Requirements #2127

Closed
Tracked by #1984
jonathanbossenger opened this issue Dec 21, 2023 · 8 comments
Closed
Tracked by #1984

Plugin Requirements #2127

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

Comments

@jonathanbossenger
Copy link
Collaborator

jonathanbossenger commented Dec 21, 2023

Details

  • Content type (Course, Tutorial, Online Workshop, or Lesson Plan): Lesson
  • Content title: Plugin requirements
  • Topic description: Introduces the basic requirements needed for a valid plugin: a PHP file with a valid plugin header. Briefly cover the rest of the possible fields in the plugin header. Introduce some plugin best practices, like the ABSPATH check.
  • Audience (User, Developer, Designer, Contributor, etc.): Developer
  • Experience Level (Beginner, Intermediate, Advanced, Any): Beginner

Learning Objectives

  • Describe the basic requirements for a valid WordPress plugin
  • Identify all the plugin header fields
  • Explain why some plugins make use of an ABSPATH check

Related Resources and Other Notes

Automation Code

@github-project-automation github-project-automation bot moved this to 👋 Ready to Create in LearnWP Content - Development Jan 15, 2024
@kaitohm kaitohm moved this from 👋 Ready to Create to 🚧 Drafts in Progress in LearnWP Content - Development Jan 15, 2024
@jonathanbossenger jonathanbossenger self-assigned this Feb 5, 2024
@jonathanbossenger
Copy link
Collaborator Author

//lesson

@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 review
  • Lesson reviewed
  • Lesson video submitted and published to WPTV
  • Lesson created on Learn.WordPress.org
  • Lesson video published to YouTube
  • Lesson on Learn.WordPress.org updated with YouTube video
  • Lesson published to Learn.WordPress.org

@jonathanbossenger
Copy link
Collaborator Author

Video for review:

02.Plugin.requirements.mp4

@jonathanbossenger jonathanbossenger moved this from 🚧 Drafts in Progress to 🔎 Ready for Review in LearnWP Content - Development Feb 19, 2024
@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).

Great tutorial, @jonathanbossenger 👏

Not sure if this is the right place (from a Learning Pathways perspective), but it's worth mentioning somewhere that a plugin can also be used to create a block.

@jonathanbossenger
Copy link
Collaborator Author

Not sure if this is the right place (from a Learning Pathways perspective), but it's worth mentioning somewhere that a plugin can also be used to create a block.

So I do cover this in the first lesson of the Introduction to developing blocks module.

@ironnysh
Copy link

ironnysh commented Mar 6, 2024

Oops, haven't watched this one yet 😄

@jonathanbossenger
Copy link
Collaborator Author

@github-project-automation github-project-automation bot moved this from 🔎 Ready for Review to 📜 Published or Closed in LearnWP Content - Development Mar 9, 2024
@kaitohm kaitohm 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

3 participants