Create Reusable Link, Button, and URL Tokens in QCDR

QCDR provides Pro-tier structured output for reusable links, Joomla-style buttons, and URL values. The same builder can use a direct destination or a Joomla frontend menu item and can centralize displayed text, target window, CSS class, and accessibility/title text.

Choose Link or button when you want an anchor element in normal content. Choose URL link when the reusable value may also need to act as a URL/attribute-safe destination in a compatible Rule context.

Choose the Destination

  1. Create or edit a Token.
  2. Choose Link or button or URL link for Output type.
  3. Under Destination type, select Enter a URL or Select a Joomla menu item.
  4. For a URL, enter a supported web URL, site-relative path, mailto:, tel:, fragment, query-style destination, or a QCDR Token that resolves to the destination.
  5. For a Joomla menu item, choose the frontend menu item from the picker. QCDR stores its item ID rather than hard-coding the visible menu title.

Unsafe executable schemes such as javascript:, vbscript:, and data: are rejected.

Set the Visitor-Facing Link

Enter Displayed text; it may be plain text or include a QCDR Token dependency. Choose whether the link opens In the same window or In a new window. New-window output includes rel="noopener noreferrer".

Normal Link vs. Joomla Button

Normal link emits a standard anchor. Joomla button adds the standard btn btn-primary classes plus any optional class you provide, and marks the anchor with button role semantics. Use a custom CSS class only when your template/site stylesheet knows what that class should do.

Advanced Link Options

The optional CSS class field is normalized to safe class-name characters. Title / accessibility label is emitted as both the link title and aria-label. These fields, along with URL and displayed text, can participate in structured Token dependency resolution when you intentionally build one reusable value from another.

Understand URL Link Output

A URL Token can return only the destination when QCDR consumes it in a URL/attribute target. When the same Token is rendered directly in ordinary content, QCDR produces the configured link output. This lets one structured URL configuration work in both appropriate contexts without exposing unsafe schemes.

Verify Before Enabling

Test the actual click destination, same/new-window behavior, visible text, button styling, and accessibility label. If the destination or displayed text depends on another Token, test both the qualifying and non-qualifying context so a missing dependency does not surprise you in production.

Community Discussion

Want to compare workflows, share practical tips, or discuss how you use this QCDR feature? Visit the QC Dynamic Replacer Community. For private support, bug reports, account-specific issues, or feature requests, use the QuantaCade support system.