Built with Astro, hosted on Hetzner behind Cloudflare. Domain registered in 2026.
tinycld.org is built with Astro, hosted on Hetzner behind Cloudflare. It measures traffic with Umami. It sends email through Postmark.
| Technology | Version | First seen |
|---|---|---|
| JavaScript Frameworks & Libraries1 | ||
| – | 6 Nov 2026 | |
| CDN & Hosting2 | ||
| – | 6 Nov 2026 | |
| – | 6 Nov 2026 | |
| Analytics & Tag Management1 | ||
| – | 6 Nov 2026 | |
| Transactional Email1 | ||
| – | 6 Nov 2026 | |
| Fonts & Icon Fonts1 | ||
| – | 6 Nov 2026 | |
Registration from the registry's RDAP record, the certificate the site serves, and its rank in public traffic lists.
The crew hasn’t read this site’s colors yet. We read a palette when we capture a site’s screenshot, busiest sites first. Meanwhile, browse palettes from other sites.
tinycld.comkevin.ns.cloudflare.comhope.ns.cloudflare.comv=spf1 include:spf.mtasv.net ~allv=DMARC1; p=none; rua=mailto:postmaster@tinycld.org# TinyCld docs > Developer documentation for extending @tinycld/core and authoring feature packages. Each entry below links to the raw markdown source. For the complete docs inlined into a single file, see https://tinycld.org/llms-full.txt. ## Developer guidelines - [tinycld/CONTRIBUTING.md](https://github.com/tinycld/tinycld/blob/main/CONTRIBUTING.md) - code style, patterns, data-query conventions, form rules, and routing/org conventions for @tinycld/core and package authors. ## Overview - [Documentation](https://tinycld.org/docs/index.md) - Pick your path - operate a TinyCld instance, or build packages on top of it. - [Install TinyCld](https://tinycld.org/docs/installation.md) - Host TinyCld yourself — one Docker container on a small Linux VM, or a single binary on Linux, macOS, or Windows. Ready in about 15 minutes. - [Command line tool](https://tinycld.org/docs/command-line-tool.md) - Download the tinycld CLI from your server, log in from a terminal, and script Drive, Mail, Boards, Contacts, Calendar, and comments. - [Automation rules](https://tinycld.org/docs/automation-rules.md) - Build rules that react to things happening in your workspace — file mail, notify yourself, create events — and run on the server whether the app is open or not. - [Optional packages](https://tinycld.org/docs/optional-packages.md) - Packages that are not part of the default install, what they add, and how to add them from Settings → Packages. - [Getting started](https://tinycld.org/docs/getting-started.md) - Assemble a TinyCld workspace, run the dev loop, and learn how the workspace, core, the app shell, and feature packages relate. - [Adding a package](https://tinycld.org/docs/adding-a-package.md) - Bring an existing feature package into your workspace as a member. - [Creating a package](https://tinycld.org/docs/creating-a-package.md) - Scaffold a new TinyCld feature package with npx @tinycld/bootstrap. - [Conventions](https://tinycld.org/docs/conventions.md) - The rules every TinyCld package follows - collection naming, data access, state, imports, and style. - [The generator](https://tinycld.org/docs/generator.md) - What tinycld/scripts/generate.ts does on every install and dev, and the files it produces. - [FAQ](https://tinycld.org/docs/faq.md) - Why the TinyCld ecosystem is shaped the way it is — the design decisions behind the per-developer workspace, the independent package repos, and the absence of a committed lockfile. - [Go server extensions](https://tinycld.org/docs/go-server.md) - How packages ship Go code that the app shell's PocketBase server loads at startup. - [Troubleshooting](https://tinycld.org/docs/troubleshooting.md) - Common failure modes when adding, generating, and building packages, with fixes. ## Package anatomy - [Manifest](https://tinycld.org/docs/anatomy/manifest.md) - Every field a package manifest can declare, and what each one wires into the app shell. - [Screens](https://tinycld.org/docs/anatomy/screens.md) - How package screens become Expo Router routes inside the app shell. - [Collections](https://tinycld.org/docs/anatomy/collections.md) - How a package declares PocketBase collections and integrates them with pbtsdb's type system. - [Settings](https://tinycld.org/docs/anatomy/settings.md) - How a package contributes entries to Personal Settings. - [Sidebar slots](https://tinycld.org/docs/anatomy/sidebar-slots.md) - How one package contributes UI into another package's sidebar. - [Event sources](https://tinycld.org/docs/anatomy/event-sources.md) - How one package contributes a read-only event feed to another package's grid. - [Automation](https://tinycld.org/docs/anatomy/automation.md) - Declare triggers and actions so users can build workflow rules on your package's events. - [Server](https://tinycld.org/docs/anatomy/server.md) - How a package ships a Go server extension that the app shell's PocketBase loads on boot. - [Seed](https://tinycld.org/docs/anatomy/seed.md) - How a package ships sample data for local development. - [Tests](https://tinycld.org/docs/anatomy/tests.md) - How a package's unit and e2e tests are discovered and run via the tinycld-pkg CLI. ## Tasks - [Routing](https://tinycld.org/docs/tasks/routing.md) - Navigate between screens with useOrgHref or appHref instead of literal paths, so the app's /a route prefix has one definition. - [PocketBase auth rules](https://tinycld.org/docs/tasks/auth-rules.md) - Add listRule, viewRule, createRule, updateRule, and deleteRule to your collection migrations — owner-scoped, member-scoped, or public — so non-superuser inserts and queries don't fail. - [Query data](https://tinycld.org/docs/tasks/query-data.md) - Read from PocketBase inside a package using useOrgLiveQuery (scoped to the signed-in user) and pbtsdb collections. - [Mutate data](https://tinycld.org/docs/tasks/mutate-data.md) - Write to PocketBase with generator-based mutations that await pbtsdb transactions. - [Forms](https://tinycld.org/docs/tasks/forms.md) - Build forms with react-hook-form, zod validation, and the themed input components from @tinycld/core. - [UI state](https://tinycld.org/docs/tasks/ui-state.md) - Share UI state across components with Zustand stores, with optional AsyncStorage persistence. - [Logging](https://tinycld.org/docs/tasks/logging.md) - Log from the client with the core `log` API and from Go with logging.ForPackage — both feed Sentry and neither is console.*. - [Theming](https://tinycld.org/docs/tasks/theming.md) - Use semantic tokens instead of raw colors so your package works in both light and dark mode. - [In-app help](https://tinycld.org/docs/tasks/in-app-help.md) - Ship help topics with your package and surface them from the UI so users can find them. ## Reference - [Manifest schema](https://tinycld.org/docs/reference/manifest-schema.md) - Every field on a package manifest, with types and requirements. - [bootstrap CLI](https://tinycld.org/docs/reference/cli.md) - Reference for npx @tinycld/bootstrap, the package scaffolder and workspace assembler. - [tinycld CLI reference](https://tinycld.org/docs/reference/cli-reference.md) - Every command, flag, and scope in the tinycld command line tool, plus how a package contributes its own command group. - [Generated files](https://tinycld.org/docs/reference/generated-files.md) - Every file the generator produces, what it contains, and how to regenerate it.