MediaWiki Application Rationalizations

Application Rationalization is a managerial term used to describe the process of transforming an organization from one that maintains an ad-hoc software portfolio to one that does so based on a set of published rules or rationales. The goal is for the organization to avoid obtaining and maintain multiple software applications that do the same things.

So.. How do you justify the use of MediaWiki to your management? Application Rationalization provided by User:Revansx "A fully-featured MediaWiki site is uniquely suited for organizations and projects to digitally transform their internal processes and automate the management of their knowledge and records by providing an in-house 'Single Source of Truth' (SSOT) environment for applying a 'Model Based System Engineering' (MBSE) approach to developing electronic processes which generates all artifacts (records and knowledge) as in-page data; and enables the tracking and monitoring of any process metrics the organization seeks to optimize."

Scientific purposes
I've focused on these arguments, which occasionally get traction. These are things that MediaWiki is particularly good at compared to, say, Sharepoint or Confluence. They are relevant to knowledge management of scientific work. -- Econterms (talk) 18:43, 12 January 2023 (UTC)

For a reference encyclopedia of scientific work we want/need to have:
 * Footnotes (to ground our work/findings in previous work which we don't need to read in detail)
 * Categories (for searching within topics and concepts, not for a known string -- thus it helps knowledge management)
 * Equations in a standard (TeX) format -- to encourage precise argumentation
 * Redirects (for alternative names/spellings/languages and to connect field-specific lingo across fields)
 * Interwiki links (if one can get people to understand the importance of integrating into the Wikimedia ecosystem including Wikidata, and Commons)