It sounds like this would be desirable for all 3rd party wikibases.
If so, this should just be changed in the text strings in wikibase itself.

@Evelien_WMDE the strings that contain the content mentioned are localized for all available languages. Not sure if this is in scope for cloud or should rather happen in Wikibase itself (as already suggested)?

@Fring Yeah Andrew brought this up as well, so he can advise a bit better. But, the requirements in the AC shouldn't affect this: Simply removing the text in AC point 3 doesn't require any translations and as for the links, those pages can be translated so also shouldn't pose a problem.

All of the content that shall be changed is to be found in the l10n strings:

• wikibase-newitem-summary
• wikibase-newproperty-summary
• wikibase-newlexeme-summary
• wikibase-shortcopyrightwarning

The hrefs themselves are defined in:

• wikibase-label-helppage
• wikibase-description-helppage

The best approach to implement the change heavily depends on how we want to tackle the localization issue.

Simply removing the text in AC point 3 doesn't require any translations and as for the links, those pages can be translated so also shouldn't pose a problem.

This could be done for English, but I personally would fail to do this in Dutch and probably ever other language we support. Does this mean, the ACs are only about the English locale?

Your best bet here is probably following the pattern of the `WikimediaMessages" extension
https://www.mediawiki.org/wiki/Extension:WikimediaMessages
This contains customized messages string for WMF production sites in comparison to default mediawiki and extensions..

You can then get up to date translations for all languages for your custom strings
https://translatewiki.net/wiki/Translating:New_project/en

I believe this is easiest set up on gerrit, but I have seen this happening on Github too, but probably best to just reach out to the translate wiki team

Though another thought with a wikibase perspective here would be that there should work for any wikibase out of the box and make sense, not being red links :)

The best way to move forward with this would be:

• Do the change in the Wikibase extension as this is a. easier and b. valuable for Suite users as well
• Add a new translation string that contains the desired copy changes
• Add a setting in the extension that decides whether the current behavior (default) is used or if the new string is used
• Have the new string localized in the default workflow
• Backport the changes to Wikibase.cloud (or upgrade)

@Fring We have Jon's blessing to go ahead

Add a setting in the extension that decides whether the current behavior (default) is used or if the new string is used

Not sure if this is actually needed. At least some of the existing messages are overridden on Wikidata anyway, see for example: https://www.wikidata.org/wiki/Special:NewItem: there the (wikibase-newitem-summary) message has a local override at https://www.wikidata.org/wiki/MediaWiki:Wikibase-newitem-summary.
So, if you want, we could see what your proposed new copy for the messages is, and probably some or all can be changed directly in the respective en.json, maybe reducing the need for extra logic.
Hopefully that simplifies things :)

Implementation split into T342000 and T342001