Your advisory board

Follow an expert#

1. Open Explore and find an expert by name, by tag or by what they say.
2. Choose Follow on their card or their profile. Their profile also shows how many people follow them.
3. Sync, or start a new session.

All of the expert's public principles run for you from then on, and so does whatever they publish later. To look at single principles first, browse the Library: every principle has a page with its advice, its detector, its tests and how often it fired.

Follow a collection#

A collection is a list of principles from several experts, picked by a curator, at a link like /c/owner/name. You follow it like an expert, on its page. You then trust the curators to choose well: what they add later reaches you too.

Following an expert does not follow the collections they curate, and following a collection does not follow the experts in it. Collections and teams explains how they nest and how to share private principles with a team.

You trust people, not revisions#

When an expert releases a new principle or a new revision, the next sync brings it to your machine and it runs. There is nothing to review or accept.

What you decide is whom you follow, and which of their principles you switch off. So follow the experts you would let review your code.

Switch a single principle off#

Your advisory board lists your experts and collections as rows. Open one to see its principles, each with a switch. A switch you turn off here applies on every machine after its next sync.

There are two more switches that live only on your machine, for one project or for all of them. Turn a principle off covers all three.

When a principle is retired#

An expert can retire a principle when the advice turned out wrong or its detector cannot be made quiet. It then runs for nobody, the expert included. Its page stays and shows the reason, and your advisory board tells you when something you ran was retired.

Retiring cannot be undone, except for a principle synced from GitHub whose folder comes back. The only way to keep a retired principle running is to fork it.

Fork a principle#

Fork on a principle's page copies its newest release into a principle of your own. The fork runs for you, you can change it and add it to your collections, and nothing the original's expert does reaches it. Its page says where it came from.