Contributing this fine WordPress Weekend

There are two events particularly relevant to the docs team coming up this weekend:

WP Contributor DayContributor Day Contributor Days are standalone days, frequently held before or after WordCamps but they can also happen at any time. They are events where people get together to work on various areas of https://make.wordpress.org/ There are many teams that people can participate in, each with a different focus. https://2017.us.wordcamp.org/contributor-day/ https://make.wordpress.org/support/handbook/getting-started/getting-started-at-a-contributor-day/. in Manchester, UK

The newly formed WP Contributor Day group is running their first event on March 1st from 10AM – 6PM UTC, @johnbillon has written a post with more details. The event’s site is at WPContributorDay.com.

For docs folks in particular, if you’re in the north of England, why not head on over? It’s sure to be a great day, whatever your skills or experience level.

If you’re elsewhere, and already familiar with contributing then joining in virtually via #wordpress-sfd would be a fantastic thing to do.

Monthly Docs Sprint in Seattle, USA

The Seattle MeetupMeetup All local/regional gatherings that are officially a part of the WordPress world but are not WordCamps are organized through https://www.meetup.com/. A meetup is typically a chance for local WordPress users to get together and share new ideas and seek help from one another. Searching for ‘WordPress’ on meetup.com will help you find options in your area. group are hosting their monthly Docs Sprint on Saturday, too. It’s running from 10AM – 2PM PST.

It’s been a while since we’ve mentioned the additional virtual nature of these sprints here on the blog, so for the benefit of newer contributors, here’s some of the backstory.

In short: the meet-up group welcomes your participation, wherever you may be!

To quote @sewmyheadon, here’s what do to if you’re not in the Seattle area:

Online: If you’re bashful, or simply outside of the Seattle area, you can simply logon to the IRC channel at #wordpress-sfd and participate from anywhere.

Why not take a peek at the getting started page for the handbooks to gather inspiration for your contributing this coming weekend?

Happy weekend, docs!

#contributor-day

Handbooks Chat: 27th Feb

Present: @blobaugh, @caseydriscoll, @hanni, @NikV @philiparthurmoore,and @sams.

1.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 Developer Handbook

The revised outline proposal was finalised last week by @blobaugh and @hanni, who are this week working on getting the content copied over from the “old” to new structure. If you take a look at the handbook you’ll see this is well underway, and we’re hoping to complete the merge in-time for the sprint.

A backup was taken of all content prior to starting this, so as to be able to “revert” in case of disaster, and also to allow the restoration the proper metadata for each and every contributors to each section when appropriate.

The structure can be seen here: https://docs.google.com/spreadsheet/ccc?key=0Ak0ISjkNpXRIdHRVSDlFOWlBakYwRnNJZV9rbDIyOHc&usp=sharing#gid=0

The first section is very much in draft form, and is intended to be written by a couple of folks going through the process of writing their own plugin (including @hanni), so no-one should be alarmed by the apparently bizarre state at present.

Note: until we’ve ported the numbers etc. we’ll not replace the link in either the spiffy new nav or the sidebarSidebar A sidebar in WordPress is referred to a widget-ready area used by WordPress themes to display information that is not a part of the main content. It is not always a vertical column on the side. It can be a horizontal rectangle below or above the content area, footer, header, or any where in the theme., so as not to confuse. This also motivates us to get it finished in time for this weekend’s Docs Sprint. Whilst the sprint is based in Seattle, everyone is welcome to participate, wherever they are.

Admin-wise, @blobaugh is leaving for a trip to Uganda on the 5th March, and will return on the 21st. As such, Ben is eager to get things in tip-top shape prior to his departure.

During @blobaugh‘s trip, @hanni will be the point of contact for the Plugin Developer Handbook.

2. Theme Developer Handbook

Due to travel, Theme Developer Handbook Editor @sewmyheadon was unable to make this week’s meeting, so @hanni attempted to fill his shoes for the day.

@philiparthurmoore kindly joined to help kick-off the effort to integrate some of the fantastic themeshaper.net content. As per previous recent handbook discussions, focus for the Theme Developer Handbook is very much on stage (i).

To this end, over the next couple of weeks @philiparthurmore will be working on an initial one page summary distilling the themeshaper content down to the basics of getting from zero to your first theme, upon which we can then expand as necessary.

He’ll have an outline ready for the Docs Sprint on March 1st, such that any folks present can see where things are going and lend a hand if they so desire.

If anyone else is interested in helping with this, please do leave a comment here or pingPing The act of sending a very small amount of data to an end point. Ping is used in computer science to illicit a response from a target server to test it’s connection. Ping is also a term used by Slack users to @ someone or send them a direct message (DM). Users might say something along the lines of “Ping me when the meeting starts.” Philip, Eric, or myself.

Thanks again everyone!

#handbook-chat, #handbooks

Handbooks Chat: 19th Feb 2014

