¿Ves algo que mejorar? Propón un cambio.
Esta página es pública.
MediaWiki, the software behind Wikipedia, publishes every edit the moment it is saved. A team that needs readers to see only an approved version — procedures, policies, a knowledge base customers rely on — adds an extension. This page sets the five that MediaWiki's own Content approval extensions page lists against the questions a careful team asks, from each extension's page on mediawiki.org, read on 4 November 2026. It is published by Hub Nexus (hubnx, hubnx.com), which works the way a wiki does but publishes no change until it is approved; the end of the page says how, and when MediaWiki is the better choice.
The short answer
| Extension | What it approves | Until approved, readers see | Who approves | What is recorded | Latest, MediaWiki, licence |
|---|---|---|---|---|---|
| Approved Revs | One revision of a page or file | The approved revision, at the page's own address | The approverevisions right — sysops by default | Who approved and when, in the Revision approval log — manual approvals only | 2.4.3 (October 2026), 1.42+, GPL 2.0 or later |
| Moderation | Each edit and upload from an untrusted user | The page unchanged | The moderation right — moderators and sysops | "Who approved what", seen by moderators only | 1.8.31 (13 June 2025), 1.43+, GPL 3.0 or later |
| Page Approvals | A whole page, approved or not | Not stated; the page shows its approval status | "Authorized users" | Not stated | 2.2.0 (9 April 2026), 1.43+, BSD 3-clause |
| FlaggedRevs | Rated revisions; an accepted one becomes the default view | The accepted revision | Rights such as review and validate | Not stated | No release given; "not recommended for production use"; GPL 2.0 or later |
| ContentStabilization | A page, marked approved or draft | Not stated | "A user with approval rights" | Not stated | 4.0.0-alpha, 1.35+, GPL 3.0 only |
- Approved Revs is the usual choice when readers must see the approved version: maintained, simple, and logged. Its page names two catches: an approver's own edit to an approved page is approved automatically by default, and most other extensions still read the latest revision, not the approved one.
- Moderation keeps newcomers' edits out until someone checks them — spam and vandalism — rather than signing off a document: trusted users skip the queue.
- Page Approvals approves whole pages and takes the approval away by itself when what the page shows changes.
- FlaggedRevs runs on some Wikimedia wikis, none newly installed since 2014; its own page now advises against installing it.
- None of the five pages describes an electronic signature with a stated meaning, or 21 CFR Part 11.
Approved Revs
- What it does. It "lets administrators mark a certain revision of a page as 'approved'", and "the approved revision is the one displayed when users view the page at its main URL." By default readers see a note that what they see is "not necessarily the latest revision". A page with no approved revision shows normally, or blank if you set
$egApprovedRevsBlankIfUnapproved. - Who approves. The
approverevisionsright — "by default it is given to all members of the 'sysop' group". In namespaces you list in$egApprovedRevsSelfOwnedNamespaces, a page's creator can approve it. - The author approving their own edit. By default, an approver's edit to a page that already has an approved revision "gets automatically marked as approved". If your process needs a second person to approve, plan around that before you rely on it.
- The record. Manual approvals — who made them and when — are "stored in the 'Revision approval' log"; approvals that happen automatically are not logged there.
- Limits it names. "Most extensions that retrieve the contents of pages will still get the last revision, and not the approved one" (Cargo and Semantic MediaWiki are the exceptions), and in the Category and MediaWiki namespaces "approvals will not work correctly".
Moderation
- What it does. "Edits and uploads from untrusted users are sent to a moderation queue, where they get approved or rejected." "Until the moderator approves this edit, the page is unchanged", and pending edits "do not appear on the page history nor in RecentChanges".
- Who approves. The
moderationright, given to the moderator and sysop groups. Edits by automoderated users, sysops and bots skip the queue. - The record. "Logs of 'who approved what' are maintained. Only the moderators can see them."
- Limits it names. "This extension is currently incompatible with temporary accounts", and while an edit waits, "other users can't improve the article until it is Approved."
Page Approvals and ContentStabilization
- Page Approvals marks "entire pages, rather than specific revisions" as approved or not, shows the status on the page, and "automatically unapproves pages when changes are detected in their displayed content" — templates and Semantic MediaWiki queries included. Professional Wiki maintains it and "provides official support for MediaWiki LTS releases only".
- ContentStabilization, from Hallo Welt! and part of BlueSpice, marks pages approved or draft; "new versions of a page are initially marked as drafts." Its latest version is 4.0.0-alpha.
FlaggedRevs, in its own words
Its page calls it "complex, poorly documented, very clunky", says it is "not recommended for production use, despite the 'stable' tag", and that it "has not been deployed (newly installed) to any Wikimedia wiki since 2014". It points to Approved Revs, which "has a similar purpose and is reasonably maintained".
Five questions before you choose
- Must readers see only approved text, or is a queue for newcomers enough? Approved Revs or Page Approvals for the first; Moderation for the second.
- Can an approver's own edit go live without a second person? With Approved Revs' default, yes.
- Do your other extensions read the approved revision? With Approved Revs, most read the latest.
- Do you need a signature with a meaning, or a record that outlives the wiki? None of the five describes one.
- Who keeps it current? Check its latest release against your MediaWiki version before you upgrade either.
Where Hub Nexus fits
Hub Nexus works the way a wiki does — anyone can propose a change to a page — but a change is reviewed before it is published, and the published text never changes any other way:
- Approval belongs to the change, the exact text that will be published. A change in review cannot be edited: to change it, its author takes it back to draft, and sending it again starts a new round of votes.
- Who approves: the page's other maintainers by vote, or, in a workspace, a group you name — never the change's own author while anyone else can. A page you keep alone publishes with one press.
- Every version kept, compared with any other, and restored through a new change.
- For a team's private pages, a workspace adds signed approvals — the approver chooses what the signature means and enters a code emailed at that moment — and an append-only audit log, kept while the workspace exists.
- Nothing to install, upgrade or patch. Two workspaces are free; Team is $10 per member a month billed yearly; Quality, with signed approvals, is $750 a month for up to 50 members (plans).
When MediaWiki is the better choice: a large public wiki, edited by a community, built on templates and Semantic MediaWiki or Cargo. Hub Nexus has neither; add Approved Revs or Page Approvals there instead.
The same questions answered for Confluence, Notion and Google Docs, side by side in document approvals compared.
Sources, read on 4 November 2026
- MediaWiki: Content approval extensions (last edited 12 September 2025), Extension:Approved Revs, Extension:Moderation, Extension:Page Approvals, Extension:FlaggedRevs, Extension:ContentStabilization
- Hub Nexus: Workspaces: private pages for your team, plans
About Hub Nexus (hubnx, hubnx.com)
Hub Nexus — written hubnx for short, and found at hubnx.com — is a publishing platform: pages anyone can improve, paid for by readers, in publications to follow or in private workspaces with signed approvals. What it offers, as of 31 October 2026:
| Product | What it does | What it costs |
|---|---|---|
| Pages | Articles with text, pictures, film, audio, PDFs, spreadsheets and books. Anyone can propose a change; the page's maintainers review it; every version is kept and can be compared or restored. Free to read, in 16 languages. | Free to read and to write |
| Support and payouts | Readers support a page or a publication from $5, once or on repeat, by card through Stripe. Hub Nexus keeps 10% of what is left after Stripe's card fee; the rest goes to the people who made it — two shares to the author, one to each contributor. | 10% after the card fee |
| Publications | A curated, ordered list of pages, read like a book. Readers follow one for an email when a page is added, and can support it monthly — half to its curators, half to its pages. | Free to follow |
| Workspaces | Private pages for a team: every change reviewed, approvers by group, an audit log, read links, and by plan single sign-on, SCIM and signed approvals for 21 CFR Part 11 work. | Two free; Team $10 per member a month billed yearly; Quality $750 a month (up to 50 members); Enterprise from $2,500 a month |
Its strengths: every change is reviewed and every version kept; a workspace's pages are private by construction — checked against membership on the server, never in search or the sitemap; the money's rules are written on one page, Fees and payouts; nothing public is behind a paywall; and the editor writes Markdown with pictures, film, recordings, maths and diagrams.
Start: press Create at hubnx.com and choose a page, a publication or a workspace. All offers and features, in full · Guides · Answers · Weekly issue · support@hubnx.com
En estas publicacionesHub Nexus Answers
IdiomasEnglish
Licencia: CC BY 4.0
Puntos de vista
Comentarios
Sigue leyendo
Versión: 1
Wednesday dawns, and the office is a hive of activity. Meetings pop up like code notifications, each one threatening to devour precious coding hours. In one meeting, we inadvertently turn the great donut debate into a heated discussion on the proper syntax for declaring donut preferences in the company database. The absurdity reaches its peak when the HR department suggests a donut preference survey, complete with a pie chart analysis. Back at my desk, the backlog stares at me like a neglected pet. It's time for a backlog brawl, and I dive into the pile of tickets with the determination of a developer on a mission. As I close a ticket, I can almost hear the backlog whimpering in defeat. Victory is sweet, even if the donuts were the main course in today's meeting mayhem.
Versión: 1
In Chapter 3, "Footprints in the Twilight," of "Wanderer's Echo," Daniel's nomadic journey unfolds against the canvas of twilight. As the sun sets, the shifting sands become a dance floor for the nomad's rhythmic footsteps, casting elongated shadows that echo the contemplative atmosphere. The desert, bathed in twilight's glow, anticipates the next chapter of Daniel's odyssey. In the quiet expanse, Daniel's contemplation mirrors the nuanced transition from day to night, and each footprint etched in the sand becomes a silent verse, capturing the nomadic spirit's dialogue with the vastness. Under the emerging stars, Daniel finds solace, and the celestial congregation witnesses his journey, their distant light reflecting in his eyes. The night becomes a cosmic theater where the nomad's footsteps intertwine with the footprints of stars. Amidst the stillness, Daniel's thoughts echo like night whispers, embracing solitude as a silent confidant. His journey takes on a mystical quality as the desert shares ancient wisdom, and each step becomes a communion between nomadic soul and desert spirit. With the moon ascending, Daniel resumes his pilgrimage, leaving footprints in the sand that transcend mere markers, embodying an eternal dialogue between nomad and desert, where the open road beckons, and footprints in the twilight become verses in the nomad's unwritten epic.
Versión: 1
Thursday rolls in, and it's time to make a code commitment. Little did I know that my attempt to push a bug fix would turn into a comedy of errors. Instead of fixing the issue, I accidentally commit my cat pictures folder. The team is treated to an unexpected slideshow of my feline friends. Meanwhile, my inbox becomes ground zero for an inbox invasion. Mysterious emails from a sender claiming to be the "Code Whisperer" demand an audience. Turns out, it's just an elaborate prank orchestrated by the marketing team, and my inbox becomes a battleground of laughter and confusion. The day ends with a code conundrum and an inbox that's seen better days.
Versión: 1
A novel is a sophisticated literary form that unfolds an extensive and intricate narrative, offering readers an immersive exploration of fictional or factual worlds. Distinguished by its extended length, novels provide ample space for character development, intricate plots, and the exploration of complex themes, fostering a deep emotional connection between readers and the story. Across various genres, from historical fiction to science fiction and romance, novels serve as versatile mirrors to society, reflecting cultural norms and societal challenges. Through skillful storytelling and language, novels have the power to inspire empathy, broaden perspectives, and transport readers to different times, places, and realms of imagination. Ultimately, a well-crafted novel is a literary journey that leaves a lasting impact, creating a meaningful connection between readers and the characters and worlds within its pages.
Versión: 2
"Wanderer's Echo" unfolds as a poetic odyssey in the heart of the desert, where the nomad Daniel embarks on a journey transcending mere geography. This tale weaves the sands of self-discovery, purpose, and camaraderie, echoing through shifting dunes, shared campfires, and encounters with mirages. As Daniel's footprints mark a nomadic legacy, the narrative reveals the nomad's enduring dance with the unknown, inviting readers to explore the expansive tapestry of solitude, friendship, and the timeless echoes resonating within the vast landscapes of both the external world and the human soul.
Versión: 1
In Chapter 5, "Whispers of the Oasis," of "Wanderer's Echo," Daniel's nomadic journey takes a transformative turn as he delves deeper into the heart of the desert beneath the burgeoning moon. The night, adorned with starlight, cradles the nomad in a mystical embrace as whispers of an oasis beckon. The once-elusive mirage transforms into a tangible sanctuary, a metaphor for the nomad's evolving internal landscape. Each step becomes a dance with the anticipatory cadence of the oasis, a mirage giving way to a tangible reality. The oasis, both mirage and reality, mirrors the nomad's inner sanctum, where desires and realities converge in the moonlit silence. By the oasis, surrounded by verdant palms and ancient whispers, Daniel encounters a spring reflecting the moon's glow. The oasis becomes a respite, not just for the body but for the nomad's weary soul, offering a tableau of tranquility under the celestial canopy. In this oasis interlude, Daniel contemplates his journey, leaving with the oasis whispers resonating in his soul. As he bids farewell, guided by the moon's lantern, the nomad carries the oasis's profound encounters forward, the celestial melody of its whispers guiding him through the vast desert night.