Handbooks: Theme & Plugin Developers

After discussion with a few people, and looking through some material that’s been sent to me, I’m thinking it may be better to separate the theme/pluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party development handbooks out from the other, more contributor- focused handbooks. This will let us get a greater level of detail into the theme/plugin dev handbooks. However, I would still like maintain consistency across these two handbooks. Both Chip and Brad sent me through some ideas, and by looking through both of them, I came up with this loose structure that I think we can fit things into.

Part 1: The Basics (how themes/plugins work)
Part 2: Requirements (what you must include in your plugin/theme)
Part 3: Functionality (different functionality available to you and how to implement it – should include working examples)
Part 4: Settings & Options (creating and using options, the settings APIAPI An API or Application Programming Interface is a software intermediary that allows programs to interact with each other and share data in limited, clearly defined ways.)
Part 5: Security (how to stay secure, data validation)
Part 6: Best Practices (UIUI UI is an acronym for User Interface - the layout of the page the user interacts with. Think ‘how are they doing that’ and less about what they are doing., UXUX UX is an acronym for User Experience - the way the user uses the UI. Think ‘what they are doing’ and less about how they do it., AccessibilityAccessibility Accessibility (commonly shortened to a11y) refers to the design of products, devices, services, or environments for people with disabilities. The concept of accessible design ensures both “direct access” (i.e. unassisted) and “indirect access” meaning compatibility with a person’s assistive technology (for example, computer screen readers). (https://en.wikipedia.org/wiki/Accessibility), general best practices)
Part 7: Releasing your Plugin/Theme on WordPress.orgWordPress.org The community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. https://wordpress.org/
Part 8: Glossary

If you’re planning to work on the plugin or theme development handbooks I’d appreciate if you could just let me know what you think of that schema, and tell me whether there is anything that you think won’t fit into those chapters.

The other thing to note, is that these two handbooks will take much longer than the shorter contributor handbooks to complete. I’m going to publish a timeframe and dates later this week, and we’ll plan for a longer time frame on these two.

Let me know what you guys think.