Update CI documentation to reflect automated target generation

[igorpecovnik]

This PR updates the CI documentation to reflect the changes introduced in armbian.github.io#184, which moved target generation from template-based to automated generation from image-info.json.

Changes

Added monitoring page notice

• Prominent note about https://actions.armbian.com/ for monitoring all action scripts

Updated target generation section

• References moved from armbian/os to armbian/armbian.github.io
• Added explanation of automatic target generation from image-info.json
• Listed all 4 generated target files with their purposes

New hardware-based classification section

• Added detailed table explaining board categories
• Listed complete slow hardware criteria
• Explained desktop selection (GNOME for fast, XFCE for slow)

Automatic extensions documentation

• Documented v4l2loopback-dkms and mesa-vpu for fast HDMI boards
• Explained that manual extensions merge with automatic ones

Updated manual overrides section

• Corrected paths for blacklist files (now in release-targets/)
• Added manual targets (.manual files) documentation
• Updated extensions map format and wildcard usage

Updated all file path references

• Changed from userpatches/targets-*.yaml to release-targets/targets-*.yaml
• Changed from armbian/os to armbian/armbian.github.io repository
• Removed references to template files (no longer used)

The documentation now accurately reflects the new automated target generation system with hardware-based desktop selection and proper categorization of boards.

Related to: armbian/armbian.github.io#184

Documentation website preview will be available shortly:

 Open WWW preview 

[coderabbitai]

Warning

Rate limit exceeded

@igorpecovnik has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 0 minutes and 18 seconds before requesting another review.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

Walkthrough

Updated CI process documentation (docs/Process_CI.md) to replace template-based target generation with image-info.json-driven target YAML generation (generate-targets.yaml); restructured hardware board classification into categories (Fast HDMI, Slow HDMI, Headless, RISC-V, LoongArch); introduced automatic extensions with an extensions map format and manual overrides (blacklisting/manual targets); replaced workflow/generated file path references with armbian.github.io release-targets paths; corrected terminology and removed legacy sections; and relaxed WeasyPrint in requirements.txt from weasyprint==68.0 to weasyprint>=60.0.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Possibly related PRs

• armbian/documentation PR 789 — Modifies the Process_CI.md Extensions area (adds kernel-description.json) and is closely related to this PR’s extensions/map and merging changes.

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title 'Update CI documentation to reflect automated target generation' directly and clearly summarizes the main change: updating documentation to reflect the shift from template-based to automated target generation.
Description check	✅ Passed	The description is comprehensive and directly related to the changeset, detailing all major documentation updates including monitoring notices, target generation changes, hardware classification, extensions documentation, and file path updates.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch update-ci-documentation

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 1

🤖 Fix all issues with AI agents

In `@docs/Process_CI.md`:
- Around line 74-105: Update the fenced code blocks to include a language
identifier (yaml) and ensure there is a blank line before and after each fence;
specifically modify the blocks containing the lines
"release-targets/targets-release-nightly.blacklist" /
"release-targets/targets-release-community-maintained.blacklist",
"release-targets/targets-release-nightly.manual" /
"release-targets/targets-release-community-maintained.manual",
"release-targets/targets-extensions.map", and the blocks under "Format:",
"Example:" and "Wildcards apply to all branches:" so each uses ```yaml and is
separated from surrounding text by a blank line on both sides to satisfy
MD031/MD040.

[coderabbitai]

Actionable comments posted: 1

🤖 Fix all issues with AI agents

In `@docs/Process_CI.md`:
- Line 103: Add a blank line immediately before the "### Kernel Descriptions for
Download Pages" heading so the Markdown has an empty line separating the
previous paragraph/block and the heading; locate the heading text "### Kernel
Descriptions for Download Pages" and insert one newline above it.

♻️ Duplicate comments (1)

docs/Process_CI.md (1)

87-99: Fix code block formatting (already flagged).

The code blocks are missing language identifiers (yaml) and blank lines before/after. This issue was already identified in a previous review.