How clockify/addon-examples works
Project type and purpose
• This is a monorepo of “addon” examples for the CAKE.com Marketplace integration with Clockify.
• Each top-level directory (hello-world-go, hello-world-java, iframe-example, pumble-notifications-java, ui-example, weather-example-serverless) is a standalone sample addon illustrating different languages, frameworks, and hosting models.
File structure
• Source code (Go, Java, Node.js)
• Manifest files (manifest.json or manifest-v0.1.json) describing the addon interface for CAKE/Clockify
• Static/UI assets in a public or static folder
• Docker/Docker Compose configs for containerized deployment
• README with setup instructions
• Patterns: Each addon is a small web service (HTTP server or serverless function) exposing two key endpoints:
a. A “manifest” API for the Clockify Marketplace to discover metadata and configuration UI
b. One or more “core” endpoints (UI templates, webhook handlers, business logic)
• Deployment scripts (Dockerfile, compose) & optional local dev proxies (Caddyfile, dev Dockerfile) enable consistent setup across examples.
Key insights from the README
• All examples share the same goal: demonstrate how to build a CAKE/Clockify addon.
• No single “system” that ties them together at runtime—they are independent micro-apps.
Elements
• Marketplace → GET /manifest
• Marketplace UI ↔ addon UI endpoints
• Clockify → POST webhooks
• Addon → Clockify REST API calls
• Addon → External API calls
• Frontend/UI (light blue)
• Backend/webhook handlers (green)
• Serverless functions (orange)
• External services (gray)
Detail is key
• Don’t attempt to merge all examples into one big block—treat each as a separate micro-app.
• Interface contracts (manifest, UI, webhook) for each service.
• Container boundaries or cloud boundaries if relevant (Docker vs. serverless).