Skip to content

Publish a list ​

A list is a text file in a public repository, and people contribute to it with issues and pull requests.

1. Write it ​

In Settings → Backup → Publish your list, fill in its name, description, and author, then press Download my list. Or write one:

! name: Official docs
! description: Tags first-party documentation and nudges it up.
! issues: https://github.com/you/lists/issues
! license: CC0-1.0
! tag: docs | Official docs | #2f5fae

$site=developer.mozilla.org,tag=docs,boost=1 # MDN publishes first-party web platform documentation.
$site=docs.python.org,tag=docs,boost=1 # This is Python's official documentation.

Give each tagged site a # comment saying why it fits. Lists that only tag are friendliest: subscribers choose what tags do. Reuse existing tag ids where they fit, and never change one once published. See the list format.

2. Put it online ​

Upload it to a gist, or to a public repository on GitHub, GitLab, or Codeberg. A name ending .anubis helps.

People paste it into Settings → Lists → Add a list, or use a one-click subscribe link.

4. Let people suggest changes ​

Put your issue tracker's address in Suggestions before downloading, or in the ! issues: line. Subscribers then get a Suggest changes button that opens a filled-in issue there.

5. Add it to the directory ​

Open a pull request adding it to lists/directory.json. See the Lists directory.

Released under the GNU AGPL v3.