Greetings,
I have been using Hugo and hosted Forgejo Actions to publish the static site to Codeberg Pages, and I noticed that there's no instructions on automatic deploy with custom domain. It's worth noticing that `.domains` file should be placed at the `static` directory for Hugo, and accordingly for other SSGs, instead of root of source repository, in order to preserve it to the output branch. I will also initiate a PR to Hugo documents regarding the sample Forgejo Action `hugo.yaml` setup.
Reviewed-on: https://codeberg.org/Codeberg/Documentation/pulls/644
Reviewed-by: Bastian Greshake Tzovaras <gedankenstuecke@noreply.codeberg.org>
Co-authored-by: freyalin <xlin@mailbox.org>
Co-committed-by: freyalin <xlin@mailbox.org>
In #601, the suggestion was made to provide details on how to use a CI to get a website published to Codeberg Pages when using a static site generator.
We already provide a lot of details on that via the Woodpecker CI examples repo, so I've linked to that to help people find those details!
Reviewed-on: https://codeberg.org/Codeberg/Documentation/pulls/628
Reviewed-by: Gusted <gusted@noreply.codeberg.org>
Co-authored-by: Bastian Greshake Tzovaras <bgreshake@googlemail.com>
Co-committed-by: Bastian Greshake Tzovaras <bgreshake@googlemail.com>
- Formatting fixes, relevant text adjustments
- Some more complicated cases (e.g. attribution), as well as outdated
information that should be removed in a later commit were
deliberately left unchanged.
- Some minor mistakes (speling, trailing whitespaces, punctuation)
in the admonition boxes were also fixed.
How to implement [Docs-as-Code](https://docs-as-co.de/) with the help of Sphinx and Codeberg Pages.
Co-authored-by: Faycal Alami-Hassani <ka2in@protonmail.com>
Reviewed-on: https://codeberg.org/Codeberg/Documentation/pulls/198
Co-authored-by: ka2in <ka2in@noreply.codeberg.org>
Co-committed-by: ka2in <ka2in@noreply.codeberg.org>
