/04-MW

Chapter 4 - Understanding the MediaWiki Philosophy

Byline: Understanding the MediaWiki concepts used by Abhiprayavedi before administering the platform.

4.1 Purpose

Before administering Abhiprayavedi, it is important to understand the MediaWiki concepts upon which the platform is built.

This chapter is not intended to be a comprehensive introduction to MediaWiki. Instead, it explains only those concepts that are necessary to understand, maintain, and develop the Abhiprayavedi implementation.

The emphasis throughout this chapter is on MediaWiki as implemented in Abhiprayavedi.

4.2 Seeing the Whole Platform

When you first open Abhiprayavedi, you see a complete publishing platform rather than an ordinary wiki.

Readers encounter published articles.

Editors create and review content through structured editorial workflows.

Administrators manage users, templates, forms, categories, system configuration, and platform maintenance.

Although these activities appear different, they are all supported by a common MediaWiki foundation.

Understanding this foundation helps administrators appreciate how the various components work together as a single publishing system.

4.3 Why MediaWiki?

MediaWiki is a mature, open-source content management platform originally developed for collaborative knowledge publishing.

Abhiprayavedi adopts MediaWiki because it provides:* Reliable page management.

• Complete revision history.
• Collaborative editing.
• Flexible templates.
• Structured categorisation.
• Extensible architecture.
• Strong user and permission management.
• Long-term sustainability supported by a large international community.

Rather than modifying the MediaWiki core, Abhiprayavedi extends its capabilities through configuration, templates, extensions, forms, and custom styling. This approach simplifies maintenance and future upgrades.

4.4 Understanding Pages

Everything in MediaWiki is stored as a page.

An article is a page.

A template is a page.

A category description is a page.

A form is a page.

Even system messages are pages.

Each page maintains its own revision history, allowing previous versions to be viewed or restored whenever necessary.

For an administrator, understanding that almost every component of the platform is represented by a page is one of the most important MediaWiki concepts.

4.5 Editing Pages

MediaWiki supports several methods of editing pages.

Within Abhiprayavedi, administrators may encounter:* Source editing using wiki markup.

• Visual editing where available.
• Structured editing through Page Forms.

Published articles are normally created and maintained through the editorial workflow rather than by unrestricted direct editing.

Whenever changes are made, administrators should preview the results carefully before saving them and should provide meaningful edit summaries describing significant modifications.

In Abhiprayavedi…

Editing is not merely the modification of pages. It forms part of a structured editorial workflow designed to preserve consistency and publication quality.

4.6 Moving Pages

Occasionally a page title requires correction.

MediaWiki provides the Move function for this purpose.

Moving a page preserves:* Revision history.

• Author attribution.
• Internal references.
• Redirects from the previous title.

Administrators should avoid copying the contents of one page into another simply to change its title.

Administrator Note

Always rename pages using Move rather than creating a new page manually. This preserves the integrity and history of the content.

4.7 Deleting, Restoring and Protecting Pages

Administrators are responsible for removing obsolete or inappropriate pages when necessary.

Deleted pages remain recoverable until permanently removed by system-level maintenance.

Important pages may also be protected to prevent accidental or unauthorised modification.

Deletion should always be undertaken cautiously and, wherever appropriate, documented.

4.8 Understanding Namespaces

MediaWiki organises pages into namespaces according to their purpose.

Within Abhiprayavedi, administrators will commonly encounter:* Main — published articles and general content.

• Draft — articles under preparation.
• Template — reusable presentation components.
• Form — structured editorial forms.
• Category — organisational pages.
• File — uploaded images and documents.
• MediaWiki — system interface pages.
• Private — restricted internal material.
• Submissions — editorial submissions awaiting processing.

Namespaces help separate different types of information while allowing them to work together as a unified platform.

4.9 Templates

Templates are reusable pages that provide a consistent presentation for articles and other content.

Rather than repeating the same layout many times, multiple pages can share a common template.

In Abhiprayavedi, templates play a central role in implementing the publishing architecture.

Administrators should therefore understand that changes to core templates may affect many pages simultaneously.

Detailed template administration is covered in a later chapter.

4.10 Categories

Categories organise related content and help readers discover articles on similar subjects.

They also support several automated features used throughout Abhiprayavedi.

Maintaining an accurate category structure is therefore important for both navigation and platform organisation.

Category administration is discussed in detail later in this manual.

4.11 Files and Images

MediaWiki stores uploaded media within the File namespace.

In Abhiprayavedi, images contribute significantly to article presentation.

Administrators should ensure that uploaded files are appropriately named, organised, and maintained in accordance with the platform's editorial practices.

4.12 Magic Words and Parser Functions

MediaWiki provides special keywords known as magic words together with parser functions that introduce dynamic behaviour into pages and templates.

Abhiprayavedi uses a carefully selected set of these features within templates and presentation components.

Administrators may occasionally encounter examples such as:* DISPLAYTITLE

• DEFAULTSORT
• PAGENAME
• FULLPAGENAME

and parser functions including:* #if

• #ifeq
• #switch
• #ifexist

A detailed understanding is unnecessary at this stage. Their purpose is simply to allow pages and templates to respond intelligently to different situations.

4.13 Special Pages and Administrative Tools

MediaWiki provides numerous built-in administrative tools through Special Pages.

Examples include:* Recent Changes

• User Management
• Page History
• Logs
• Uploads
• Wanted Pages
• Maintenance Reports

These tools assist administrators in monitoring platform activity and maintaining system health.

4.14 Working with the Platform

One of the strengths of MediaWiki is that it encourages administrators to extend the platform through configuration rather than modification.

Accordingly, administrators should:* Prefer native MediaWiki capabilities whenever practical.

• Use templates rather than duplicating layouts.
• Use extensions rather than altering the MediaWiki core.
• Preserve revision history.
• Test significant changes before deployment.
• Document important administrative decisions.

These practices contribute directly to the long-term maintainability of the platform.

4.15 MediaWiki in Abhiprayavedi

Although Abhiprayavedi is built upon MediaWiki, it is not intended to function as a conventional open-editing wiki.

MediaWiki provides the underlying technology, while Abhiprayavedi applies structured editorial workflows, carefully designed templates, custom forms, presentation standards, and administrative procedures to create a professional publishing environment.

Understanding this distinction is fundamental to successful administration.

Administrators should therefore regard MediaWiki not as the final product, but as the foundation upon which the Abhiprayavedi publishing platform has been carefully constructed.

4.16 Concluding Remarks

This chapter has introduced the MediaWiki concepts required to understand the Abhiprayavedi implementation.

Subsequent chapters build upon this foundation by examining the platform's architecture, configuration, administration, and maintenance in progressively greater detail.

Throughout this manual, MediaWiki concepts will be revisited whenever necessary so that understanding develops naturally as the administrator's responsibilities expand.