fix: polish posts

mfocko · mfocko · commit 868bb9ba9533 · 2023-07-17T15:07:47.000+02:00
* add tags
* adjust headings
* formatting
* admonitions

Signed-off-by: Matej Focko &lt;mfocko@redhat.com&gt;
diff --git a/posts/2021-features/index.md b/posts/2021-features/index.md
@@ -1,9 +1,11 @@
 ---
 title: 2021 for Packit
 date: 2022-01-12T09:23:38+01:00
-draft: false
-weight: 97
 authors: flachman
+tags:
+  - 2021
+  - yearly-features
+  - summary
 ---
 
 # Packit project in 2021
diff --git a/posts/2021-in-numbers/index.md b/posts/2021-in-numbers/index.md
@@ -1,8 +1,11 @@
 ---
 title: 2021 in Numbers
 date: 2022-01-04
-weight: 98
 authors: flachman
+tags:
+  - 2021
+  - yearly-numbers
+  - summary
 ---
 
 # 2021 for Packit in numbers
diff --git a/posts/2022-features/index.md b/posts/2022-features/index.md
@@ -1,12 +1,13 @@
 ---
 title: "2022 for Packit"
 date: 2023-01-28T11:58:50+01:00
-weight: 91
 authors: flachman
+tags:
+  - 2022
+  - yearly-features
+  - summary
 ---
 
-## Packit project in 2022
-
 As you will see in the following paragraphs, the year 2022 was really fruitful for the Packit project. Without further ado, let’s take a look at what the Packit team accomplished last year!
 
 <!--truncate-->
diff --git a/posts/copr-srpms/index.md b/posts/copr-srpms/index.md
@@ -1,8 +1,10 @@
 ---
 title: Building SRPMs in Copr
 date: 2022-03-07T12:57:40+01:00
-weight: 96
 authors: lbarczio
+tags:
+  - srpm
+  - copr
 ---
 
 Let's find out how Packit builds your SRPMs in the Copr.
diff --git a/posts/downstream-automation/index.md b/posts/downstream-automation/index.md
@@ -1,8 +1,9 @@
 ---
 title: "Downstream automation is here"
 date: 2022-05-06
-weight: 95
 authors: flachman
+tags:
+  - propose-downstream
 ---
 
 # Downstream automation is here
diff --git a/posts/fas-verification-automation/index.md b/posts/fas-verification-automation/index.md
@@ -1,8 +1,9 @@
 ---
 title: "Automation of FAS verification in Packit Service"
 date: 2022-05-24
-weight: 94
 authors: lbarczio
+tags:
+  - fas
 ---
 
 As you may already know, for using Packit Service
diff --git a/posts/fedora-eln/index.md b/posts/fedora-eln/index.md
@@ -1,8 +1,9 @@
 ---
 title: "Working on the next major RHEL release, in your upstream repo"
 date: 2020-10-04
-weight: 99
 authors: ttomecek
