Skip to content

Add Gutenberg post content placeholders#420

Draft
cbravobernal wants to merge 2 commits into
WordPress:trunkfrom
cbravobernal:branch/issue-419-gutenberg-custom-field-placeholders
Draft

Add Gutenberg post content placeholders#420
cbravobernal wants to merge 2 commits into
WordPress:trunkfrom
cbravobernal:branch/issue-419-gutenberg-custom-field-placeholders

Conversation

@cbravobernal
Copy link
Copy Markdown
Contributor

Adds frontend-only Gutenberg post content placeholders for supported SCF fields.

Closes #419

Use of AI Tools

Used AI tooling extensively to help draft the pipeline artifacts, implementation, tests, documentation, and review guidance. All generated output was reviewed and adjusted before submission.

@github-actions
Copy link
Copy Markdown

The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the props-bot label.

Core Committers: Use this line as a base for the props when committing in SVN:

Props cbravobernal.

To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook.

@cbravobernal cbravobernal force-pushed the branch/issue-419-gutenberg-custom-field-placeholders branch from 757c8ee to 67cf387 Compare April 27, 2026 13:15
@cbravobernal cbravobernal marked this pull request as draft April 28, 2026 17:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Experiment: Add Gutenberg-compatible custom field placeholders for post content.

1 participant