Supporting other page editors in the popup

[jakemgold]

On sites built with a page builder, the popup's Edit button points to the standard WordPress editor, but the builder's own edit link is usually what people actually use (see #87). The admin bar handles this by offering both, and I think the popup should too: keep the standard Edit, and add the site's page editor as a second edit action when we recognize one.

Early thinking on how this stays fair and useful:

• Recognition is based on simple public criteria, not on which tools maintainers happen to use. Any page editor with meaningful usage and a recognizable edit link should qualify.
• The list of recognized editors lives in the open in this repo, and anyone can propose additions here.
• Scope stays limited to page editors, alongside existing developer tooling like Query Monitor. The popup is deliberately not a mirror of the admin bar; turning the admin bar on per site remains the way to get the full toolkit.

If you'd like an editor supported, comment with its name and what its edit link looks like from a page you're viewing (an example URL with the site name redacted is perfect).

Bug fixes are the current priority, so I see this as a future feature release. Feedback on the overall approach is very welcome, this is early thinking.

[itzmekhokan]

@jakemgold Approach looks right — reading the editor's link off the admin bar beats synthesizing one. Every editor I checked already gates its own node on capability (Beaver is_post_editable, Elementor is_editable_by_current_user, Visual Composer canEdit, SiteOrigin edit_post), so node presence is the permission check, and a stale id just means no row instead of a broken link.

One thing worth settling first: are we comfortable naming commercial products in the UI? Open criteria answer "why these and not others?", not "why is WordPress naming paid plugins at all?" Two ways to lower the stakes:

• Ship node ids, not names. Render the label the site's own admin bar provides — repo carries only DOM ids, and it respects Beaver's get_branding() white-labelling. Caveat: label quality varies (Elementor "Edit with Elementor" is fine, Breakdance gives "Open 'Hello world!'", Beaver's title is HTML).
• Require a plugin-directory listing. Objective and project-owned. Cost: drops Divi, WPBakery, Bricks, Oxygen, Breakdance.

Two gotchas regardless of direction:

• Elementor builds its node in JS, so anything parsing fetched or cached HTML won't see it — live DOM read only.
• Breakdance points at get_edit_post_link() for posts outside its own mode, which duplicates the standard Edit row. Worth de-duplicating.

Node ids I could verify, minus the wp-admin-bar- prefix:

Editor	Node id	Source
Elementor	elementor_edit_page	modules/admin-bar/module.php
Divi	et-use-visual-builder	rendered markup
Beaver Builder	fl-builder-frontend-edit-link	classes/class-fl-builder.php
WPBakery	vc_inline-admin-bar-link	rendered markup
Visual Composer	edit-with-visual-composer	Modules/Editors/EditPostLinks/Controller.php
Breakdance	edit_with_breakdance	plugin/admin/admin_bar_menu.php
Brizy	brizy_Edit_page_link	public/main.php
SiteOrigin Page Builder	so_live_editor	siteorigin-panels.php

Divi and WPBakery came from rendered markup rather than vendor source, so they're likeliest to have drifted. Nothing public for Bricks or Oxygen, so I left them out.

Happy to put a branch behind whichever direction you pick.