Today, users find the configuration by reading inside implementations. An entry point on the NLG Function's page removes that search.

Users often arrive from an abstract article, which calls an HTML NLG Function that wraps the dispatching one, so the entry point must also work from the wrapping Function and take the user to the right dispatching Function. If the language already has a language-specific Function, the entry point says so and links to it, so the user does not make a duplicate.

The entry point has a documented, stable URL, with the NLG Function and the language as parameters. This lets the community add their own calls to action, for example in the documentation of wrapping Functions, without asking us for a new feature.

Acceptance criteria

• The entry point shows on the pages of both "defining role sentence (HTML)" (Z37011) and "defining role sentence (monolingual)" (Z28016), and both lead to the same dispatching Function.
• For a language that already has a language-specific Function, the entry point links to that Function and does not offer to create a new one.
• The URL pattern is documented on Wikifunctions, and a link that follows it opens the flow with the NLG Function and the language already selected.