Adapted from WP main repo. Reviewed-on: #49 Co-authored-by: pat-s <patrick.schratz@gmail.com> Co-committed-by: pat-s <patrick.schratz@gmail.com>

- Add yamllint - Add markdownlint - Add precommit config - Add editorconfig - Rename `.yml` to `.yaml` - Add CI workflow to enforce lint rules Configs are taken from Woodpecker org lint rules. Reviewed-on: #39 Co-authored-by: pat-s <patrick.schratz@gmail.com> Co-committed-by: pat-s <patrick.schratz@gmail.com>

Reviewed-on: #30

I've been able to successfully make a NodeJS based CI solution to build pages for a static site using eleventy ([11ty.dev](https://11ty.dev)). ## Overview This process will make use of the following - Source repo to contain the source code - Destination repo that will be used to serve the pages - Codeberg CI (early access) - Secrets within the CI ## How it works Currently the `.Woodpecker.yml` file will live in your source codes repo, and have the build commands. Find more [here](https://codeberg.org/cjerrington/eleventy-base-blog-source/src/branch/main/.woodpecker.yml). For the CI we will start by using the node image, setup the secrets, and build commands. The use of secrets keeps your information secured and only accessed by the build system. This is beneficial for the email and access token. During the build, the pipeline will clone the source repo, then move into our commands. We will use the default build dir by 11ty of `_site`. The pipeline will clone our destination repo as _site, then set the remote url for the push after we run our install and build. Once built, it will change directory to the build site and perform our commit and push. ## Accessing the site On the remote repo we need the default repo to be named pages. This is also houw [Codeberg Pages](https://docs.codeberg.org/codeberg-pages/) setups up the access to what serves the pages we just built. You can follow their documentation on how to access your build site based on `username.codeberg.page`. Co-authored-by: Clayton Errington <me@claytonerrington.com> Co-authored-by: 6543 <6543@obermui.de> Reviewed-on: #23 Reviewed-by: 6543 <6543@obermui.de> Co-authored-by: Clayton Errington <cjerrington@noreply.codeberg.org> Co-committed-by: Clayton Errington <cjerrington@noreply.codeberg.org>