Part of #86. Make the third-party connector path real and discoverable. ## Scope - "Writing a connector" guide on the docs site: `defineConnector`, auth spec, mounting, testing — using the reference connector from #87 as the worked example. - A discovery story: naming convention (`connector-*`) + a registry/listing page (mirror the Vike extensions listing model). - Link first-party connectors (GitHub, Drive) as canonical examples. ## Why Third parties shipping their own connectors is the payoff of the kit existing — orchestration stays the open, copyable layer.
Part of #86.
Make the third-party connector path real and discoverable.
Scope
defineConnector, auth spec, mounting, testing — using the reference connector from connectors: Phase 0 — @gemstack/connectors kit (contract + reference connector) #87 as the worked example.connector-*) + a registry/listing page (mirror the Vike extensions listing model).Why
Third parties shipping their own connectors is the payoff of the kit existing — orchestration stays the open, copyable layer.