The Connectors API is a framework for managing connections to services like AI, anti-spam, etc. It was introduced on March 18, 2026 with WordPress 7.0 at https://make.wordpress.org/core/2026/03/18/introducing-the-c... and the PR at https://github.com/WordPress/gutenberg/pull/75833.
It introduces a new prominent page in your wordpress settings that recommends popular services to you. All other services are behind a link that says "Find more connectors in the plugin directory" and are less visible.
See image https://developer.wordpress.org/news/files/2026/03/image-1.j..., which is the second image on "What’s new for developers?" at https://developer.wordpress.org/news/2026/03/whats-new-for-d...
In Matt Mullenweg Overrules Core Committers; Puts Akismet on WP 7's Connector ListWordPress
gutenberg
TypeScript2017–2026
WordPress / gutenberg
gutenberg
The Block Editor project for WordPress and beyond. Plugin is available from the official repository.
29Distinct people
30Mentions
0Explicit recommenders
11.8KGitHub stars
What to know before exploring
What it is
The Block Editor project for WordPress and beyond. Plugin is available from the official repository.
GitHub
Where it is used
No documented product use was verified in the last source check.
What people are saying
No recommendation phrase was found in the indexed comments.
No classified warning is attached to this page. Read the discussions before treating silence as approval.
Also in these discussions
No other repository is repeatedly linked in the same discussions.
This week on Hacker News
Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 11:56:56 AM UTC.
No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.
Mentions over time
HN mentions by year30 dated mentions
Observed mentions: 2017-02-11 04:41:50 UTC to 2026-04-19 16:03:52 UTC.
* An incomplete calendar period is marked with an outlined bar. Its count is not directly comparable with a full period.
Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.
View mention counts and date ranges
| Period | Start (UTC) | End (exclusive, UTC) | Mentions | Submissions | Comments |
|---|---|---|---|---|---|
| 2017 | 2017-01-01 00:00:00 UTC | 2018-01-01 00:00:00 UTC | 10 | 4 | 6 |
| 2018 | 2018-01-01 00:00:00 UTC | 2019-01-01 00:00:00 UTC | 5 | 2 | 3 |
| 2019 | 2019-01-01 00:00:00 UTC | 2020-01-01 00:00:00 UTC | 1 | 0 | 1 |
| 2020 | 2020-01-01 00:00:00 UTC | 2021-01-01 00:00:00 UTC | 3 | 1 | 2 |
| 2021 | 2021-01-01 00:00:00 UTC | 2022-01-01 00:00:00 UTC | 4 | 1 | 3 |
| 2022 | 2022-01-01 00:00:00 UTC | 2023-01-01 00:00:00 UTC | 2 | 0 | 2 |
| 2023 | 2023-01-01 00:00:00 UTC | 2024-01-01 00:00:00 UTC | 2 | 0 | 2 |
| 2024 | 2024-01-01 00:00:00 UTC | 2025-01-01 00:00:00 UTC | 2 | 1 | 1 |
| 2025 | 2025-01-01 00:00:00 UTC | 2026-01-01 00:00:00 UTC | 0 | 0 | 0 |
| 2026 (partial) | 2026-01-01 00:00:00 UTC | 2027-01-01 00:00:00 UTC | 1 | 0 | 1 |
From the project README
An excerpt from the repository, fetched Nov 13, 2026.
Read the project’s introduction
Gutenberg
Welcome to the development hub for the WordPress Gutenberg project!
"Gutenberg" is a codename for a whole new paradigm in WordPress site building and publishing that aims to revolutionize the entire publishing experience as much as Gutenberg did the printed word. Right now, the project is in the second phase of a four-phase process that will touch every piece of WordPress -- Editing, Customization, Collaboration (which includes Real-time collaboration, Asynchronous collaboration, Publishing flows, Post revisions interface, Admin design, Library), and Multilingual -- and is focused on a new editing experience, the block editor.
The block editor introduces a modular approach to pages and posts: each piece of content in the editor, from a paragraph to an image gallery to a headline, is its own block. And just like physical blocks, WordPress blocks can be added, arranged, and rearranged, allowing WordPress users to create media-rich pages in a visually intuitive way -- and without workarounds like shortcodes or custom HTML.
The block editor first became available in December 2018, and we're still hard at work refining the experience, creating more and better blocks, and laying the groundwork for the next three phases of work. The Gutenberg plugin gives you the latest version of the block editor, so you can join us in testing bleeding-edge features, start playing with blocks, and maybe get inspired to build your own.
Check out the Keeping up with Gutenberg Index.
Getting Started
Get hands-on: check out the block editor live demo to play with a test instance of the editor.
Using Gutenberg
Download: To use the latest release of the Gutenberg plugin on your WordPress site: install from the plugins page in wp-admin, or download from the WordPress.org plugins repository.
User Documentation: See the WordPress Editor documentation for detailed docs on using the editor as an author creating posts and pages.
User Support: If you have run into an issue, you should check the Support Forums first. The forums are a great place to get help. If you have a bug to report, please submit it to the Gutenberg repository. Please search prior to creating a new bug to confirm it's not a duplicate.
Developing for Gutenberg
Extending and customizing is at the heart of the WordPress platform, this is no different for the Gutenberg project. The editor and future products can be extended by third-party developers using plugins.
Review the Quick Start Guide for the fastest way to get started extending the block editor. See the Block Editor Handbook for extensive tutorials, documentation, and API references. Also, check the WordPress Developer Blog for great articles about block development, among other topics.
Contribute to Gutenberg
Gutenberg is an open-source project and welcomes all contributors from code to design, and from documentation to triage. The project is built by many contributors and volunteers, and we'd love your help building it.
See the Contributors Handbook for all the details on how you can contribute.
To get up and running quickly with code contribution, see Getting Started With Code Contribution. Also check out the other resources available on the Code Contributions page.
In whichever way you wish to contribute, please be sure to read the Contributing Guidelines first.
As with all WordPress projects, we want to ensure a welcoming environment for everyone. With that in mind, all contributors are expected to follow our Code of Conduct.
Get Involved
You can join us in the #core-editor channel in Slack, see the WordPress Slack page for signup information; it is free to join.
License
WordPress is free software, and is released under the terms of the GNU General Public License version 2 or (at your option) any later version. See LICENSE.md for complete license.
Read the full README on GitHubWhat Hacker News says
30 sourcesFor anyone wondering, this is not gutenberg.org, Gutenberg is the name of the Block Editor from WordPress which has 32000 commits.
> The Block Editor project for WordPress and beyond. Plugin is available from the official repository.
https://github.com/WordPress/gutenberg
In [dead]There are efforts to document how you can use WordPress editor as a stand alone library for your web projects. https://github.com/WordPress/Gutenberg/platform-docs/docs/in...
In Ask HN: What is your favorite FOSS WYSIWYG editor?Around 2 years ago I was trying to move my blog to Wordpress. I found that the vast majority of themes want your money (unlike static site generators like Jekyll, Zola, and probably Hugo), I found numerous editing and cursor movement bugs in the Gutenberg editor (https://github.com/WordPress/gutenberg/issues?q=is%3Aissue+s...), I was unable to edit pre code blocks on the mobile app, and converting articles between Gutenberg and classic formats resulted in structural issues (someone else has elaborated on the technical reasons at https://gschoppe.com/wordpress/comments-arent-structure/).
In WP20 and Audrey ScholarsOk, let's not talk about the duotone bit. Let's talk about patterns: https://wordpress.org/patterns/
Why on earth should I include these very beautiful and also very random bird illustrations and colors and typography into my website?
Are these "pattern" in the sense of reusable solution to common problems or just random and non-consistent design blocks?
Also, why on earth should I control border-radii, gradient, colors for every single block in the editor?[0][1]
This is complete madness. For two reasons at least: One, styles should be defined at least on a global level, using tokenized values and possibly exposed only to users with higher capabilities (designers).
Two, authors and editors should focus on content, not styling. Many of them are unable to take rational design decisions. Giving them the power of styling border radii or gradi
Read the rest
ents on multiple buttons/elements in a random fashion on the same page, or even on the same website, is a recipe for a visual disaster.
Yes, you're right about how the semantic data may be stored. Everything else? I can still see a "lousy PowerPoint for the web" everywhere.
What's worst, is that they are pushing these bad design decisions really hard. Breaking existing websites in production. Maybe they'll make it right someday, at least I hope so, but it will take years time. This is why, as I said, all of this should be at least opt-in.
[0]: https://github.com/WordPress/gutenberg/pull/28541
[1]: https://github.com/WordPress/gutenberg/pull/31585
WordPress(.org) has completely lost it. It started outputting real junk in the html[0], out of the blue. This kind of stuff should be at least opt-in.
With this block madness it turned from a "semantic publishing platform" to some lousy PowerPoint for the web.
It's time for a hard fork, or for some new project/idea to disrupt it. It may take some time, but this is something inevitable at this point.
[0]: https://github.com/WordPress/gutenberg/issues/38299
In What are you doing, WordPress.com?Gutenberg is a joke.
Clients wonder how to use it and internally, it's a mess like all the other core part of WordPress.
They leave a bug having the previewing feature broken with any custom fields for 2 years and they don't know what to do.
https://github.com/WordPress/gutenberg/issues/16006
There are plenty of better visual editors out there.
In WordPress 18Wordpress Gutenberg: Dual Licensing Under GPLv2 and MPLv2
2 points · Open discussionAnother alternative is wp-env, which is a small node wrapper over Docker. It’s meant to be very straightforward to use, though less powerful than other tools. It’s used for a lot of core editor development. You basically just have a JSON file pointing at whatever local source code you’re developing (or alternative options you need), wp-env start, and you’re good to go.
I’ve done a lot of development on the project, and it could always use more contributors: https://github.com/WordPress/gutenberg/tree/trunk/packages/e...
In Lokl – WordPress local development environment for Mac, Win and LinuxGutenberg is a really robust and active project[1] in its own right, separate from WordPress, and I hope that it becomes a cross-CMS standard.
If you've worked on any sort of editor, block system, page builder, etc Automattic are hiring very aggressively for senior JS positions. [2] It's a fun and fast-moving project to work on, with a huge impact. Many others are hiring for Gutenberg skills as well, so it's a high-demand competency.
[1] https://github.com/WordPress/gutenberg
[2] https://automattic.com/work-with-us/javascript-engineer/
In 5M+ Wordpress sites use “Classic Editor” plugin> If I wanted to do that on my hypothetical WordPress site, I'd be out of luck.
Well, they are working on a new feature that will (hopefully) change that. It's called Full Site Editing (FSE), and will basically transform the WordPress editor into a complete website builder that, considering the WordPress's market share, may become a thing. It's arriving next year. Ref: https://github.com/WordPress/gutenberg/issues/20791
In FrontPage: The Good, The Bad, and The UglyWell, I'll chime in with a weird bug that was supposedly gone from previous versions but came back in WP 5.4 Gutenberg.
You know those side panels where you can change values for blocks like padding, etc.? Well, every time I started typing in a value, the input field would lose focus. So if I wanted to enter 100 as a value for height in pixels, I would need to enter 1, click back in the field, enter 0, click back in the field, enter 0 again. Or type it in a text edit and copy-paste.
Googling told me it was a bug that had crept back: https://github.com/WordPress/gutenberg/issues/20950
It was fixed again in WP 5.5, but it was agonising working on layouts before that.
In On not choosing WordPress for the W3C redesign projectProposition to change the license from GPL v2.0 to Mozilla Public License v2.0
2 points · Open discussionI took a different approach btw building collaborative editing in WordPress core editor. Knowing about OT/CRDT but decided to go with the approach here: https://github.com/WordPress/gutenberg/pull/1877
Might be useful to you as this is react/redux.
In Creating a Collaborative EditorShowing the 15 most recent of 30 sources. Enable JavaScript to search and browse every indexed mention.