diff --git a/content/codeberg-pages/pushing-output.md b/content/codeberg-pages/pushing-output.md
index b88cb77..f4dcab1 100644
--- a/content/codeberg-pages/pushing-output.md
+++ b/content/codeberg-pages/pushing-output.md
@@ -11,6 +11,8 @@ eleventyNavigation:
 If you are using a static site generator (SSG) and are satisfied with the result of your project on your local development
 environment, you can push the files to your Codeberg Pages repository.
 
+## Manual pushing
+
 To begin with, we will have two separate repositories, both locally and on Codeberg:
 
 - A main repository for the source files, i.e. where the source files related to your main project will be located.
@@ -89,3 +91,13 @@ request to merge it into the default branch. To learn more about pull requests,
 
 You should now be able to access your content by visiting https://{username}.codeberg.page.
 You can find more information in the [Codeberg Pages](/codeberg-pages/) section.
+
+## Using a CI
+
+Both the [Woodpecker CI](/ci/#using-codeberg's-instance-of-woodpecker-ci) and the [hosted Forgejo Actions](/ci/actions/) can be used to automate the build and deployment of your static website.
+
+For the Woodpecker CI, you can see the [existing example workflows in the `Codeberg-CI/examples` repo](https://codeberg.org/Codeberg-CI/examples), which provides examples for Jekyll, Hugo, Zola and many other popular SSG.
+
+Currently, we do not have any examples for the Forgejo Actions yet, but individual SSG tools might have details in their own documentation:
+
+- [Hugo docs on using Forgejo Actions for Codeberg Pages](https://gohugo.io/host-and-deploy/host-on-codeberg-pages/#automated-deployment-using-forgejo-actions)