To Note: async (asynchronous) is a situation when an individual is not present during the meeting but, made an effort to make their presence known after the adjournment of the meeting. Additionally, user handles are taken from their respective Slack accounts and may not match up to WordPress.com accounts.

Summary: There was very little to report due to @emaralive was still ramping up on the learning curve for the Docusauras tool. Additionally, @emaralive was the only one in real-time attendance.

1⃣ BP Documentation tracker status:

The stats – 58%, there was no change in percentage points – 58% 58%

NOTE: The stats remained flat due to no new issues were submitted and completions remained the same..

There is 1 (one) issue that is currently In Progress. For details see the In Progress section (Note: Project views are dynamic and are subject to change without notice).

Due to a reduction in the number of writers/authors, the documentation effort has slowed to a crawl.

2⃣ Continuation of the “revisit for the Update README with Documentation roadmap” – Part 11:

Phase 2 – conduct feasibility studies for potential tools which should determine the “final web home“

General discussion – 2nd feasibility study – Docusaurus – example of use: WordPress Playground

@emaralive reported that he was still digesting the documentation provided by the tool maker (Docusaurus).

Phase 2 feasibility studies status

• In progress:
  • WordPress Playground documentation, based on Docusaurus – mentioned here
• To Do:
  • WordPress Advanced Administration Handbook, based on WordPress – inferred here
  • GitHub Wiki – mentioned during April 2, 2025 meeting.
• Completed:
  • Woocommerce REST API documentation, based on Slate – proposed here. – awaiting final report (star to be appended when final report has been published)

– in progress, completed – toying with emojis to indicate basic status of any given study – no emoji indicates “to do”.

To provide context to this ongoing saga, there was information posted related to the backstory of how the documentation effort has progressed from inception to the current process for the creation of documentation, for example:

BP Documentation choices

• July 12, 2023: use BuddyPress code repository to reorganize/migrate/update/improve the BuddyPress Codex.
• January 10, 2024: create this repository to track BuddyPress Codex migration tasks as well as new documentation tasks.
• January 24, 2024: using GitHub to contribute on the next BuddyPress documentation is our choice & it’s a good one!

Note: This agenda item is slated to be on the agenda for the next documentation meeting as a continuance.

3⃣ Open Floor:

There were no conversations nor comments to report for this agenda item.

Next Docs-Chat

NOTE: The docs-chat meeting that was scheduled for August 6, 2025 is cancelled due to a conflict in schedule for @emaralive.

Our next documentation meeting will, tentatively, happen on August 20, 2025 at 19:00 UTC in #BuddyPress.

#docs-chat, #documentation, #summary

Our next documentation meeting will happen on July 23, 2025, at 19:00 UTC in #BuddyPress. Here’s our agenda:

1⃣ BP Documentation tracker status.

2⃣ Continuation of the “revisit for the Update README with Documentation roadmap” – Part 11

Phase 2 – conduct feasibility studies for potential tools which should determine the “final web home“

• General discussion – 2nd feasibility study – Docusaurus – example of use: WordPress Playground

Phase 2 feasibility studies status

• In progress :
  • WordPress Playground documentation, based on Docusaurus – mentioned here
• To Do:
  • WordPress Advanced Administration Handbook, based on WordPress – inferred here
  • GitHub Wiki – mentioned during April 2, 2025 meeting.
• Completed :
  • Woocommerce REST API documentation, based on Slate – proposed here – awaiting final report (star to be appended when final report has been published)

– in progress, completed – toying with emojis to indicate basic status of any given study – no emoji indicates “to do”.

3⃣ Open Floor

If you have specific or additional points to discuss, please do so in the comments section of this post.

#agenda, #docs-chat, #documentation

To Note: async (asynchronous) is a situation when an individual is not present during the meeting but, made an effort to make their presence known after the adjournment of the meeting. Additionally, user handles are taken from their respective Slack accounts and may not match up to WordPress.com accounts.

1⃣ BP Documentation tracker status:

The stats – 58%, there was no change in percentage points – 58% 58%

NOTE: The stats remained flat due to no new issues were submitted and completions remained the same..

