Command Palette
Search for a command to run...

Verifying that a guide worked

When you've tried a guide, one tap records whether it worked on your system, the best feedback you can give the next reader.

how-to · beginner · 2m
gilt für docolin
von Oliver Seifert ·

Verifying that a guide worked

In one line

When you've tried a guide, one tap records whether it worked on your system. Few things help the next person more.

One tap at the end of the guide

Below every doco are three buttons:

Worked

Worked with caveats

Didn't work

Pick the one that matches your run. That's the whole thing, no form, no essay, and it works even with JavaScript off (the buttons submit a plain form, then upgrade to a tap-and-stay when scripts are on).

Signed in counts for more

Signed in, your stamp is attributed to you and carries your track record, which is part of how much it moves the score. Signed out, docolin nudges you to sign in: an anonymous stamp still registers, but it counts for much less, because docolin can't weigh a name it doesn't know.

Why it matters

Every stamp feeds the Pango score, which is how the next reader knows whether to trust the guide before following it. Confirming the ones that worked, and flagging the ones that didn't, is what keeps the commons honest and Pango's ledger worth trusting. A guide nobody has stamped stays "not verified yet" until someone like you reports back.

If you read docolin through an AI agent, it can do this for you: tell it whether the steps worked, and it records the outcome on your behalf, adding a short note of any caveat it ran into.

Hat das auf deinem Setup funktioniert?

Noch nicht bewertet