+tags:
+  - downstream
 ---
 
 [Fedora EL Niño](https://docs.fedoraproject.org/en-US/eln/) (ELN) is such an
diff --git a/posts/manual-triggering/index.md b/posts/manual-triggering/index.md
@@ -1,8 +1,9 @@
 ---
 title: (Tests) job triggering improvements
 date: 2023-07-11T08:46:18+02:00
-weight: 88
 authors: lbarczio
+tags:
+  - configuration
 ---
 
 Recently, we received multiple contributions from the Strimzi team, specifically [Jakub Stejskal](https://github.com/Frawless)
diff --git a/posts/monorepos/index.md b/posts/monorepos/index.md
@@ -1,8 +1,9 @@
 ---
 title: Introducing monorepository support
 date: 2023-07-04T09:20:06+02:00
-weight: 89
 authors: lbarczio
+tags:
+  - monorepos
 ---
 
 We are very happy to announce a major enhancement to Packit! We have now added support for
diff --git a/posts/pre-commit-hooks/index.md b/posts/pre-commit-hooks/index.md
@@ -1,12 +1,11 @@
 ---
 title: "Packit's pre-commit hooks"
 date: 2023-05-16T11:00:00
-weight: 90
 authors: jpopelka
+tags:
+  - workflow
 ---
 
-## pre-commit
-
 [pre-commit](https://pre-commit.com) is a wonderful tool that saves you
 a lot of time by automatically checking your changes before you
 commit and/or push them out.
@@ -15,11 +14,12 @@ commit and/or push them out.
 
 For example, in our [packit repo](https://github.com/packit/packit/blob/main/.pre-commit-config.yaml)
 we run various hooks upon each commit:
-[Black (Python code formatter)](https://github.com/psf/black),
-[Prettier (code formatter)](https://github.com/prettier/prettier),
-[Flake8 (Python source code checker)](https://pypi.org/project/flake8),
-[Mypy (static type checker for Python)](https://github.com/python/mypy),
-and [several other pre-commit hooks](https://github.com/pre-commit/pre-commit-hooks).
+
+- [Black (Python code formatter)](https://github.com/psf/black),
+- [Prettier (code formatter)](https://github.com/prettier/prettier),
+- [Flake8 (Python source code checker)](https://pypi.org/project/flake8),
+- [Mypy (static type checker for Python)](https://github.com/python/mypy),
+- and [several other pre-commit hooks](https://github.com/pre-commit/pre-commit-hooks).
 
 ## Our pre-commit hooks
 
diff --git a/posts/pull-from-upstream/index.md b/posts/pull-from-upstream/index.md
@@ -1,8 +1,9 @@
 ---
 title: "Automatic pulling of upstream releases to Fedora"
 date: 2023-01-23T09:23:44+01:00
-weight: 92
 authors: lbarczio
+tags:
+  - downstream
 ---
 
 In the previous year, we [automated](/posts/downstream-automation) the Fedora downstream release process in Packit.
@@ -30,7 +31,6 @@ Let's now look at how to set it up and how it works.
 of a project. The bug is automatically created by
 [Upstream Release Monitoring](https://docs.fedoraproject.org/en-US/package-maintainers/Upstream_Release_Monitoring/).
 To enable the Upstream Release Monitoring:
-{{< columns >}}
 
 1. Add the upstream project (if it is not there yet)
    to [Anitya](https://release-monitoring.org/) and configure the mapping to a Fedora package:
@@ -40,17 +40,17 @@ To enable the Upstream Release Monitoring:
 
 ![Monitoring in dist-git](img/dist-git-monitoring.png)
 
-{{< /columns >}}
+:::info
 
-{{< hint info >}}
 In Anitya, there are multiple backends you can configure the mapping for.
 Besides GitHub or GitLab, you can use e.g. PyPI, pagure, or
 [many others](https://release-monitoring.org/static/docs/user-guide.html#backends).
 Also, be aware that there can be a delay in retrieving the new version,
 so the update to Fedora is usually not created instantly (e.g. for Python projects,
 it is better to configure PyPI backend rather than GitHub since the monitoring
 there is much less delayed).
-{{< /hint >}}
+
+:::
 
 ### Packit configuration
 
diff --git a/posts/release-field-handling/index.md b/posts/release-field-handling/index.md
@@ -1,12 +1,12 @@
 ---
 title: "Handling of Release field in propose_downstream job"
 date: 2023-05-23T12:00:00
-weight: 90
 authors: nforro
+tags:
+  - specfile
+  - propose-downstream
 ---
 
-## Handling of `Release` field in `propose_downstream` job
-
 We have recently made some fixes to the process of handling the `Release` field regarding the `%autorelease` macro, so let's take that opportunity to explain how it works.
 
 <!--truncate-->
diff --git a/posts/testing-farm-triggering/index.md b/posts/testing-farm-triggering/index.md
@@ -1,8 +1,9 @@
 ---
 title: "Running tests with builds from another PR"
 date: 2022-12-21
-weight: 93
 authors: fnecas
+tags:
+  - testing-farm
 ---
 
 Do you contribute to projects which depend on each other?
