Jump to content

Main Page

From SolidWiki


SolidWiki is a MediaWiki specialist - not a generalist web agency that occasionally touches wiki software between other projects. This page explains why that distinction matters, what working with a specialist actually changes, and where to go for full details on services, pricing, and process.

Why a Specialist Instead of a Generalist

MediaWiki is not WordPress, and it is not Confluence. It has its own architecture, its own extension ecosystem, its own performance considerations, and its own failure modes. A web agency that occasionally touches MediaWiki between WordPress builds will configure it adequately. A specialist configures it correctly - and knows the difference between the two long before something breaks.

Deep, focused expertise
We do not split attention across ten platforms. Every hour spent learning goes into MediaWiki specifically - its extension ecosystem, caching behaviour, permission model, and the ways it differs from general-purpose content management systems.
Built to scale from day one
MediaWiki is the same software running Wikipedia at a scale of hundreds of millions of page views. A correctly configured installation can grow from a ten-person internal wiki to a knowledge base with thousands of pages without requiring a rebuild - provided the architecture was done properly the first time.
Security as standard, not an upsell
SSL encryption, firewall configuration, namespace-level permissions, and automated backups are part of every installation, not an optional add-on tier.
Built for the long term
Because MediaWiki is open-source and self-hosted, your knowledge base does not depend on a vendor's pricing changes or feature removals. You own the software, the data, and the server it runs on.

For the full list of services this covers in practice, see MediaWiki Development Services.

Where We Are Right Now

We are a focused, early-stage MediaWiki specialist team. We don't have a long client roster yet, and we'd rather say that directly than imply otherwise. What we offer instead is depth of focus on a single platform, transparent fixed-price proposals, and direct access to the people actually doing the work- not an account manager relaying messages from a delivery team you'll never speak to.

If you'd like to see a real, live example of a MediaWiki installation we've configured, we're glad to walk you through one on an initial call. Real client feedback is available on our main website at solidwiki.com.

Industries MediaWiki Serves

MediaWiki's structure- namespaces, permissions, revision history, and an open extension ecosystem- makes it well suited to a wide range of organisations. The table below describes how the platform applies in different settings; for a summary of who we currently work with, see Who We Work With on the main page.

Sector How MediaWiki Applies
Enterprises & Growing Companies Internal knowledge bases, standard operating procedures, onboarding documentation, and cross-team reference material that scales as headcount grows
Education Course documentation, departmental knowledge bases, and research project wikis benefit from MediaWiki's structured, citation-friendly editing environment
Government & Public Sector Public transparency portals and internal policy documentation benefit from MediaWiki's full revision history, which provides a natural audit trail
Technology Companies Technical documentation, API references, and internal engineering wikis benefit from MediaWiki's template system and API integration options
Open-Source Communities Public project wikis and contributor documentation benefit from MediaWiki's collaborative editing model and zero licensing cost
Research Organisations Structured data and citation management, particularly with the Semantic MediaWiki extension, suit research databases and structured knowledge repositories

Why MediaWiki Is the Platform Worth Building On

A condensed view is below. For the complete explanation with statistics and sourcing, see Advantages and Benefits on the full services page.

Open source
Licensed under GPLv2, with no licensing fees regardless of how large your wiki or team grows.
Proven at enterprise scale
The same software runs Wikipedia, serving hundreds of millions of page views daily across hundreds of languages.
Flexibility
Over a thousand community-built extensions and a fully open skin system support use cases from a simple internal FAQ to a structured, permission-controlled enterprise knowledge base.
Full ownership
Self-hosted means your content, database, and configuration live on infrastructure you control. No vendor can change pricing or restrict access to your own data.
Security through transparency
As open-source software with an active developer community, MediaWiki's codebase is continuously reviewed and patched publicly.
SEO advantages
Clean, semantic HTML, native canonical URL and sitemap support- the same software runs one of the most heavily indexed sites on the internet.

How a Project Works

Every project follows the same structured process, regardless of size. A full breakdown of each phase - setup, branding, migration, and maintenance - is available on the MediaWiki Development Services page. In short:

  1. Discovery - understanding your current documentation situation and what success looks like
  2. Planning - a written, fixed-price proposal with every deliverable listed
  3. Architecture - namespace structure and permissions planned before installation begins
  4. Development - installation, skin development, and extension configuration in a staging environment
  5. Migration - existing content converted and validated against the original source
  6. Testing - functionality, permissions, and performance checked before launch
  7. Deployment - the wiki goes live, with your team trained on day-to-day usage
  8. Ongoing support - updates, monitoring, and backup verification, where a maintenance plan is in place

Frequently Asked Questions

A full FAQ covering pricing, timelines, and technical questions is available on the dedicated FAQ page. A few of the most common questions specific to specialist positioning:

Why choose a MediaWiki specialist instead of a general web development agency?

MediaWiki has its own architecture, extension ecosystem, and performance characteristics distinct from general-purpose content management systems. A specialist brings focused depth on this specific platform, rather than applying generic web development practices to a system that benefits from platform-specific expertise.

Can MediaWiki handle enterprise-scale documentation?

Yes. MediaWiki is the same software running Wikipedia, which manages tens of millions of articles and hundreds of millions of daily page views. A properly architected installation scales well beyond typical enterprise documentation needs.

Can an existing, outdated MediaWiki installation be brought back up to date?

Yes. This is a common engagement. The process typically involves auditing the current version, identifying outdated or vulnerable extensions, and bringing the installation to a current, properly maintained state.

For all other questions - pricing, ownership, migration, and security - see the full FAQ page.

Get Started

Whether you're starting from nothing or trying to fix a wiki that's fallen out of date, the first conversation is free and there's no obligation to continue. We'll give you a direct, honest assessment of whether MediaWiki - and working with us - is the right fit.

Book a consultation: solidwiki.com
Retrieved from "https://hub.solidwiki.com/index.php?title=Main_Page&oldid=83"