Skip to content

6.7 Dev Note Tracking Issue #65784

New issue
New issue
Closed
Task
Closed
6.7 Dev Note Tracking Issue#65784
Task
Assignees
fabiankaegymumtahinafaguni
Labels
[Type] Developer DocumentationDocumentation for developers[Type] Tracking IssueTactical breakdown of efforts across the codebase and/or tied to Overview issues.
@fabiankaegy

Description

@fabiankaegy
fabiankaegy
opened on Oct 1, 2024

Tracking all Dev Notes from Gutenberg plugin releases 18.6 - v19.3

Please read the information below carefully. If you have questions or suggestions, connect with @fabiankaegy via Slack, ping @fabiankaegy on GitHub, or comment here.

Important

🗓 Deadline Drafts for All Dev Notes - October 13th, 2024 (a few days before Beta 3, so there's enough time for reviews)
🗓 Deadline All Dev Notes Published - October 20nd, 2024 (a few days before RC1)

Not all developer-related information must be in a separate DevNote on the Make Core blog for the field guide. We can group related information. We can already decide whether some features warrant a stand-alone blog post or a group post.

Stand-alone post

To streamline the process and eliminate bottlenecks, all writers of stand-alone dev notes will write the dev notes on the Make Core Blog.

Instructions
  • Create your note in a new post,
  • Save as Draft
  • Enable public preview
  • Share the link to the public preview in a comment below as "ready for review"
  • "For dev notes, each one must have at least two reviewers" (Handbook)

Part of a group post

If the information related to your PR will be part of a group post, please write the dev note in a comment on the PR, so it can be reviewed and, if necessary commented on, by the release docs team or a reviewer.

Before you start writing 📣 please read the handbook pages:

Note

The list is incomplete. We are in the process of reviewing plugin release changelogs and add them as we progress on the task.

There are two labels relevant to DevNotes :

If you worked on a feature/module/component that definitely needs a dev note, please assign the label needs dev note If you already added the Dev Note to the make blog on draft or as a comment on the PR, please label it has dev note

TO DO

Progress of the Documentation work for WP 6.7 release (including the DevNotes tracked on this issue) can also be followed at WP 6.7 Documentation project dashboard

PRs with label has-dev-note or a related DevNote draft are marked with [x]

Standalone Posts:

Stabilize Role Attribute Property ✅ - [Draft]
@youknowriad and @getdave have agreed to work on this one and already shared a Draft.

Zoomed Out Mode
I'd love to have one dev note dedicated to all things Zoomed out mode that explains the feature and how to work with it. Including how stuff like the "Section detection algorithm" work.

@getdave has volunteered to help triage this :) A draft is available at #64197 (comment)

Block Bindings
We should have a dedicated dev note for all things Block Bindings that talks about all the new stabilized API's etc. Assigned to @artemiomorales [Draft]

Interactivity API Updates
@DAreRodz or @michalczaplinski , can you help with this?

Components Package Updates

@mirka @ciampo have volunteered to help with this :)

Miscellaneous Editor Updates (TBD)

Query Loop Updates
@ryanwelcher would you be able to help write a dev note for these changes?

Consolidating and expanding block supports
@mumtahinafaguni Would you be able to draft a dev note that includes all these updates in one post? 🤔

Metadata

Metadata

Assignees

Labels

[Type] Developer DocumentationDocumentation for developers[Type] Tracking IssueTactical breakdown of efforts across the codebase and/or tied to Overview issues.

Type

Task

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions