← Back to mockups index

📋 URL Structure Proposal v2 — Wikimedia Analysis + Corrections

🔬 v2.1 — Based on comparative Wikimedia analysis 2026-06-10  🔄 2 major corrections integrated  ✅ 2026-06-12 — Coherence audit: contract ecosystem completed (10 dimensions)  🇫🇷 Version française

This v2 proposal corrects two fundamental points of v1 based on a comparative analysis of the 4 major Wikimedia projects (Commons, Meta-Wiki, Wikipedia EN, Wikibooks):
① Multilingual: every URL must include a language suffix (/en mandatory, even for English)  ·  ② Contracts = articles (core marketplace content, not governance)

🔬 1. Comparative Analysis — 4 Wikimedia Projects

Each Wikimedia project has developed its own conventions to separate governance, content, and multilingual structure. These patterns are the foundation of our v2 proposal.

Aspect analyzed 🖼️ Wikimedia Commons
commons.wikimedia.org
🌐 Meta-Wiki
meta.wikimedia.org
📖 Wikipedia EN
en.wikipedia.org
📚 Wikibooks
en.wikibooks.org
Governance / rules namespace Commons:
E.g.: Commons:Project_scope, Commons:Deletion_policy, Commons:Licensing
Meta:
E.g.: Meta:About, Meta:Babel
Wikipedia:
E.g.: Wikipedia:Core_content_policies, Wikipedia:NPOV, Wikipedia:Namespace
Wikibooks:
E.g.: Wikibooks:Policies_and_guidelines, Wikibooks:Community_Portal
Main content namespace File: (media)
Files are the core content. E.g.: File:Cat.jpg
(main) no prefix
Coordination pages. E.g.: Terms_of_use, Stewards
(main) no prefix
Encyclopedic articles. E.g.: Switzerland, Cooperative
(main) no prefix
Collaborative books. E.g.: Calculus, Python_Programming
Thematic portals Commons:Portal or categories
E.g.: Commons:Photography, Commons:Arts
Project pages in main
E.g.: Wikimedia_Forum, Research
Portal: (namespace 100)
E.g.: Portal:Science, Portal:Arts — 5000+ portals
Subject: namespace or categories
E.g.: Subject:Mathematics
Multilingual — main pattern Subpages /language
E.g.: Commons:Policies_and_guidelines/fr, /de, /es
All languages on the same domain
Subpages /language
E.g.: Meta:About/fr, Meta:About/de, Meta:About/ru
Same domain meta.wikimedia.org
Subdomains
fr.wikipedia.org, de.wikipedia.org, es.wikipedia.org… each language = separate wiki
Subdomains
fr.wikibooks.org, de.wikibooks.org… same model as Wikipedia
Default language (no prefix) Implicit English (no /en)
But all translations are explicit subpages /fr /de etc.
Implicit English (no /en)
Same convention: the version without suffix = EN
Subdomain en.wikipedia.org
English has its own subdomain — no "language-less" version
Subdomain en.wikibooks.org
Same logic: /en is explicit via the subdomain
Community Portal Commons:Community_portal
Content: policies, backlogs, elections, contests, GLAM, multilingualism. NOT the media files themselves.
Main page + coordination forums
Meta is entirely dedicated to coordination. No separate "portal".
Wikipedia:Community_portal
Content: to-do, articles to improve, ongoing discussions. NOT the encyclopedic articles.
Wikibooks:Community_Portal
Content: collaborative projects, discussions, resources. NOT the books themselves.
Governance / content separation Strict: Commons: = rules. File: = media. Never mixed. Total: Meta-Wiki is entirely governance. Content lives elsewhere. Strict: Wikipedia: = rules. (main) = articles. Portal: = thematic portals. Strict: Wikibooks: = rules. (main) = collaborative books.
WikiDeal analogy Commons = media repository
WikiDeal = contract repository
Contracts are WikiDeal's "File:"
Meta = institutional governance
meta.wikideal.net? for central governance
Wikipedia = encyclopedic articles
WikiDeal = contract pages + marketplace portals
Structure (main) + Portal: → Contract: + Market:
Wikibooks = collaborative books
WikiDeal = collaborative contracts
Same idea: co-created content organized by topic

1.1 Real URLs observed on each project

🖼️ Commons — Observed URLs

🌐 Meta-Wiki — Observed URLs

📖 Wikipedia EN — Observed URLs

📚 Wikibooks — Observed URLs

💡 2. Lessons for WikiDeal

🖼️ From Commons → WikiDeal

🌐 From Meta-Wiki → WikiDeal

