Prerequisites

For bookmarklets there are no prerequisites.

For userscripts a userscript manager like Grease Monkey or Tampermonkey must be installed to the browser. The userscript manager builds the context in which the script is executed.

Common Approach

The common approach to both solutions is that a JavaScript is run in the browser that matches HTML elements and alters them to be hidden. Therefore all elements are rendered as normal and then are hidden by the script.

Note that this use case is not properly supported the bookmarklet. A user will probably not run the bookmarklet manually when using the autocomplete function to select a macro.

Bookmarklet Solution

The bookmarklet solution is easily installed as a bookmark in a browser. The advantage is that no additional tools are required. The disadvantage is that the user needs to open the bookmarklet to remove the elements from the page manually each time.

This solution may be appropriate in case the user only occasionally wants to remove the element.

if (AJS) {
  AJS.toInit(function () {
    function hideElements($element) {
      if ($element) {
        $element.css("display", "none");
      }
    }

    function hideSpaceBlueprints() {
      const $templateElements = AJS.$('#create-dialog .templates .template[data-blueprint-module-complete-key*="projectdoc"][data-create-result="space"]');
      hideElements($templateElements);
    }
    function hidePageBlueprints() {
      const $templateElements = AJS.$('#create-dialog .templates .template[data-blueprint-module-complete-key*="projectdoc"]:not([data-create-result="space"])');
      hideElements($templateElements);
    }
    function hideMacros() {
      const $macroElements = AJS.$('#select-macro-page .dialog-page-body .macro-list-item[id*="projectdoc"]');
      hideElements($macroElements);
    }
    function hideAutocompleteMacros() {
      const $macroElements = AJS.$('li>a[class*="autocomplete-macro-projectdoc"]');
      if ($macroElements) {
        $macroElements.parent().css("display", "none");
      }
    }

    hideSpaceBlueprints();
    hidePageBlueprints();
    hideMacros();
    hideAutocompleteMacros();
  });
}

For more information on the bookmarklet, please visit Hide projectdoc Tools.

Userscript Solution

The userscript can be configured to be automatically executed on every page whose URL matches a regular expression. This way a user may select the script to remove element only on certain spaces, while leave them untouched on others.

A userscript is a JavaScript script with some metadata. It may also use services provided by the userscript manager context.

The following screenshot shows the script installed with Tampermonkey.

You may want to edit the script and adjust the match URL to your Confluence server.

// @match        https://*/confluence/*

The browser plugin may also take care of automatically update the scripts. The source of the script could be hosted in a controlled environment. We recommend to copy the script to your server and alter it to meet your specific requirements.

For more information on the userscript, please visit Hide projectdoc Tools.

Deactivation of Blueprints

As mentioned in the introduction, blueprints can be deactivated in your Confluence instance.

This short example walks you through the steps to deactivate the projectdoc Blank Document Doctype. This doctype is a meant as a simple starter for new users. Once the team uses the Core Doctypes or has designed their own doctypes, this doctype is no longer needed.

1. As an admin, go to Manage apps
2. Select the app that contains the blueprint you want to deactivate
   
3. Open the list of modules by clicking on the plus sign
    
4. Deactivate the following modules for each doctype: The doctype template, the home and index page template, the blueprint and the wizard module.
   

For information on how to control blueprints on space level, please refer to the tip Overwhelmed with Blueprints?.

Resources