Hacktoberfest 2026：维护者为十月标记出来的 issue，仍然开放、适合新手。 浏览 Hacktoberfest issue

Sending blocks to WordPress?

未关闭
#5 2 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

评估

难度
5/5
预计耗时
一周以上
新手友好度
25/100
Issue 类型
功能
描述清晰度
需要澄清
活跃度
停滞
技术栈
javascript, wordpress
领域
api, backend-api-design, web-dev

调研方向

Start by reviewing the WordPress addPost API behavior described in the issue, especially the proposed html content_type and block conversion. No files, tests, or entry points are named, so the first step is to locate the relevant API integration. Done would require an agreed architecture for centralizing HTML-to-block translation and a defined implementation scope.

由索引模型根据 Issue 内容生成。

描述

As more people at Automattic try WordLand I'm hearing a question, always politely asked, why aren't we using blocks?

There's no religious issue here, if it were easy to do, I would be ready to try it soon, to see what happens, if anything in WordLand breaks. On an experimental basis.

My first thought though, is why the addPost API on the WP side of it, doesn't do the translation. If I specify the content_type of the content as html, the server could parse that into a block structure.

In any case I wanted to open a place to explore this from an architecture standpoint. If there has to be an HTML parser somewhere that generates block, I would think it should be as central as possible, so everyone doesn't have to write the same tedious code. It's the kind of thing imho you want to bury as deeply as you can.

主要语言
JavaScript
星标
21
派生
2
30 天内没有已合并 PR

贡献指南

这个仓库没有索引到贡献指南

从这里开始

  1. 先读完整个 Issue，再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库，在一个分支上完成修改。
  4. 提交 Pull Request，并在描述里引用这个 Issue 编号。

scripting/wpIdentity 的其他 Issue

查看 scripting/wpIdentity 的全部 Issue

相似的 Issue

更多 JavaScript Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。