CMS with the makings of a Wiki?

Question

CMS

The site will use essentially a standard set of functions:
Registration / Authorization
The ability to comment on the material by the visitor.
Likes , etc.
The administrator will fill the site.
I do not see it appropriate to use a full-fledged Wiki engine for this.
What do you need from the Wiki?
Let's say the site is a collection of salad recipes.
The salad consists of such ingredients as: cabbage, carrots, peas, etc.
You need the ability to highlight the right words with links. For example carrots. So that when you click on a carrot, a page with a description of the carrot plant opens.
and so on the entire site, you need to be able to highlight the words with links.
In a regular CMS, I can manually link to the "carrot" page in the right places... but one BUT! let's say if the carrot page url changes, all links will become broken and you will need to manually edit them.
As far as I know, there is no such problem in wiki engines.

Answer 1

In a regular CMS, I can manually link to the "carrot" page in the right places... but one BUT! let's say if the carrot page url changes, all links will become broken and you will need to manually edit them.

In CMS MODx, for each new page, an identifier is created in the form of a number. Instead of a direct link, you can specify the very ID of the page to which you want to link:
in this case, you can change the url of the page at least as many times as you like, the link will always work correctly. Maybe wordpress also has such an option, but I don't know for sure.

Answer 2

Is there multilingualism? how many subdomains?
In order for the links not to be broken, it is necessary that the pages be in the form of updated directories. Here you can most likely use Wordpress. but with a very good news plugin. Or a suitable blog plugin. You won't find a suitable cms by default
Do not use a specific cms. it will be problematic to find a plugin or specialists for it

Answer 3

Look for a good cross-link plugin and start from there when choosing a CMS.
Or write your own plugin/extension for the CMS you need.
PS: it's better - write it down in the FT list, and then draw up a detailed TOR in order to foresee everything at the design stage and not forget anything.