Kim Parsell 1:09 pm on September 16, 2014
Tags: docs ( 156 )

Docs Team Update: September 11, 2014

The following is the status of our current projects:

1. DevHub:

All DevHub-related issues with the parser have been identified.

The workflow has been implemented for editing parsed content in the code reference. Parsed content has been moved to metadata to allow the post editor to be used for curated content.

The content migrationMigration Moving the code, database and media files for a website site from one server to another. Most typically done when changing hosting companies. workflow from the Codex was discussed. A style guide for the content will need to be written. Redirects will need to be put into place for all content that has been moved.

(9/9/2014 chat summary)

2. Handbooks:

The Seattle Documentation Sprint was very productive. 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 made considerable progress – several pages were completed, reviewed, and are now marked at 100% for content. There are still 6 sections that need to be completed. The Theme Developer Handbook also made progress during the sprint.

If you would like to help out with the handbooks (writing content, editing, proofing, testing), please contact @samuelsidler, @blobaugh, or @sewmyheadon.

(9/10/2014 chat log)

3. Docs at WCSF:

The team discussed what project should be the focus of the 2-day team 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. after WCSF during the 9/11/2014 team office hours. We reviewed the projects listed in @siobhan‘s post. Completing the developer handbooks is the project far enough along that the team could finish them during the meetup. @samuelsidler will work up a plan with both handbook editors for completing the content this week.

(9/11/2014 chat log)

#docs

Kim Parsell 12:43 am on September 8, 2014
Tags: docs ( 156 )

Docs Team Update: September 4, 2014

The following is the status of our current projects:

1. DevHub:

The team didn’t have their regular meeting this week, so there is no report for DevHub.

2. Handbooks:

The handbook teams are moving things along. More progress was made on finishing up sections 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. The Theme Developer Handbook was planning for a big push this weekend with the Seattle Documentation Sprint.

If you would like to help out with the handbooks (writing content, editing, proofing, testing), please contact @samuelsidler, @blobaugh, or @sewmyheadon.

(9/3/2014 chat summary)

3. Version 4.0 Codex Page:

@DrewAPicture took the lead on getting the Version 4.0 Codex page prepared before the release on 9/4/2014. Thank you to everyone who pitched in to help!

#docs

Kim Parsell 4:01 am on September 2, 2014
Tags: docs ( 156 )

Docs Team Update: August 28, 2014

The following is the status of our current projects:

1. DevHub:

Some of the pull requests for the parser have been committed. @siobhan will review the open parser issues, and tag any that are related to DevHub.

Work continues on implementing changes to the code reference.

@samuelsidler is working on the handbook content migrationMigration Moving the code, database and media files for a website site from one server to another. Most typically done when changing hosting companies., and will report any handbook theme issues encountered during migration.

(8/26/2014 chat summary)

2. Handbooks:

Progress was slow this past week on both handbooks. @samuelsidler said he had some contributors to the handbooks during the WordCampWordCamp WordCamps are casual, locally-organized conferences covering everything related to WordPress. They're one of the places where the WordPress community comes together to teach one another what they’ve learned throughout the year and share the joy. Learn more. Boston 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/..

@blobaugh said he needs help with the Sanity Practices page in Section 2 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.

@sewmyheadon said the next Seattle Docs Sprint is coming up on Saturday, September 6.

(8/27/2014 chat log)

#docs

Kim Parsell 3:57 am on August 23, 2014
Tags: docs ( 156 )

Docs Team Update: August 21, 2014

The following is the status of our current projects:

1. DevHub:

The team did a bug scrub of open MetaMeta Meta is a term that refers to the inside workings of a group. For us, this is the team that works on internal WordPress sites like WordCamp Central and Make WordPress. tickets. There are 6 tickets that will require changes to the parser before they can be worked on. We need a volunteer to step up and help maintain the parser so these can move forward.

Implemention of changes for both examples and explanations in the code reference should happen this week.

(8/19/2014 chat summary)

2. Handbooks:

The handbooks received a lot of attention from both the WordCampWordCamp WordCamps are casual, locally-organized conferences covering everything related to WordPress. They're one of the places where the WordPress community comes together to teach one another what they’ve learned throughout the year and share the joy. Learn more. Grand Rapids and WordCamp Maine contributor days. Huge thanks to all the new contributors!

Both handbooks are progressing, and the focus is now on getting them into a usable state so they can be migrated to their permanent home at developer.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/.

