Markets/en/Portal:Model/Main
Neutral model for WikiDeal market portals. WikiDeal concept (credits).
Market Portal Model
Purpose
Every WikiDeal market portal is intended to follow one shared structure, so that a user who has learned one market can find their way in any other. This page and its nine subpages form that structure, with neutral example content in each section. A new market (babysitting, small loans, pet sitting, housing, and so on) starts from this model: copy the nine sections, replace the neutral examples with market-specific content, keep the section names and their order.
The model starts from a simple idea: a contract is not a single document but a small ecosystem. Around the contract text live alerts, amendments, legal references, statistics, follow-up messages, quality criteria, packaged versions and tutorials. A portal that offers only the contract text leaves users alone at every difficult moment. A portal that offers all nine sections accompanies them from first contact to final signature and beyond.
The nine sections
| # | Section | What it holds |
|---|---|---|
| 1 | Contract | The base contract model: preamble clauses, substance clauses, annexes. Every clause carries an optional pedagogical commentary: why it makes sense, its advantages, risks and limits. |
| 2 | Alerts | Short messages sent when a contract needs attention: deadlines, late payments, safety issues, pending signatures. |
| 3 | Amendments and addenda | How a living contract changes: amendments modify existing clauses, addenda add new elements. Templates for both. |
| 4 | Legal references | Applicable legal texts, quoted and linked, organized by country and language, with plain-language notes. |
| 5 | Statistics | Anonymized usage statistics showing trends, ordered from the most important indicator to the least important. |
| 6 | Follow-up messages | Message templates for before, during and after the contract: proposals, reminders, alternatives, renegotiation, closing. |
| 7 | Quality criteria | Measurable standards the market community sets for itself: process, service, safety, satisfaction, dispute handling. |
| 8 | Contracts in action | Packaged contracts for apps and platforms: fixed parameters plus predefined variables, intended to be validated by lawyers. |
| 9 | Tutorials | User guides to carry a contract through to success: educational, funny, spectacular. Run by a tutorial sub-community that can organize its own open calls. |
How to instantiate the model
- Choose a short, popular portal name (one or two everyday words) and a full descriptive name.
- Create
Markets/en/Portal:<Name>/Mainwith the market's story: the real-life problem, who the parties are, what trust mechanisms apply. - Create the nine subpages, following the naming pattern
Markets/en/Portal:<Name>/<Section>:<Name>. - Replace the neutral examples of each section with market-specific content. Keep every clause commentary honest: state risks and limits, not only advantages.
- Mark every draft as a draft. Contract clauses and packaged contracts are intended to be reviewed and validated by lawyers before any operational use.
- Mark every figure that is not measured as illustrative.
Editorial rules
- Drafts stay drafts. Nothing on a portal is legal advice. Clauses, packages and legal notes are working material, intended to be validated by lawyers.
- Say which data you mean. Variables typed into a contract (names, amounts, addresses) are private by default. Aggregated anonymized statistics and contract states (signed, completed, in dispute) are published by design.
- Short beats filler. A clause with a three-line commentary that names a real risk is worth more than a page of generalities.
- Both sides of every clause. Each pedagogical commentary answers four questions: why the clause makes sense, what it protects, what risks remain, where it stops helping.
See also
- Contract structures: the state and transition framework behind every contract
- Babysitting portal: the first pilot
- Small Loans portal: the first portal instantiated from this model
- Open Calls