Where to Find Woodpecker CI Documentation and How to Contribute

Woodpecker CI's official documentation is reachable from its website, woodpecker-ci.org, which links to the docs and describes the project as an open-source, free CI/CD engine. The site states that Woodpecker "is and always will be totally free," that its source code is open-source so you can contribute, and that pipelines run in Docker containers with plugins available for extending pipeline features. If you want to start using it or help build it, the site itself is the entry point; the sections below cover what you'll find there and what to do next.

What Woodpecker CI Is

Woodpecker is a CI/CD engine built around Docker containers. Each pipeline step executes in a container, and when a normal Docker image isn't enough, you can write plugins to extend what a pipeline can do. The site also highlights multi-workflow support: you can define several workflows for one project, and they can depend on each other.

That combination — container-based steps, a plugin mechanism, and interdependent workflows — is the core of what the project offers, and it shapes both how you'd use it and how you'd contribute to it.

Finding the Documentation

The website is the starting point. From woodpecker-ci.org you can reach the project's docs, which cover how pipelines, plugins, and multi-workflow setups work. The site explicitly points readers to the docs for details on multiple workflows, so that's the place to go when you need configuration specifics rather than a general overview.

A practical path:

1. Open woodpecker-ci.org.
2. Follow the link to the documentation.
3. Read the pipeline and plugin sections first if you plan to run builds, or the workflow section if you need several pipelines that depend on each other.

Getting the Source and Contributing

Because Woodpecker's source code is open-source, contributing is a stated option on the site — the project invites you to "contribute to help evolving the project." The site doesn't spell out a contribution process in the material available here, so the concrete steps (where the repository lives, how to open issues or pull requests, coding conventions) come from the docs and the repository itself rather than the landing page.

If you want to contribute, the realistic sequence is:

• Read the docs to understand how pipelines, plugins, and workflows are structured.
• Locate the source repository through the links on the site.
• Start with the contribution guidance in the docs or repository before submitting changes.

What to Do Next

The site confirms three things you can rely on: Woodpecker is free and open-source, pipelines run on Docker containers, and plugins extend pipeline features. Anything beyond that — installation steps, exact configuration syntax, contribution rules — lives in the documentation and repository, which is where you should go next.