Contribute to the wiki

A clear explanation can save someone else many trials. Help fill missing descriptions, improve wording or point out an error.

Suggest a description from its entry

1. Open the exact overload in the CKS reference.
2. Select Suggest a better description. The form starts with the published description, if available.
3. Write your proposal in Spanish or English. Submit anonymously or provide a name.
4. Select Send proposal. The dialog closes when the inbox confirms receipt.

Proposals go to a private inbox. Upercat reviews them before adding them to the documentation. You do not need a GitHub account, and submissions are not published automatically.

Canceling discards your draft. Reopening the form restores the published description. If sending fails, your text remains in the dialog so you can keep it and try again.

What makes a useful description

• Explain what the exact overload does, receives and returns, as far as you know.
• Keep relevant conditions, edge cases and usage warnings.
• Mark assumptions clearly. A function name alone does not establish its behavior.
• Do not include personal information in the description. An author name is optional.

Entries without a description matter especially. Find them using the explorer’s “Missing” filter.

Inbox protection

Submission limits and progressive waiting periods reduce abuse. If you reach a limit, the form shows how long to wait. A submitted proposal remains pending review and does not change the entry by itself.

Other ways to contribute

For extension changes or a wider technical discussion, use the CKS extension repository. See credits and tools.