Welcome to drydock Discussions!

[s-b-e-n-s-o-n]

Welcome to drydock Discussions!

Thanks for stopping by! This is the place to connect with the drydock community — whether you're monitoring a handful of containers on a home server or managing updates across a larger setup.

Here's how we use Discussions:

• Q&A — Stuck on a registry config, trigger setup, or migration from WUD? Ask here.
• Ideas & Feature Requests — Have a registry, trigger, or integration you'd like to see supported? Let us know.
• Show & Tell — Share your docker-compose setups, dashboards, or creative drydock configurations.
• General Chat — Anything container-update-related that doesn't fit in an issue.

A few ground rules:

• Be kind and constructive.
• Search existing discussions before opening a new one.
• Use Issues for confirmed bugs and actionable work — use Discussions for everything else.

Drop a comment below to introduce yourself — what are you running drydock on, and what registries/triggers are you using?

[Waler]

Hi, I would like to contribute with some PR's but I'm missing the documentation sources (like in WUD). And opening a PR without adding the required documentation for it feels wrong. Where are you keeping the documentation sources?

[s-b-e-n-s-o-n]

Hey @Waler, thanks for wanting to contribute — and for thinking about docs too!

There's a full CONTRIBUTING.md in the repo root covering setup, code style, testing, and pre-push checks.

The documentation source lives in content/docs/ in the repo and is published to https://drydock.codeswhat.com. So when you submit a PR, you can include doc changes in that directory alongside your code changes.

A few other things that'll help with PRs:

• Branch target: PRs should target main for bug fixes, or the active feature branch for new features
• Commit convention: Gitmoji + Conventional Commits — e.g. ✨ feat(registry): add xyz support
• Tests: 100% coverage thresholds are enforced in both app/ and ui/ — PRs need passing tests (npm test in app/, npm run test:unit in ui/)
• Linting: We use Biome — npm run lint from any workspace

Feel free to open a PR or ask here if anything's unclear!

[s-b-e-n-s-o-n]

Hey @Waler! Great question — and thanks for the test fix PR (#137).

Documentation sources live in two places in the repo:

1. content/docs/current/ — This is the source of truth for the published docs site at drydock.codeswhat.com/docs. These are MDX files organized by section (configuration, changelog, etc.).

2. README.md — The project README with quickstart, roadmap summary, and feature overview.

When submitting a PR that changes behavior or adds features, including the corresponding doc update in content/docs/current/ is always welcome. The docs are committed in-repo and consumed by the website app in apps/web/.

Let me know if you have questions about the structure!