The team is considering having weekly online handbook sprints to encourage contributors to work on the handbooks on a regular basis.

(8/20/2014 chat summary)

#docs

Kim Parsell 11:27 pm on August 15, 2014
Tags: docs ( 156 )

Docs Team Update: August 14, 2014

The following is the status of our current projects:

1. DevHub:

No progress on integrating Posts2Posts with the parser. We’re looking for a volunteer to help move this forward.
@coffee2code is currently working on implementing examples in the code reference. Work on implementing voting has been put on hold until that is completed.
@DrewAPicture and @coffee2code have been discussing how to implement content in the code reference. @DrewAPicture has offered to spearhead some of the changes needed.
@nicolealleyinteractive‘s pull request was merged in, including the archive/search simplification. Other handbook design changes have been merged as well.
@ryelle worked up a template for a dashicons page for the Resources section. She will put together a patch so we can migrate it to DevHub.

(8/12/2014 chat log)

2. Handbooks:

@topher1kenobe cleaned up the spreadsheet for 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 so that it better reflects the current status of the handbook. He also added Chapter 17 (Helper Tools), and finished the 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/ section (pending final edit).
@samuelsidler started migrating the Theme Developer Handbook to its permanent home on DevHub (section 1). Adjustments to the handbook plugin/theme will be made, as needed, to ensure the content looks good. Link cleanup will happen as part of the migrationMigration Moving the code, database and media files for a website site from one server to another. Most typically done when changing hosting companies..

(8/13/2014 chat log)

#docs

Kim Parsell 6:32 pm on August 8, 2014
Tags: docs ( 156 )

Docs Team Update: August 7, 2014

1. Project Status: The following is the status of our current projects:

DevHub: Work continues on implementing Posts2Posts in the parser. @coffee2code is working on the voting functionality. The team seems happy with the proposal for dealing with content in the code reference. @coffee2code will work on the implementation. (8/5/2014 chat summary)
Handbooks: The Metadata section in 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 is complete, and awaiting review. Part One of the Theme Developer Handbook is nearly complete. The Seattle Docs Sprint last Saturday had several contributors working on both handbooks, and a few new contributors were brought up to speed so they can start working on the handbooks as well. (8/6/2014 chat summary)

2. Weekly Docs Chat: During this week’s chat, we discussed changing the format of our weekly Docs team chat on Thursdays from a formal meeting to general office hours, with a weekly P2P2 P2 or O2 is the term people use to refer to the Make WordPress blog. It can be found at https://make.wordpress.org/. post for the individual teams to post their weekly status update to. With the team working on individual projects, most of the discussion takes place during the weekly project meetings rather than the general chat on Thursday. The full proposal is posted on Make/Docs for the team to review and discuss further. (8/7/2014 chat log)

#docs

Kim Parsell 2:30 pm on August 2, 2014
Tags: docs ( 156 )

Docs Team Update: July 31, 2014

The following is a summary of the topics discussed:

1. DevHub: @samuelsidler said more progress was made. @coffee2code is in the process of committing new stuff, including the mods to selectively enable the handbooks (with necessary tweaks and fixes), along with fixes for #437 (Make watch/unwatch a post action link rather than a widgetWidget A WordPress Widget is a small block that performs a specific function. You can add these widgets in sidebars also known as widget-ready areas on your web page. WordPress widgets were originally created to provide a simple and easy-to-use way of giving design and structure control of the WordPress theme to the user.), #439 (add handbook name to the top of handbook pages), and #436 (remove “Flag Unresolved” from handbook pages). He’s also done some initial work on example voting. @siobhan and @samuelsidler are discussing the best way to get general (non-typo) feedback, such as how the site functions, new features, etc. (7/29/2014 chat log)

2. Handbooks: The WordCampWordCamp WordCamps are casual, locally-organized conferences covering everything related to WordPress. They're one of the places where the WordPress community comes together to teach one another what they’ve learned throughout the year and share the joy. Learn more. Vancouver 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/. had 6 people focusing on the handbooks. Most of them worked on the Theme Developer Handbook, but a couple worked on 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. @blobaugh and @sewmyheadon send a huge thank you to the WordCamp Vancouver contributors! We also discussed the internal links in both handbooks. Currently there are a lot of links to existing Codex pages that will need to be changed to internal links in the handbooks, and the Codex pages redirected. A full review of all links will take place once the handbooks are migrated to DevHub, and necessary changes made at that time. (7/30/2014 chat log)

