Best practice editable link/button?

Hi Justin,

I think Brenden Kehren's answer to a similar question, linked below, is a must-read for everyone. It recommends using fields of a custom page type instead of a web part.

https://devnet.kentico.com/questions/webparts-vs-widgets-vs-static-html

This technique even works if you need to allow authors to add 0 to many sections of content on a page. I elaborated on this technique in a recent user group. The slidedeck is here:

https://www.slideshare.net/mikewills/kentico-content-architecture-the-inaugural-seattle-kentico-users-group-may-2017

If you were using this technique, the editable web parts would be fields within your page type instead of web parts on a template. You could provide a field with a "URL Selector" control as well.

Mike

My approach is the inline widget. There is a link button web part as you said, but you can create a customize widget based on the link/button web part. No programming involved. For customization I want editors to select links from a specific subset and I want the to use predefined styles etc. I've changed the default control to drop down which I populated with a query:

If a form control for a field in your document is Rich Text Editor(CK Editor), i.e. you can edit text as HTML in the form tab and you have ability to insert inline widgets:

I use this feature to let editors to insert buttons (Call to Action) they can pick and customize them based on predefined values, i.e. links, CSS etc.

If you want to style the link or button a specific way (say to match your website's theme), keep in mind the Transformable WebPart on the marketplace allows you to create structured webparts easily, which then you can turn into a Widget and do inline.