📖 From Wikipedia → WikiDeal

📚 From Wikibooks → WikiDeal

✅ 3. Corrections Integrated in Proposal v2

🔧 Correction 1: Multilingual — /en mandatory on all URLs

v1 problem: URLs had no language suffix. WikiDeal:Arbitration presupposed English as the "prefix-less" default.

v2 solution: Every URL — whether in English or any other language — must carry an explicit language suffix.

Phase Pattern Example
Phase 1 (now) wikideal.net/wiki/[Page]/en wikideal.net/wiki/WikiDeal:Arbitration/en
Phase 1 (translation) wikideal.net/wiki/[Page]/fr wikideal.net/wiki/WikiDeal:Arbitration/fr
Phase 2 (long term) en.wikideal.net/wiki/[Page] en.wikideal.net/wiki/WikiDeal:Arbitration

Inspired by: Wikipedia (en.wikipedia.org — English has its own subdomain) + Commons/Meta (explicit /fr subpages). English is never "the version without a prefix" — it is a version like any other.
🔧 Correction 2: Contracts = Articles (marketplace content), not governance

v1 problem: Contracts appeared in the Community Portal and were treated as "separate" resources, between the rules and the marketplace.

v2 solution: Contracts are WikiDeal's equivalent of Wikipedia articles. They are the wiki's core content, organized through marketplace portals.

Analogy:
Wikipedia WikiDeal
Article: Switzerland Contract: Contract:Babysitting_Base/en
Portal:Geography → geo articles Market:Babysitting → babysitting contracts
Wikipedia:NPOV (rule) WikiDeal:Contract_Governance/en (rule)
Talk:Switzerland (discussion) Contract_talk:Babysitting_Base (discussion)

Each contract has an ecosystem of satellite pages: individual clauses, legal references, use cases, alerts.
💡 Option: meta.wikideal.net for institutional governance

Inspired by: meta.wikimedia.org — a subdomain entirely dedicated to institutional coordination.

Proposal: Advantage: Total governance/content separation, as at Wikimedia. Governance can evolve independently of content.
✅ Validated with Theo — Recommended for phase 2 minimum.

🔄 4. Migration Path: /lang Suffix → Subdomain Prefix

The current suffix structure (/en, /fr) is designed to make a later migration to subdomains easy. It is not a compromise — it is a deliberate phase 1 choice with a planned trajectory towards en.wikideal.net, fr.wikideal.net, etc.

🛠️ The migration is technically trivial

📅 Deployment phases

🔀 Concrete migration example — WikiDeal:Arbitration

Step URL Status
Phase 1 (now) wikideal.net/wiki/WikiDeal:Arbitration/en ✅ Active page
Phase 2 (target) en.wikideal.net/wiki/WikiDeal:Arbitration 🎯 New canonical URL
Auto redirect wikideal.net/wiki/WikiDeal:Arbitration/en  →  301  →  en.wikideal.net/wiki/WikiDeal:Arbitration 🔄 nginx regex block
✅ Conclusion: The suffix structure is a deliberate phase 1 choice. Migration to subdomains is planned and technically trivial — about ten lines of nginx config + native MediaWiki #REDIRECTs. No link will ever break thanks to permanent 301 redirects.

📋 5. Strategic Decisions to Validate

⚠️ These 4 decisions require explicit validation before implementation ❓ 4 decisions pending
# Decision ✅ Recommendation 🔀 Alternative 💬 Justification Status
1 meta.wikideal.net
Subdomain dedicated to institutional governance, inspired by meta.wikimedia.org
❌ NOT for now
Keep everything on wikideal.net with the WikiDeal: namespace
Separate subdomain
meta.wikideal.net
like meta.wikimedia.org
~15 governance pages currently → a separate subdomain = unnecessary complexity at this stage.
Create meta.wikideal.net when volume > 500 governance pages.
2 Contracts — dedicated namespace
Where to host contracts: centralized Contract: or subpages of Market:?
✅ YES — centralized Contract:
E.g.: Contract:Babysitting_Base/en
Contracts as portal subpages:
Market:Babysitting/Contract_Base/en
Transversality: the same contract can serve several Market: portals.
Contract: = core content (≈ Wikipedia articles).
No dependency on a specific portal.
3 support/ pages
Dashboard, wallet, register, simulation, buy-subscription…
❌ OUTSIDE THE WIKI
app.wikideal.net, not MediaWiki
Pages in MediaWiki:
Support:Dashboard/en
Dashboard, wallet, register, simulation = application features, not editorial content.
MediaWiki is not an application framework — do not mix.
4 community/ pages
Apply_Developer, Apply_Lawyer, Create_User_Group…
WikiDeal:Meta/
E.g.: WikiDeal:Meta/Apply_Developer/en
Dedicated namespace:
Community:Apply_Developer/en
Internal project procedures, not encyclopedic articles.
WikiDeal:Meta/ = wiki operational layer — the right layer for participation processes.

