Skip to content

6.5 Dev Note Tracking Issue #59155

@Leonardus-Nugraha

Description

@Leonardus-Nugraha

Tracking all Dev Notes from Gutenberg plugin releases 16.8 - 17.7

Please read the information below carefully. If you have questions, connect with @Leonardus-Nugraha via Slack or comment here.

  • 🗓 Deadline March 4th, 2024

Not all developer-related information needs to be in a separate DevNote on the Make Core blog for the field guide. We can group related information. We can already make decisions on some features if it warrants a stand-alone blog post or if the information will be part of 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:

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:
needs dev note and has dev note

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

viewScriptModule: dev note preview - Published

Site editor and page editor unification: dev note preview

Deprecate outer margins: dev note draft

Font Library: dev note draft

Misc Dev Notes: post draft

Block Hooks - Published

Block Bindings - Published

Metadata

Metadata

Assignees

No one assigned

    Labels

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

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions