Sending blocks to WordPress?
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- javascript, wordpress
- Domain
- api, backend-api-design, web-dev
Research direction
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.
Written by the indexing model from the issue text.
Description
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.
- Dominant language
- JavaScript
- Stars
- 21
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from scripting/wpIdentity
-
Difficulty 3/5 1-2 days Newbie friendliness 25/100
scripting/wpIdentity#6 ·
-
WebSockets rewrite Open
Difficulty 4/5 3-5 days Newbie friendliness 25/100
scripting/wpIdentity#4 · 1 comment ·
-
Difficulty 5/5 Over a week Newbie friendliness 20/100
scripting/wpIdentity#2 · 2 reactions ·
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
scripting/wpIdentity#1 ·
All issues in scripting/wpIdentity
Similar issues
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
avniproject/avni-client#2135 ·
-
automated broken-link
Difficulty 1/5 Under an hour Newbie friendliness 85/100
-
agent/security hive/hosted-available-lke648397-260827-5n31 security
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
babalae/bettergi-scripts-list#3674 ·
-
A-Release-Notes C-Editing D-Modest S-Ready-For-Implementation
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
bevyengine/bevy-website#2595 ·