Frammenti di testo/markdown inseribili e gestiti centralmente

[merefield (Robert)]

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!:

[Johani (Joe)]

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:

and clicking the button would add

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

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

and the end result looks like this

and you can use

[data-theme="disclaimer"] {

}

in CSS to style it however you like.

[merefield (Robert)]

That’s awesome! Thanks @Johani

Added to Tips’n’Tricks.

[pacharanero (Marcus Baw)]

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

[merefield (Robert)]

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

[Luke_Cousins]

Anche il suggerimento di @pacharanero sarebbe fantastico per noi. Nel nostro caso, sarebbero solo per il personale, quindi non vorremmo che nulla venisse mostrato nella barra degli strumenti dell’editor, ma inserire un breve codice per inserire il blocco di aggiornamento automatico sarebbe fantastico

[pacharanero (Marcus Baw)]

Per ora, un modo non-Discourse e non gestito centralmente per ottenere questo comportamento oggi è utilizzare un gestore di appunti multipiattaforma come CopyQ e impostare la sezione ‘Comandi/Scorciatoie globali’ in modo da poter inserire testo arbitrario negli appunti.

Questi snippet possono quindi essere gestiti nell’interfaccia utente di CopyQ, assegnati a un tasto di scelta rapida o apparire nel menu contestuale di CopyQ. Non è bello come un plugin integrato in Discourse, ma ha il vantaggio di funzionare su tutte le applicazioni, ed esiste già!

(Nota che questo dovrebbe essere configurato su ciascuno dei computer che si desidera utilizzare in questo modo. È possibile esportare e importare questi comandi e scorciatoie globali su file, per consentire la configurazione delle stesse impostazioni su più macchine o in un team)

[pacharanero (Marcus Baw)]

@merefield

Andrebbe bene se il testo apparisse solo nell’anteprima e nella visualizzazione finale elaborata?

Andrebbe benissimo per me. Penso che, a differenza di DiscoTOC e Placeholders, dovrebbe essere correttamente renderizzato nel riquadro di anteprima, ma nell’editor potrebbe semplicemente mostrare qualsiasi frase di attivazione :slug: fosse stata scelta.

[Luke_Cousins]

Grazie per la risposta. La soluzione CopyQ non fa quello che sto cercando (almeno, non credo).\n\nAd esempio, vorrei inserire uno snippet in un post (ad esempio, :slug:) e poi, ogni volta che questo viene renderizzato, renderizza il contenuto corrente per questo slug (che potrebbe contenere markdown). Se cambio il contenuto di questo slug, tutti i post che lo utilizzano verrebbero immediatamente aggiornati per avere il nuovo contenuto (il post stesso contiene solo lo slug e il contenuto viene inserito al momento del rendering).\n\nMi andrebbe bene anche se la ricerca non conoscesse l’esistenza del contenuto (e mostrare solo la versione finale elaborata va bene per me).\n\nSaluti

[denvergeeks]

Ecco un approccio diverso…

Composer Help Button

I’ve now completed my work on a composer help button. It adds a button to the composer window [image] and a setting in the Admin area: [image] Clicking on that icon, will open a modal window with the content from the first post at the URL set in the Admin area [image] The only caveat, is that you need to store the Topic in a publicly accessible location so ALL of your members can see it. Otherwise, they’ll get an access denied error.

GitHub - cpradio/discourse-plugin-composer-help-button: Add a Help Button to the Composer Window in...