I saw the plugin by @thguenther for links and had ideas for improvements. So I decided to fork it and experiment. I ended up creating a completely different plugin and I think it’s an improvement. It has better UX, more options, and more functionality in the templates. Here’s a demo:
- Native Kirby fields used for pages, files, url, email (with
mailto:), and tel (with
- When used in a structure, you get nice previews; for links to a page or file, the native file/page preview is shown
- Specify link text inside the field itself, you don’t need a separate field just for it
- Toggle whether the link opens in a new tab
- Specify a fragment (hash) for the link
- In the blueprint, you can specify possible link types and settings. For example, if you specify
pageas the only link type and set
settings:false, the field would look just like a pages field, which simplifies the UX.
You also get a bunch of methods for rendering the link in the template. First, you convert the link to a Link instance via
$link = $field->toLink(), similar to what you would to for a pages or files field with
Then, you can render it like this:
<a <?= $link->attr()?> class="my link"> <?= $link->title() ?> </a>
…which would add
target and any other attributes accordingly. Internally, it uses Kirby’s
Html class to render the link.
My favorite part is that you can also just do:
<?= $link->tag() ?>
…and you’d get a full
<a> tag with the correct href, target, and any text you’ve specified.
I’ve used in a couple of projects so far and I’ve had no issues with it.
Check it here:
Feedback would be much appreciated!