Posts Bridge – Remote CMS

Lýsing

Bridge your posts collections with your backend over HTTP APIs, enabling remote and automated web content management.

How it works

Posts Bridge treats post collections as indexes that represents your backend data and allow you to use Gutenberg, WordPress’ powerful page builder, as the frontend editor of your backend. Whether through manual or automatic synchronization —using ahead-of-time or live fetches— Posts Bridge fully integrates your backend data into the WordPress CMS system.

Bridges

Think of a bridge as a mapping that bounds your backend data with a post type collection on your WordPress web page. Each item on your backend database can be converted to a post, and each field on your backend tables can be mapped to a post field or taxonomy. Once a bridge is configured, you can trigger manual synchronizations, or let Posts Bridge automatically synchronize content between the two sides on the background.

Addons

Posts Bridge comes with free addons. Each addon adds to the plugin new bridges to work with specific APIs and bridge templates.

Posts Bridge has the following addons:

Backends

In Posts Bridge, a backend is a set of configurations that handles the information required to get your posts synchronized over HTTP requests with remote systems.

To register a new backend you only have to set 3 fields:

  1. A unique name for the new connection
  2. The URL of your backend
  3. An array of HTTP headers with connection metadata and credentials
  4. Optional, an HTTP authentication credential (Basic, Bearer, etc)

Once registered, you can reuse your backend connection on your post bridges.

Remote Mappers

Remote mappers allow you to mutate your backend’s API responses to match the WordPress post model (e.g., post_title, post_content, post_name). This enable automatic conversion of backend data into WordPress posts on each synchronization loop (ahead-of-time).

With mappers you can map backend data to post fields, custom fields and into taxonomy terms (such as categories and tags).

Remote Field

If you want your backend data loaded dynamically on each render, you can use the Remote Field custom block. This block lets you designate parts of your post templates as remote content. On render time, this blocks will be replaced with the data fetched from the backend.

Templates

To streamline the bridge setup process, Posts Bridge comes packed with templates. Templates are blueprints of bridges you can use to set up your integrations in a matter of minutes.

Docs

Browse the plugin’s documentation on postsbridge.codeccoop.org.

Links

Skjámyndir

  • Settings page
  • Backends
  • Bridges
  • Template Wizard
  • Debug console

Blocks

This plugin provides 1 block.

  • Remote Fields Remote fields custom block that replace marks by its remote value on the render.

Umsagnir

There are no reviews for this plugin.

Þátttakendur & höfundar

“Posts Bridge – Remote CMS&#8221 er opinn hugbúnaður. Eftirfarandi aðilar hafa lagt sitt af mörkum við smíði þessarar viðbótar.

Höfundar

Breytingarsaga

4.0.0

  • feat: schemas refactor
  • feat: frontend refactor
  • feat: improve custom post types ui
  • feat: sync ping poll
  • feat: remove templates
  • feat: remove gsheets addon
  • feat: bridge enabled state
  • feat: update deps

3.0.8

  • feat: setting sanitization with defaults recovery
  • feat: add wp rest mirror template
  • feat: wp rest reuse authorization if exists

3.0.7

  • feat: addons mount method
  • feat: improve debug console outputs
  • fix: exclude loco files from git