Remote Templates Management System

Feature Requests / Improvements
1

Alright, another thought on remote templates here. Adding multiple remote templates to a client website is great, but what if we want to give client websites access to different templates, but not all?

Example:

Say I have:

  • wire frame remote templates
  • remote templates for my custom theme “Avery”
  • remote templates for my custom theme “Benton”
  • remote templates for my custom theme “Charlie”
  • remote templates of hero sections only
  • remote templates of cards only
  • etc

I may not want to provide access to every single remote template to my client. For example, perhaps my wireframe templates are only to be used by myself when first building a client website, and then access is later removed. Perhaps my custom theme templates are only used by way of example when initially sitting down with a client. However, I might want some of my remote templates to remain accessible at all times. Perhaps I want to provide access to both my hero section and card templates.

In this case, we would need to group remote templates into categories or tags, toggle each category or tag as publicly available (query-able by another Bricks website), and then assign a unique password to each category or tag.

Does that sound like something the Bricks team might implement one of these days?

2

use the hook ‘bricks/get_remote_templates_data’ to filter your remote templates, or access the browser IndexedDB → BricksDB → templates, update the DB with js.

add_filter( 'bricks/get_remote_templates_data', function( $remote_templates ) {
    error_log(print_r($remote_templates, true));

    return $remote_templates;
} );