3. Seattle Docs Sprint: @sewmyheadon said the next WordPress Docs Sprint is Saturday, August 2, 2014 (today!) at 10am PDT in Seattle. The focus will continue to be on both developer handbooks. Contributors can also participate virtually in the #wordpress-sfd IRC channel.

You can read the chat logs here.

#docs

Kim Parsell 1:52 am on June 22, 2014
Tags: docs ( 156 )

Docs Team Update: June 19, 2014

The following is a summary of the topics discussed during our weekly Docs chat:

1. DevHub: @samuelsidler said Post2Posts still needs to be implemented with the parser. @coffee2code has implemented source code on the individual pages, and is working on implementing the examples functionality. The handbook 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 has been updated with the required changes.

2. Handbooks: Some progress was made this week, mostly in the Plugin Developer handbook. @blobaugh and @sewmyheadon will add the anticipated new permalinks for each page to the spreadsheets for their respective handbooks. Once that is done, @samuelsidler plans to manually migrate over completed handbook pages, one section at a time, to their permanent home on developer.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/. Adjustments will be made to the handbook theme and plugin, as needed, during content migrationMigration Moving the code, database and media files for a website site from one server to another. Most typically done when changing hosting companies.. Contributor information is being gathered, and will be included on the Credits page in each handbook.

3. Docs Issue Tracker: Development has stagnated on the project, and there most likely isn’t any developer time available right now. I’ll be going through the alpha release post comments, and creating TracTrac Trac is the place where contributors create issues for bugs or feature requests much like GitHub.https://core.trac.wordpress.org/. tickets for suggested changes so the discussion can continue on the tickets.

4. Trac Tickets: @DrewAPicture brought up a new ticket that could be an interesting cross-team effort between CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress., Support, and Docs: #28551 – Add Better Debugging Documentation Into wp-config.php. In addition to providing more debug constants and documentation, the current user sections of the file can be improved with better inline documentation.

The chat logs are available here.

#docs

Kim Parsell 11:45 pm on June 8, 2014
Tags: docs ( 156 )

Docs Team Update: June 5, 2014

The following is a summary of the topics discussed during our weekly Docs chat:

1. DevHub: @siobhan said Post2Posts will be bundled with the parser. @coffee2code will be implementing source code on the individual pages, as well as the examples functionality. Feedback is still needed on implementing explanations in the code reference, and differentiation on the search results pages.

2. Handbooks: @blobaugh said part one of the Theme Developer Handbook is on schedule to be completed by early next week. Two sections 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 are almost complete, and should be done by next week, with one more section near completion. If you are interested in getting involved, contact @blobaugh and @sewmyheadon at the email addresses listed in this post. The subject of a style guide for the handbooks was brought up in this week’s handbooks chat. I noted that the Docs Handbook has a style guide and a tutorial template that should be used as references.

3. Admin Help: @Clorith said he still needs to talk with @jenmylo about working with local 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. organizers to identify areas that their new users are struggling with.

You can read the chat logs here.

#docs

Kim Parsell 1:20 am on June 1, 2014
Tags: docs ( 156 )

Docs Team Update: May 29, 2014

The following is a summary of the topics discussed during our weekly Docs chat:

1. DevHub: @siobhan said Post2Posts will be used to make everything relational, and @Rarst is looking at the best way to implement that. @coffee2code will implement source code on the individual pages, as well as the examples functionality. A link will be added at the top of the Codex to direct people to the new code reference. Feedback is still needed on implementing explanations in the code reference, and differentiation on the search results pages.

2. Handbooks: @blobaugh posted a summary of the weekly Handbooks chat containing the current status of both Developer Handbooks. Part One of the Theme Developer Handbook is on schedule for completion by June 7. One section 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 is complete, and 2 more are near completion. Contact @blobaugh and @sewmyheadon at the email addresses listed in the post if you’re interested in getting involved. The next Docs Sprint is Saturday, June 7, 2014 at 10am PDT in Seattle. Contributors can also participate virtually in the #wordpress-sfd IRC channel.

3. CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. string feedback: TracTrac Trac is the place where contributors create issues for bugs or feature requests much like GitHub.https://core.trac.wordpress.org/. ticket #28199 is a request to improve the upgrade translations text, and needs feedback from the Docs team. @siobhan added her feedback to the ticket.

You can read the chat logs here.

#docs