📊 6. Reclassification Table v2 — 178 pages

Changes compared to v1: ① All URLs carry the /en suffix · ② Contracts are reclassified as "marketplace content" (mobility 🟢) · ③ Contracts are affiliated to their respective Market: portals
WikiDeal: Immutable rules
WikiDeal:Meta/ Wiki operations
En/ Editorial content
Contract: Marketplace content (≈ articles)
Market: Marketplace portals
Support: App (outside the wiki)
178
Pages classified
WikiDeal: (rules /en)
WikiDeal:Meta/ (/en)
En/ editorial (/en)
Contract: marketplace
Market: portals
Support/outside wiki
Folder Mockup page (slug) MediaWiki URL v2 (with /en) Layer Mobility Justification v2

🏛️ 7. Community Portal v2 — Without the Contracts

Key v1→v2 difference: The Community Portal no longer lists contracts. Contracts live in their respective Market: portals. The Community Portal remains dedicated to governance, rules, and participation.

📜 Fundamental rules (WikiDeal:)

⚙️ Wiki operations (WikiDeal:Meta/)

📝 Editorial content (En/)

🏪 Marketplace portals (Market:)

👥 Participate

🌍 Available translations

🔮 Phase 2 — Subdomains

🏪 8. Contract Ecosystem — 10 Dimensions around a Marketplace Portal

Example: Market:Babysitting/en — How templates (generic and specific), clauses, common errors, legal references, alerts, debates, usage statistics, use cases and the full lifecycle organize themselves around a portal.

🏪 Market:Babysitting/en — Full structure

🏪 Main portal
  • Market:Babysitting/en
  • Index of all contracts
  • Sector guide
  • Legal framework per country
  • Market:Babysitting/fr (translation)
📄 ① Generic templates (base models)
  • Contract:Babysitting_Base/en
  • Contract:Pet_Sitting/en
  • Neutral reference model, reusable by all apps
  • Maintained by the global community
  • + /fr versions for each
🎯 ② Specific templates (User Group validated)
  • Contract:Babysitting_Base/Variant_KidsCare_App/en
  • Contract:Babysitting_Base/Variant_Geneva_Coop/en
  • Derived from the generic template
  • Validated by a User Group for a specific marketplace app
  • Cross-ref: WikiDeal:User_Groups/en
📋 ③ Individual clauses
  • Contract:Babysitting_Base/Clause_01/en
  • Contract:Babysitting_Base/Clause_02/en
  • Contract:Babysitting_Base/Clause_03/en
  • … dozens of clauses
  • Each clause = subpage of the contract
  • ✅ Validated with Theo
❌ ④ Common errors
  • Contract:Babysitting_Base/Common_Errors/en
  • Frequent drafting mistakes
  • Typical abusive clauses of the sector
  • Cross-ref: WikiDeal:ToU_Worst_Clauses/en
⚖️ ⑤ Legal references
  • Contract:Babysitting_Base/Legal_CH/en (Switzerland)
  • Contract:Babysitting_Base/Legal_FR/en (France)
  • Contract:Babysitting_Base/Legal_EU/en (EU)
  • References per clause + per jurisdiction
  • ✅ Validated with Theo
⚠️ ⑥ Alerts & Risks
  • Contract:Babysitting_Base/Alert_Abuse/en
  • Contract:Babysitting_Base/Alert_Hours/en
  • Contract:Babysitting_Base/Alert_Payment/en
  • Alerts per clause (abusive clauses, risks)
  • Cross-referenced with WikiDeal:ToU_Worst_Clauses/en
💬 ⑦ Debates on risks & opportunities
  • Contract_talk:Babysitting_Base/en
  • Contract_talk:Babysitting_Base/Clause_03/en
  • Discussions about conflicting clauses
  • Risks & opportunities debated by the community
  • Wikipedia pattern: native MediaWiki Talk: namespace
📊 ⑧ Usage statistics
  • Market:Babysitting/Stats/en — sector stats
  • Contract:Babysitting_Base/Stats/en — contract usage
  • Usage per marketplace / app
  • Feeds the maturity score (En/Innovation/Maturity_Score/en)
