Insertable, centrally maintained text/markdown snippets

Community wiki Developers
1

I was wondering if there was any way I could define a string of text in a single place and insert it within posts with a single, short reference.

It’s a bit like the out of the box Admin -> Customize -> Text Content, but for my own custom variables that can be inserted into posts.

My use case was adding a disclaimer for my affiliate links. As the number of affiliate links grew across many posts and Topics I noted that my disclaimers were proliferating along with them. I occasionally like to make improvements to the disclaimers and this gets more onerous as the number grows.

I’m also considering making my affiliate links more generic so I have one centrally managed link for each product link, for example, which appears multiple times. If that product link changes, I only have to change it in one place.

Obviously I might be able to do some kind of rails find & replace, but that’s not as clean/safe nor ‘online’.

So I wanted a place to define & maintain a text string in a single place and have changes immediately reflected everywhere that is used on next page view.

Read on for @Johani’s solution!:

3 Likes
2

One possible option is to use a theme component.

This goes in header.html

<script type="text/discourse-plugin" version="0.8">
var disclaimer = settings.Disclaimer_text,
  disclaimer_selector = 'div[data-theme="disclaimer"]';

$.fn.disclaimer = function() {
  if (!this.length) {
    return;
  } else {
    this.each(function() {
      $(this).html(disclaimer);
    });
    return this;
  }
};

api.decorateCooked($elem => $elem.children(disclaimer_selector).disclaimer());

// create composer button
let currentLocale = I18n.currentLocale();

I18n.translations[currentLocale].js.disclaimer_button = "Add disclaimer";
I18n.translations[currentLocale].js.composer.disclaimer_prompt = ""; // leave empty

api.onToolbarCreate(function(toolbar) {
  toolbar.addButton({
    trimLeading: true,
    id: "disclaimer-button",
    group: "insertions",
    icon: "exclamation-circle", // change icon
    title: "disclaimer_button",
    perform: function(e) {
      return e.applySurround(
        '<div data-theme="disclaimer">',
        "</div>",
        "disclaimer_prompt"
      );
    }
  });
});
</script>

and this goes into your component’s settings.yml file

Disclaimer_text:
  default: "Lorem ipsum dolor sit amet, ei purto complectitur has, per at quas senserit. Et malis libris eos, vix id pericula dissentiet, aliquid apeirian pro eu. Sed ex viderer inciderint, vitae officiis dissentiet eos no. Omnes percipit singulis in has, ne nam nibh tation inciderint. Quas nulla ei sit, ex eam rebum voluptaria. Id eam altera similique. Ex justo assentior persequeris mea, ei hinc paulo ubique mei. <br><br>Cu nam epicurei torquatos, et accusam accommodare vim. Vis sint saperet officiis et. Ad consequat posidonium mea, et duo paulo quidam maluisset, vel an electram expetendis. An vis repudiare tincidunt, mentitum convenire eloquentiam ut vis, summo partiendo pro ad."
  description:
    en: Enter desired disclaimer text. Use &lt;br&gt; for linebreaks.

You would then have a button in the composer that looks like so:

1
1906×1002 20.9 KB

and clicking the button would add

<div data-theme="disclaimer"></div>

which get’s converted to whatever you set in the component’s settings

1
1980×191 10.2 KB

and the end result looks like this

1
11788×556 55.5 KB

and you can use

[data-theme="disclaimer"] {

}

in CSS to style it however you like.

20 Likes
3

That’s awesome! Thanks @Johani

Added to Tips’n’Tricks.

2 Likes
4

Hi @merefield - funnily enough I was looking for similar functionality - inserting a standard snippet of text - but rather than a button I wanted a trigger string that would expand out to a piece of markdown. (OK, I suppose alternatively I could modify the button to a dropdown with a few options)

This is probably not a core Discourse feature but a plugin.

Ideal behaviour:

  • I type :stub: (I don’t mind about using something instead of the delimiting : characters, but wondered if hooking into the emoji interface might work since that has the kind of ‘completion’ type behaviour that I’d like)

  • Discourse replaces :stub: with

    > This article is a stub - please improve it by  **editing**  and  **adding links**  and  **detail**  (it’s a ‘wiki’ so any user can edit and add information) or by  **commenting**  below.

  • which is rendered as

    This article is a stub - please improve it by editing and adding links and detail (it’s a ‘wiki’ so any user can edit and add information) or by commenting below

  • and there should be somewhere in the UI to configure these snippets, a bit like the Custom Emoji interface

5 Likes
5

Great idea for a plugin! Would you be ok for the text to appear only in the preview and the final cooked view?

4 Likes
6

The suggestion from @pacharanero would be fantastic for us too. In our case, they would be for staff only, so we wouldn’t want anything shown in the editor toolbar, but entering a short code to insert the auto-updating block would be amazing :+1:

1 Like
7

For now, a non-Discourse, non-cetnrally managed way of achieving this behaviour today is to use a cross-platform clipboard manager like CopyQ and set up the ‘Commands/Global Shortcuts’ section so that you can insert arbitrary text into the clipboard.

These snippets can then be managed either in the CopyQ UI, assigned to a hotkey, or appear in the right-click CopyQ menu. It’s not quite as nice as a Discourse-embedded plugin, but then it has the advantage of working across all applications, and it already exists!

(Note that this would have to be set up on each of the computers you would want to use in this way. You can export and import these commands and global shortcuts to file, to enable setting up the same settings on multiple machines or across a team)

8

That would be absolutely fine with me. I think that unlike DiscoTOC and Placeholders it would need to be properly rendered in the preview pane, but in the composer it could simply show whatever :slug: trigger phrase was chosen.

9

Thanks for the response. The CopyQ solution doesn’t do what I’m looking for (I don’t think, at least).

For example, I’d like to enter a snippet in a post (e.g. :slug:) and then whenever this is rendered, it renders the current content for this slug (which might contain markdown). If I change the content of this slug, then all posts using this would be immediately updated to have the new content (the post itself contains the slug only and the content is switched in upon render).

I’d be fine with the search not knowing the content exists too (and only showing the final cooked version is good for me).

Cheers

10

Here’s a different approach…

1 Like