This repository contains the website-specific presence definitions used by Nowly to display activity in Discord. Each presence lives under src/{LETTER}/{Service Name}/ and supplies its matching metadata, activity script, localized strings, and publishing assets. Browse the source catalog or the generated list below; the list is maintained from presence metadata, not by hand.
The catalog between these markers is updated by scripts/generate-readme.ts after qualifying new-presence merges. Keep the markers intact and do not manually edit generated entries.
-
Propose the platform with its website, the activity it should show, and representative pages or edge cases. Wait for maintainer feedback before starting a new presence.
-
Read the presence authoring guide and Nowly documentation. Compare similar definitions in the source tree. Add your implementation in
src/{LETTER}/{Service Name}/, includingmetadata.json,presence.ts, localized activity strings, and the assets needed for publication. -
From the presences repository root, install dependencies and the published CLI, then build and check your presence (replace
your-service-slugwith the lowercase, hyphenated folder name):pnpm install pnpm i -g @nowly/cli nowly build your-service-slug nowly validate your-service-slug npx tsc --noEmit -p tsconfig.json
-
Use
nowly extension your-service-slugto generate a ready-to-load development extension, then load it in Chrome and exercise the relevant pages and activity states. Check that the activity shown in Discord is accurate and clears when it should. Build/metadata validation does not replace this manual check; publishing also needs the required images. Submit a pull request once the presence is ready for review.
The authoring guide covers metadata, locales, assets, SDK conventions, and alternative local packaging (nowly pack).
Use the broken-presence report. Include the platform, an example page URL, steps to reproduce, expected versus actual Discord activity, and browser/version details; attach relevant extension debug logs or screenshots if available. Do not include credentials or private browsing data.
Maintainers review proposals and pull requests; a proposal is not an automatic acceptance. Changes to the catalog are generated after qualifying merges, so contributions should update the presence source rather than the table above. For discussion and other repository issues, use GitHub issues.
This repository is licensed under the MIT License.