Vote on knowledge, technologies and cases

A vote is your judgment on the quality of something Fito holds. You hold at most one vote per thing, up or down, and you can change it or take it back at any time.

This is the whole of a learner’s curation surface. Anyone signed in can vote. Nothing else is asked of you, and there is no role to apply for.

Before you begin

You are signed in to the web app. A signed-out visitor sees the counts but cannot vote — see Create an account and sign in.

Where the control is

The up/down pair sits next to the title on three kinds of page:

Page	Address	What you are judging
A knowledge component	`/knowledge/<type>/<slug>`	That one write-up
A technology	`/knowledge/<slug>`	The technology as a whole
A case cover	`/cases/<id>`	That case

Replace <type> and <slug> with the component’s own reference parts, and <id> with the case’s id. You never type these — you reach them by browsing. See Browse the knowledge area and Find a case to work on.

Cast a vote

Open the page for the thing you want to judge.
Find the two chips beside the title. Each shows an arrow and a count — the up arrow with its upvotes, the down arrow with its downvotes.
Click the arrow you mean. The counts update straight away, and the chip you clicked fills in to show the vote is yours.

Confirm it worked: one of the two chips is now filled, and its count went up by one.

If the write fails, the control says so beside the chips and your vote is not recorded. Click again.

Change or retract a vote

Both are one click on the same pair.

To switch, click the other arrow. One count drops, the other rises.
To take it back, click the arrow that is already filled. The chip empties and the count drops.

Casting the same vote twice changes nothing at all. It does not even move the vote’s timestamp, so a re-click never makes an old vote look fresh.

What a vote means

It judges content quality, and it reaches the person who wrote the content.

That is the one thing two numbered arrows cannot say on their own, which is why the control carries it on hover: “Vote for the content quality. Content creators receive this assessment.”

What each vote sticks to

The three targets bind to different things, and the difference matters when content changes underneath you.

A knowledge component vote sticks to the revision you are reading, not to the chain. Every revision is its own row with its own reference id, so a corrected replacement starts clean instead of inheriting the downvotes of the defect it repaired. See Versions and alternative definitions.
A technology vote covers the technology as a whole, not one major line. A technology carries two editable descriptions — the overview and each major line’s own prose — and both are corrected in place, so there is no successor to keep clean.
A case vote survives a version publish. A case keeps its id across versions, so your vote stays on the case rather than on the version you happened to work.

Where a downvote goes

A downvote puts the target into the curation catalogue, the worklist a case creator opens at /curation. The catalogue ranks targets by the downvotes each has attracted since it was last judged, so a fresh wave of downvotes lifts a target back to the top even if somebody already looked at it.

A downvote never hides, removes or demotes anything on its own. No count crosses a threshold and triggers something. A person reads the queue and decides.

See Work the curation catalogue for what happens on the other side.

Signed out

The counts are public, so a signed-out visitor sees them. They render as plain text rather than as buttons, and a Log in to vote link sits beside them.

A vote is attributed to a person by definition, so there is no anonymous vote and no visitor identity is invented to stand in for one.

What’s next

Work the curation catalogue — the queue your downvotes feed.
Triage indications on your case — saying what is wrong, which a vote cannot.
Browse the knowledge area — finding the components and technologies to judge.