Drupal8 Port

I would consider the individual links (alinks) as content and not as a configuration. The automatic links interact with content (nodes) and e.g. the editor would add some new "alinks" for its new article. But if this is a configuration entity and the drupal instance is controlled via version control, this generates some overhead.

So I think for the module settings (/admin/config/content/alinks) it makes sense that this is a config entity. But for the alinks itself, it should be better a content entity.

I'm just thinking if there are reasonable scenarios to move the patterns through various environments. In my use case would generate a better internal linking between article/sites. So I react on content and link to content.

The fundamental decision is to consider whether an entity rather is configuration or content. I would rather tend to the "it's content" direction, since the entities rather work with content / based on it. And yes, sometimes the decision is really hard, because some "entities" are more likely between.

--

Unfortunately, I don't have used your module in Drupal 7. Therefore, I do not know how it worked there. If you have good reasons to use config entities for that, then it is a understandable decision. I only wanted to contribute another consideration.

+1 on Content Entity, this provides the ability to store more metadata to a single link.

Here is an alinks solution built on content entities https://github.com/BurdaMagazinOrg/alinks

It's not ready and full featured but it works fine so far.

I want to add the ability to use taxonomy terms as keywords to.

Big thanks to @webflo for the initial work.

Here is a patch on base of current 8.x-1.x-dev

Here i opened a PR https://github.com/Greg-Boggs/alinks/pull/4

Thanks Greg for bringing this to d.o.