@sewmyheadon, @blobaugh, and, @hanni had our first checkin yesterday.

  1. Stated utility and purpose of the meetings: to support each other as far as possible, and ensure we’re all the right track with regards to the goals of the handbooks, focusing on incremental progress rather than becoming bogged down with concern over current timeline.
    @hanni’s purpose to allow each editor to focus on their handbook whilst watching for potential problems or unwanted divergences, reviewing diffs on an at least weekly basis and helping out with editing when and as she can.
  2. Agreed on the provisional contents the reference portion of 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 Developer Handbook cut up by @blobaugh and @hanni).
  3. Started on new spreadsheet for the Plugin Developer Handbook to reflect structure update and porting of existing content (links forthcoming).
  4. @sewmyheadon will be meeting with @philiparthurmoore to integrate the ThemeShaper tutorials and restructure Theme Developer Handbook as needed over the next ten days or so.
  5. Welcomed new contributor @lorax who’ll be attending the docs chat today to get involved!

#handbook-chat

Where are we with the Plugin and Theme Developer Handbooks?

Hanni! You just posted something about a handbook status meeting but what’s actually happening with these mythical creatures?

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 Developer Handbook Stasis

We’ve now a proper (as opposed to acting) editor for the Plugin Developer Handbook, in the very capable form of Ben Lobaugh (@blobaugh).

. Ben and I are in the process of re-jigging the structure and existing to fit with the two-tiered goals of the handbooks. Watch this space! The new outline will be ready for the Docs Chat this week, Feb 20th.

Goal Parity

With little policing of contributions over these past months, we’re in danger of creating two unwieldy information dumps as opposed to digestible handbooks.

A rough goal could be stated as providing an overview for each handbook such that:

i) The reader gets into the book and to show them how to build a simple theme, or plugin, so they can see how easy it is and get introduced to the necessary and basic building blocks.

ii) Then, once that overview is complete for each handbook we’ll proceed with more in-depth dives into each section as and when is necessary.

With the current state of the handbooks, we’ll be focusing on finessing (and constructing!) i) for the foreseeable future.

New Contributors

i. Plugin Developer Handbook
We have some great news about increased interest in contributing to the project! (Thanks to all those who graciously caved in to my pestering are champing at the bit to give back and get involved.)

I’m so excited to announce that Woo are eager to give of their time to help the Plugin Developer Handbook effort, in particular: @scottbasgaard, @hlashbrooke, @mikejolley, and @corsonr. Thanks, Woo!

The guys at fooplugins, @bradvin and @awarner20, are also on board.

Thrilled to add that @trepmal, @shaunandrews, @johnny5 (tech reviewing), @westonruter, and @pcrumm have also kindly offered to give of their time, as and when they can.

Existing contributor @jackreichert is also eager to help with the renewed push.

With such a great bunch we should be able to get things moving at a good pace. I’ll be in touch will all of the above over the next few of days to make sure everyone has the correct access and is able to hit the ground running.

ii .Theme Developer Handbook

@philiparthurmoore is eager to work on the Theme Developer Handbook, as is @nudge – good news for the project! Thanks, you two.

Looking to get involved?

If you’re looking to help out with one of the handbooks, feel free to come to any of the weekly check-in meetings, pingPing The act of sending a very small amount of data to an end point. Ping is used in computer science to illicit a response from a target server to test it’s connection. Ping is also a term used by Slack users to @ someone or send them a direct message (DM). Users might say something along the lines of “Ping me when the meeting starts.” myself or the editor for the handbook in question, leave a comment on this post, or join the regular weekly Docs Team chat.

Again, as noted in @kpdesign’s notes from last week’s chat, I take full responsibility for the stalling of the Handbooks. Onwards and upwards, folks!

Lastly, thank you to everyone who has given, and continues to give so much of their valuable time to what is truly a community effort.

#handbooks

Weekly Handbooks Check-in

It’s time to get back on the handbook bandwagon, folks!

We’re starting a weekly check-in meeting between those responsible for the progress of a number of the handbooks, @hanni (general helper), @sewmyheadon (editor of the Theme Developer Handbook), and @blobaugh (editor of the 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 Developer Handbook), and anyone else who is both interested in the progress of the above, and wishes to find out more about getting involved.

The goal of this status meeting is to ensure that we’re keeping an eye on content coming in, making the requisite progress (here’s to getting back the momentum we lost!), doing all we can to support both current, and potential contributors. Most importantly, we want to keep the outlines of the handbooks on track to meet the common goals of outlining the process to build both a theme and plugin for those newer to the process, whilst also providing an appropriate level of reference for those familiar more familiar with theme and plugin development. More to come on this subject.

Please feel free to join, it’ll be in #wordpress-sfd at 5PM Pacific, every Wednesday. Open to all!

#handbooks

GSoC Doc Camp

Quick PSA that we didn’t make the cut for this year’s GSoC Doc Camp. Here’s to getting things together in advance next year!

#gsoc