MediaWiki to AsciiDoc Converter

About MediaWiki to AsciiDoc Converter

Convert MediaWiki table markup to AsciiDoc table format. Perfect for technical documentation, books, and publishing workflows using AsciiDoc.

Key Features

• Multiple Table Styles: Grid, simple (PSV), and CSV formats
• Header Support: Toggle header row with options attribute
• Auto-sizing: Grid tables automatically adjust column widths
• AsciiDoc Compatible: Works with Asciidoctor and AsciiDoc processors
• Publishing Ready: Suitable for books, manuals, and documentation
• File Upload: Upload .wiki files directly
• Instant Preview: Real-time conversion as you type
• Copy & Download: Easy export options

How to Use

1. Input MediaWiki Table: Paste your MediaWiki table markup or upload a .wiki file
2. Choose Style: Select table style and header options
3. Review Output: The AsciiDoc markup updates automatically
4. Copy or Download: Use the Copy or Download button to save your AsciiDoc

Table Styles

• Grid: Bordered table with visible cell boundaries (best for complex tables)
• Simple (PSV): Pipe-separated values with clean syntax (most common)
• CSV: Comma-separated values format (compact and portable)

Example Conversion

MediaWiki Input:

{| class="wikitable"
! Name !! Age !! City
|-
| John Doe || 28 || New York
|-
| Jane Smith || 34 || London
|}

AsciiDoc Output (Simple):

[options="header"]
|===
| Name | Age | City

| John Doe | 28 | New York
| Jane Smith | 34 | London
|===

AsciiDoc Output (Grid):

+------------+-----+----------+
| Name       | Age | City     |
+============+====+===========+
| John Doe   | 28  | New York |
+------------+-----+----------+
| Jane Smith | 34  | London   |
+------------+-----+----------+

Common Use Cases

• Technical Documentation: Create documentation with AsciiDoc
• Book Publishing: Write books using AsciiDoc format
• API Documentation: Document APIs with structured tables
• User Manuals: Create professional user guides
• README Files: Enhanced documentation for projects
• Static Site Generators: Use with Jekyll, Hugo, or Antora

AsciiDoc Compatibility

The generated markup is compatible with:

• Asciidoctor (Ruby implementation)
• AsciiDoc Python
• Antora (documentation site generator)
• GitHub AsciiDoc rendering
• GitLab AsciiDoc support
• Static site generators supporting AsciiDoc

When to Use Each Style

• Grid: Complex tables with many columns, precise alignment needed
• Simple: Most common choice, clean and readable source
• CSV: Compact format, easy to import/export, good for data tables

Tips for Best Results

• Use simple style for most documentation tables
• Use grid style when you need precise column alignment
• Use CSV style for data-heavy tables
• Keep cell content concise for better readability
• Use header row for column names
• Test output with Asciidoctor to verify rendering
• Consider table width in final rendered output

Frequently Asked Questions (FAQ)

• Which AsciiDoc processors are supported?

  The generated markup targets standard AsciiDoc syntax and works well with Asciidoctor, Antora, and other popular AsciiDoc processors that follow the common syntax rules.

• Can I use this output in static site generators?

  Yes. You can drop the resulting AsciiDoc tables into documentation projects built with Antora, Hugo (with AsciiDoc support), Jekyll (via plugins), and other static site generators that accept AsciiDoc content.

• What if my wiki table contains very long text or code blocks?

  Long content is preserved, but it may affect table width and readability. For code samples or large blocks of text, consider moving them outside the table into dedicated code blocks or paragraphs in your AsciiDoc document.

• Does the tool support complex MediaWiki features like row spans or nested tables?

  No. The converter focuses on simple, rectangular tables. Advanced features such as rowspans, colspans, or nested tables are not automatically translated and may require manual editing in the AsciiDoc output.

• Is any of my MediaWiki or AsciiDoc content uploaded?

  No. All parsing and conversion are done client-side in your browser. Your input and output remain on your device and are not sent to any remote server.

Privacy & Security

All conversions happen locally in your browser. Your MediaWiki data is never uploaded to any server, ensuring complete privacy and security.