Discuss Kit appears as a predecessor product name and as a current ARC reference package at blocklets/discuss-kit in the ARC monorepo. Use it to study a specific data and surface pattern. Do not use the name as proof that every historical Discuss Kit, forum, blog, wiki, bookmark, or messaging feature is available as a platform product today.
Continuity statement
| Claim | Status |
|---|---|
There is a current ARC package named discuss-kit | Yes — blocklets/discuss-kit |
| It demonstrates replicated posts/comments (and an anon collection) | Yes — replicated in blocklet.yaml |
It demonstrates pretty URL bindings onto /instance/app/content/posts | Yes — sites.bindings |
| It is used as a multi-layer test anchor for replication / board read / comments | Yes — package README lists runtime tests |
| Every legacy Discuss Kit product surface is platformized unchanged | No — not claimed |
| Media Kit, DID Connect UI, or other historical apps are implied by this package | No |
What the current package is for
From its own README and manifest (ARC tree, read-only reference):
- Role: Discussion board reference app (
scope: app) - Data:
replicatedcollections for posts, comments, and anonymous items with explicit roles and copy modes - Surfaces: AUP pages for list (
index) and detail (detail) with man pilots - Bindings:
/posts→ list AFS path;/posts/{slug}→ detail - Extras: declarative
cronfor scheduled post generation;indexdomain for instance-axis search;networkReadfor guest-readable content paths
Study the live files:
blocklets/discuss-kit/blocklet.yamlblocklets/discuss-kit/README.md.aup/pages andseed/content in the same package
What it is not
| Not this | Why it matters |
|---|---|
| A drop-in replacement guarantee for every old Discuss Kit deployment | Different runtime, data model, and product cut |
| Proof that "comments everywhere" is a global platform service | Collections are declared per package |
A starter recipe equivalent to arc blocklet create --recipe … | It is a full reference app with platform-test coupling |
| Permission to describe Media Kit or other kits as fully migrated | Separate evidence required per product |
How to learn from it without over-claiming
- Read
replicatedandsites.bindingsas a worked example of collection + URL design. - When building your own app, declare your collections and bindings — do not assume discuss-kit's paths.
- For third-party onboarding, prefer
minimal-appor Web Device first-site for the first green path; graduate to replication only when you need it. - Keep public docs language at "reference implementation of replicated discussion data / surfaces," not "the platform forum product."
Related reading
- Reference applications
- Data and AFS
- Package and instance
- Architecture lineage (when published on the architecture board) for name-mapping tables across historical products