Automattic / Automattic/jetpack

Build and serve wpcom-block-editor inside Jetpack

Open
#16,470 2 comments 0 reactions 0 assignees View on GitHub
[Feature] WordPress.com Block Editor [Focus] Performance [Pri] Normal [Size] M Enhancement
Dominant language
PHP
Stars
1.8k
Forks
898
Avg merge
1d 18h
Merged PRs (30d)
774

Description

Currently, wpcom-block-editor is loaded from widgets.wp.com.

In its current form, for _most_ Jetpack sites, it serves two features:
- switch to classic editor button (powered by jQuery, which as a side-note seems an odd fit for a React component)
- some rich text buttons for underline and justify

At a minimum, this file should be built in Jetpack and served from the origin. Separately, we should evaluate if it's necessary at all for non-Atomic Jetpack sites.

Contributor guide

Open the contributing guide

Research direction

Start by locating wpcom-block-editor and the code that currently loads it from widgets.wp.com. Trace how Jetpack builds and serves related editor assets, then verify that this component is served from the site origin and document whether it is still needed for non-Atomic sites.

Written by the indexing model from the issue text.

Assessment

Tech stack
jquery, php, react
Domain
build-system, frontend
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.