There is 1 (one) issue that is currently In Progress. For details see the In Progress section (Note: Project views are dynamic and are subject to change without notice).

Due to a reduction in the number of writers/authors, the documentation effort has slowed to a crawl.

2⃣ Continuation of the “revisit for the Update README with Documentation roadmap” – Part 10:

Phase 2 – conduct feasibility studies for potential tools which should determine the “final web home“

General discussion – 2nd feasibility study – Docusaurus – example of use: WordPress Playground

The conversation was basically a first look at the Docusaurus  tool and based on the implementation by the WordPress (WP) Playground team, this tool looks like it might be a nice fit for the 3 BuddyPress (BP) handbooks (User, Developer & Contributor). At this time, the tool had not been installed (locally) by @emaralive and he had indicated that he had queued up a couple of the online demos that were provided by the tool makers.

A main feature is SPA (Single Page Application); Internationalization (i18n) is another feature of which @rollybueno (async) indicated that he had translated documents for the WP Playground project (see Translation: Tagalog (Filipino) #2336).

@dcavins indicated “[t]he result is screaming fast to use” which the tool makers claim:

Lightning-fast. Docusaurus v2+ follows the PRPL Pattern that makes sure your content loads blazing fast.

Phase 2 feasibility studies status

• In progress:
  • WordPress Playground documentation, based on Docusaurus – mentioned here
• To Do:
  • WordPress Advanced Administration Handbook, based on WordPress – inferred here
  • GitHub Wiki – mentioned during April 2, 2025 meeting.
• Completed:
  • Woocommerce REST API documentation, based on Slate – proposed here. – awaiting final report (star to be appended when final report has been published)

– in progress, completed – toying with emojis to indicate basic status of any given study – no emoji indicates “to do”.

To provide context to this ongoing saga, there was information posted related to the backstory of how the documentation effort has progressed from inception to the current process for the creation of documentation, for example:

BP Documentation choices

• July 12, 2023: use BuddyPress code repository to reorganize/migrate/update/improve the BuddyPress Codex.
• January 10, 2024: create this repository to track BuddyPress Codex migration tasks as well as new documentation tasks.
• January 24, 2024: using GitHub to contribute on the next BuddyPress documentation is our choice & it’s a good one!

Note: This agenda item is slated to be on the agenda for the next documentation meeting as a continuance.

3⃣ Open Floor:

This agenda item was forgone due to an interruption in conversations caused by other pressing matters.

Next Docs-Chat

Our next documentation meeting will happen on July 23, 2025 at 19:00 UTC in #BuddyPress.

#docs-chat, #documentation, #summary

Our next documentation meeting will happen on July 9, 2025, at 19:00 UTC in #BuddyPress. Here’s our agenda:

1⃣ BP Documentation tracker status.

2⃣ Continuation of the “revisit for the Update README with Documentation roadmap” – Part 10

Phase 2 – conduct feasibility studies for potential tools which should determine the “final web home“

• General discussion – 2nd feasibility study – Docusaurus – example of use: WordPress Playground

Phase 2 feasibility studies status

• In progress :
  • WordPress Playground documentation, based on Docusaurus – mentioned here
• To Do:
  • WordPress Advanced Administration Handbook, based on WordPress – inferred here
  • GitHub Wiki – mentioned during April 2, 2025 meeting.
• Completed :
  • Woocommerce REST API documentation, based on Slate – proposed here – awaiting final report (star to be appended when final report has been published)

– in progress, completed – toying with emojis to indicate basic status of any given study – no emoji indicates “to do”.

3⃣ Open Floor

If you have specific or additional points to discuss, please do so in the comments section of this post.

#agenda, #docs-chat, #documentation

To Note: async (asynchronous) is a situation when an individual is not present during the meeting but, made an effort to make their presence known after the adjournment of the meeting. Additionally, user handles are taken from their respective Slack accounts and may not match up to WordPress.com accounts.

1⃣ BP Documentation tracker status:

The stats – 58%, there was no change in percentage points – 58% 58%

NOTE: The stats remained flat due to no new issues were submitted and completions remained the same..

There is 1 (one) issue that is currently In Progress. For details see the In Progress section (Note: Project views are dynamic and are subject to change without notice).

Due to a reduction in the number of writers/authors, the documentation effort has slowed to a crawl.

2⃣ Continuation of the “revisit for the Update README with Documentation roadmap” – Part 9:

Phase 2 – conduct feasibility studies for potential tools which should determine the “final web home“

General discussion – 1st feasibility study – Slate Docs

There were a couple of tests that were failing while deploying to the experimental repository (bp-rest-api-docs) that were related to Ruby versions 2.6 & 2.7. These failures appear to be attributed to upgrading the Bundler version to 2.5.3 which is currently compatible with Ruby version 3.x and not prior versions. Most likely, the testing for Ruby versions of 2.6 & 2.7 should be removed, given that the dependencies have been upgraded to be compatible with Ruby version 3.x.

The Slate tool analysis is basically complete, a documented report will be forthcoming, when time is available.

Phase 2 feasibility studies status

• In progress:
  • Woocommerce REST API documentation, based on Slate – proposed here
• To Do:
  • WordPress Playground documentation, based on Docusaurus – mentioned here
  • WordPress Advanced Administration Handbook, based on WordPress – inferred here
  • GitHub Wiki – mentioned during April 2, 2025 meeting.
• Completed:
  • TBD

– in progress, completed – toying with emojis to indicate basic status of any given study – no emoji indicates “to do”.

To provide context to this ongoing saga, there was information posted related to the backstory of how the documentation effort has progressed from inception to the current process for the creation of documentation, for example:

BP Documentation choices

• July 12, 2023: use BuddyPress code repository to reorganize/migrate/update/improve the BuddyPress Codex.
• January 10, 2024: create this repository to track BuddyPress Codex migration tasks as well as new documentation tasks.
• January 24, 2024: using GitHub to contribute on the next BuddyPress documentation is our choice & it’s a good one!

Note: This agenda item is slated to be on the agenda for the next documentation meeting as a continuance.

3⃣ Open Floor:

There was a support forum topic, BuddyPress plugin not tested with my WP version, which brought to light that the latest version (14.3.4) of BuddyPress is only compatible up to WordPress 6.7.2. There was some discussion on how to handle the next upgrade, however the date for release is still yet to be proposed/determined due to not having a list of bug fixes, etc. that would be included within this next release.

Another topic of interest was an issue with fonts as rendered by various browsers and operating systems. an example is a reply to a support forum topic, cant find all the buddypress widgets, whereby some of the text should have rendered as bold. For example, @emaralive indicated that for Chrome based browsers on a Linux 64 bit distro, what should have been bold text does not appear as bold, however, @dcavins indicated that on a Mac with Firefox and Vivaldi the bold text is rendered as such.

Next Docs-Chat

Our next documentation meeting will happen on July 9, 2025 at 19:00 UTC in #BuddyPress.

#docs-chat, #documentation, #summary

Our next documentation meeting will happen on June 25, 2025, at 19:00 UTC in #BuddyPress. Here’s our agenda:

1⃣ BP Documentation tracker status.

2⃣ Continuation of the “revisit for the Update README with Documentation roadmap” – Part 9

Phase 2 – conduct feasibility studies for potential tools which should determine the “final web home“

• General discussion – 1st feasibility study – Slate Docs

Phase 2 feasibility studies status

• In progress :
  • Woocommerce REST API documentation, based on Slate – proposed here
• To Do:
  • WordPress Playground documentation, based on Docusaurus – mentioned here
  • WordPress Advanced Administration Handbook, based on WordPress – inferred here
  • GitHub Wiki – mentioned during April 2, 2025 meeting.
• Completed :
  • TBD

– in progress, completed – toying with emojis to indicate basic status of any given study – no emoji indicates “to do”.

3⃣ Open Floor

If you have specific or additional points to discuss, please do so in the comments section of this post.

#agenda, #docs-chat, #documentation

To Note: async (asynchronous) is a situation when an individual is not present during the meeting but, made an effort to make their presence known after the adjournment of the meeting. Additionally, user handles are taken from their respective Slack accounts and may not match up to WordPress.com accounts.

Summary: There was only one real-time participant (@emaralive) for this meeting: meaning anyone who added a “reaction” or commented after the fact was included as an asynchronous attendee.

1⃣ BP Documentation tracker status:

The stats – 58%, there was no change in percentage points – 58% 58%

NOTE: The stats remained flat due to no new issues were submitted and completions remained the same..

There is 1 (one) issue that is currently In Progress. For details see the In Progress section (Note: Project views are dynamic and are subject to change without notice). The information covered was related the use of Docker as it pertained to the Slate Docs tool, e.g. “Using Slate in Docker”.

Due to a reduction in the number of writers/authors, the documentation effort has slowed to a crawl.

2⃣ Continuation of the “revisit for the Update README with Documentation roadmap” – Part 8:

Phase 2 – conduct feasibility studies for potential tools which should determine the “final web home“

Update on the progress of the 1st feasibility study – Slate Docs

Using Slate in Docker – The Docker method proved to be outdated when pulling the “Slate Docs” image from the Docker Hub. It appears the dependency requirements were for Ruby 2.6 which was applicable at the time when Docker image and file known as “Dockerfile” were created and the same was apparently true for the Vagrant method. Updating “Dockerfile” to change the Ruby version from 2.6 to 3.3 along with updating “Gemfile” with the addition of  4 more Ruby gems and then using the “docker build” command created a Docker image that will now successfully build and serve the HTML documents.

All this means is that whichever method(s) is/are provided for building the BP REST API documents via the Slate tool, will have to be maintained to ensure a reliable build process, e.g., checked to make sure that there are no conflicts with dependencies as updates are made to those dependencies.

Phase 2 feasibility studies status

• In progress:
  • Woocommerce REST API documentation, based on Slate – proposed here
• To Do:
  • WordPress Playground documentation, based on Docusaurus – mentioned here
  • WordPress Advanced Administration Handbook, based on WordPress – inferred here
  • GitHub Wiki – mentioned during April 2, 2025 meeting.
• Completed:
  • TBD

– in progress, completed – toying with emojis to indicate basic status of any given study – no emoji indicates “to do”.

To provide context to this ongoing saga, there was information posted related to the backstory of how the documentation effort has progressed from inception to the current process for the creation of documentation, for example:

BP Documentation choices

• July 12, 2023: use BuddyPress code repository to reorganize/migrate/update/improve the BuddyPress Codex.
• January 10, 2024: create this repository to track BuddyPress Codex migration tasks as well as new documentation tasks.
• January 24, 2024: using GitHub to contribute on the next BuddyPress documentation is our choice & it’s a good one!

Note: This agenda item is slated to be on the agenda for the next documentation meeting as a continuance.

3⃣ Open Floor:

There were a couple of comments regarding an individual’s inability to attend this meeting in real-time, e.g. scheduling conflicts.

Next Docs-Chat

Our next documentation meeting will happen on June 25, 2025 at 19:00 UTC in #BuddyPress.

#docs-chat, #documentation, #summary

Our next documentation meeting will happen on June 11, 2025, at 19:00 UTC in #BuddyPress. Here’s our agenda:

1⃣ BP Documentation tracker status.

2⃣ Continuation of the “revisit for the Update README with Documentation roadmap” – Part 8

Phase 2 – conduct feasibility studies for potential tools which should determine the “final web home“

• Update on the progress of the 1st feasibility study – Slate Docs
  • Using Slate in Docker

Phase 2 feasibility studies status

• In progress :
  • Woocommerce REST API documentation, based on Slate – proposed here
• To Do:
  • WordPress Playground documentation, based on Docusaurus – mentioned here
  • WordPress Advanced Administration Handbook, based on WordPress – inferred here
  • GitHub Wiki – mentioned during April 2, 2025 meeting.
• Completed :
  • TBD

– in progress, completed – toying with emojis to indicate basic status of any given study – no emoji indicates “to do”.

3⃣ Open Floor

If you have specific or additional points to discuss, please do so in the comments section of this post.