Jump to content

Wiki@IndraStra:Manual of Style

From Wiki@IndraStra
Revision as of 05:32, 2 August 2026 by WikiSysopIG (talk | contribs)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

The Wiki@IndraStra Manual of Style (MoS) establishes the editorial, formatting, and writing standards for all content published on Wiki@IndraStra. It promotes consistency, readability, neutrality, and structured presentation across articles, templates, and project pages. Contributors are encouraged to follow these guidelines when creating or editing content.

Purpose

The Manual of Style aims to:

  • Maintain a consistent appearance across the platform.
  • Improve readability and accessibility.
  • Facilitate structured knowledge organization.
  • Support data consistency for templates and Cargo tables.
  • Promote professional and encyclopedic writing.

General Principles

Articles should be:

  • Neutral in tone.
  • Fact-based and verifiable.
  • Clearly organized.
  • Well-referenced.
  • Free from promotional language.
  • Written in formal English.

Article Structure

Most articles should follow a logical structure appropriate to the subject. A typical company article may include:

  1. Lead
  2. History
  3. Corporate Profile
  4. Business Operations
  5. Products and Services
  6. Markets
  7. Leadership
  8. Financial Performance
  9. Corporate Governance
  10. Sustainability
  11. Strategic Developments
  12. References
  13. External Links

Articles on other subjects should adopt a comparable logical structure.

Lead Section

Every article should begin with a concise introductory paragraph that:

  • Identifies the subject.
  • Explains why it is notable.
  • Summarizes the most important facts.
  • Avoids excessive detail.

The lead should normally stand alone as a summary of the article.

Writing Style

Editors should:

  • Write in complete sentences.
  • Use active voice where appropriate.
  • Avoid subjective or promotional language.
  • Avoid first-person writing.
  • Avoid unnecessary jargon.
  • Explain technical terminology when appropriate.

Avoid words such as:

  • Leading
  • Best
  • Premier
  • World-class
  • Revolutionary

unless directly attributed to reliable sources.

Neutral Point of View

Articles should present information fairly and proportionately.

Where differing viewpoints exist, they should be summarized using reliable sources without editorial endorsement.

Verifiability

Factual statements should be supported by reliable published sources.

Preferred sources include:

  • Government publications
  • Regulatory filings
  • Official company reports
  • Academic journals
  • Books from reputable publishers
  • International organizations
  • Established news organizations

Original Research

Wiki@IndraStra primarily documents published knowledge.

Original analysis should only be included where:

  • Methodology is transparent.
  • Assumptions are clearly identified.
  • Supporting evidence is provided.
  • The analysis complies with applicable editorial policies.

Headings

Use sentence case for headings.

Correct:

== Corporate governance ==

Incorrect:

== Corporate Governance ==

Headings should accurately describe the section content.

Company Names

Use the organization's complete legal name upon first mention.

Example:

Apple Inc.

Subsequent references may use the common name where appropriate.

Dates

Dates should use the format:

1 January 2026

Avoid regional date formats.

Numbers

Use commas for large numbers.

Example:

1,250,000

Use internationally recognized units wherever practical.

Currencies should identify the currency.

Examples:

US$2.5 billion
₹125 crore
€850 million

Capitalization

Avoid unnecessary capitalization.

Use official capitalization only for proper names and trademarks.

Abbreviations

Spell out abbreviations upon first occurrence.

Example:

Environmental, Social and Governance (ESG)

Thereafter:

ESG

Internal links should connect related Wiki@IndraStra articles.

Avoid excessive linking.

External links should normally appear only in the "External links" section unless required for citations.

Images

Images should:

  • Be relevant to the article.
  • Be appropriately licensed.
  • Include descriptive captions.
  • Support the surrounding text.

Decorative or excessive images should be avoided.

Infoboxes

Where available, articles should use the standard Wiki@IndraStra templates.

Editors should not create alternative infoboxes without community consensus.

Templates

Templates should:

  • Follow established naming conventions.
  • Be reusable.
  • Support structured data.
  • Avoid unnecessary complexity.

Categories

Every article should belong to one or more appropriate categories.

Categories should be:

  • Specific
  • Hierarchical
  • Non-redundant

References

References should be presented using inline citations wherever practical.

Unsourced factual claims may be challenged or removed.

External links should be limited to authoritative resources such as:

  • Official websites
  • Regulatory authorities
  • International organizations
  • Public databases

Commercial or promotional links should generally be avoided.

Corporate Intelligence Articles

Company articles should maintain a neutral and factual presentation of:

  • Corporate identity
  • Business activities
  • Leadership
  • Ownership
  • Financial performance
  • Products and services
  • Markets
  • Strategic developments
  • Regulatory matters
  • Risk factors

Speculation, rumours, and unsupported claims should not be presented as factual information.

Structured Data

Where applicable, articles should utilize:

  • Standard templates
  • Cargo data fields
  • Categories
  • Navigation templates
  • Structured metadata

Structured information should complement, not replace, descriptive content.

Language

Wiki@IndraStra uses English as its primary editorial language.

Editors should use clear, internationally understandable English and avoid unnecessary regional expressions.

Consistency

Editors are encouraged to maintain consistency with existing articles, templates, and formatting conventions.

Where uncertainty exists, contributors should follow established practices used throughout the platform.

See also