🔄 ⑨ Contract lifecycle
  • Contract:Babysitting_Addendum/en
  • Contract:Babysitting_Amendment/en
  • Contract:Babysitting_Closing/en
  • Contract:Babysitting_Compensatory/en
  • Addendums, amendments, closing, compensation
📖 ⑩ Use Cases
  • Contract:Babysitting_Base/UseCase_Solo/en
  • Contract:Babysitting_Base/UseCase_Family/en
  • Contract:Babysitting_Base/UseCase_Agency/en
  • Concrete usage contexts
  • Links to real pilots (En/Living_Labs/en)
Navigation structure: Market:Babysitting → Contract:Babysitting_Base → Clause_01, Common_Errors, Legal_CH, Alert_Abuse, Contract_talk, Stats, UseCase_Solo, Addendum
Same logic: Wikipedia:Portal:Geography → Switzerland → [History, Geography, Economy] (sub-sections/linked articles)
✅ Coverage checklist — the 10 dimensions of the contract ecosystem (audit 2026-06-12):
  1. Individual clauses → Clause_* subpages ✅
  2. Common errors → Common_Errors
  3. Generic templates → Contract:*_Base
  4. Specific templates (User Group) → Variant_*
  5. Legal references (CH, FR, EU…) → Legal_*
  6. Alerts per clause → Alert_*
  7. Debates on risks & opportunities → Contract_talk:
  8. Usage statistics → Stats
  9. Portals by sector → Market:* ✅ (see below)
  10. Lifecycle → Addendum/Amendment/Closing

🏪 Market:Pet_Sitting/en

🏪 Market:Street_Fundraising/en

🏪 Market:Real_Estate/en

🏪 Market:Musician/en (future)

🗂️ Portals by sector — aggregated view (dimension ⑨)

Above the individual marketplace portals, sector-level aggregator portals group related markets — same logic as Wikipedia's top-level Portal: pages (Portal:Science → Portal:Physics, Portal:Chemistry…).

👨‍👩‍👧 Market:Family_Services/en

🏠 Market:Housing/en

🚕 Market:Transport/en

🐾 Market:Pet_Sitting/en · 💼 Market:Professional/en

🔄 9. Comparison v1 → v2

Aspect ❌ v1 (problems) ✅ v2 (corrections)
English language WikiDeal:Arbitration
English = "language-less" version
WikiDeal:Arbitration/en
English has its explicit suffix
Translations Contract:AI_Cocreation/fr (existed)
But Contract:AI_Cocreation = EN without suffix
Contract:AI_Cocreation/en + /fr
Total coherence — all languages explicit
Contracts in Community Portal Contracts listed in the Community Portal
Treated as "mixed" resources
Contracts = marketplace content, not governance
Affiliated to their respective Market: portals
Community Portal "📄 Contracts (Contract:)" section in the portal
Mixing governance + marketplace
Streamlined portal: governance + operations + participation
No contracts (→ Market:)
Contract mobility 🟡 Stable (treated as rules) 🟢 Flexible (treated as articles/content)
Contract ecosystem structure Not defined. One contract = one page. Contract = hub with a 10-dimension ecosystem:
clauses, common errors, generic & specific templates, legal references, alerts, debates (talk), statistics, sector portals, lifecycle
Institutional governance Everything on central wikideal.net Option: meta.wikideal.net for governance
✅ Validated with Theo (phase 2)
Number of pages 178 pages classified 178 pages reclassified with /en on all URLs

Volumetric summary v2

Layer Mobility Phase 1 pages Pages at maturity v2 notes
WikiDeal: 🔴 Immutable ~65 pages ~2,000 Master /en + translations /fr /es /it — centralized validation
WikiDeal:Meta/ 🟡 Stable ~25 pages ~100 Conventions, architecture, disclaimers, prototypes — all /en
En/ 🟢 Flexible ~55 pages ~1,000 Innovations, analyses, position papers — /en suffix required
Contract: 🟢 Flexible 11 templates ~5,000 Core marketplace content (≈ Wikipedia articles). Each contract = ecosystem of subpages (clauses, legal, alerts, use cases)
Market: 🟡 Stable 14 portals ~500 Sector portals — organize the contracts. Analogy: Wikipedia's Portal:
Support: ⚙️ App 10 pages ~50 Outside the central wiki — app.wikideal.net
TOTAL central wikideal.net 178 mockups ~8,650 Excluding language subdomains and meta.
+ Phase 2 subdomains ~1.5M+ en.wikideal.net + fr. + meta.wikideal.net (option)