Extensions: add FAQ section and make entry for notable extensions

[leggewie]

No description provided.

[coderabbitai]

Walkthrough

This pull request updates the documentation for Armbian extensions by modifying docs/Developer-Guide_Extensions.md. The change replaces a section heading with a FAQ section that includes references to example extensions (image-output-qcow2 and uboot-btrfs) and adds a new FAQ entry explaining how to opt out of specific hook functions using a Bash snippet (unset -f hook_name__individual_function), with a note that this approach is unofficially unsupported.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~5 minutes

This is a documentation-only change affecting a single file with structural reorganization and content additions. No code logic is present, and the changes are straightforward documentation updates.

Possibly related PRs

• Document the process of skipping/ignoring/opting-out of an individual hook function #842: Adds the same documentation about opting out specific hook functions in Developer-Guide_Extensions with identical Bash snippet guidance.

Suggested labels

size/small

Suggested reviewers

• igorpecovnik

Pre-merge checks and finishing touches

❌ Failed checks (1 inconclusive)

Check name	Status	Explanation	Resolution
Description check	❓ Inconclusive	No pull request description was provided by the author, making it impossible to assess whether it relates to the changeset.	Add a pull request description explaining the purpose of adding the FAQ section and why these extensions are notable.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title accurately describes the main changes: adding a FAQ section and documenting notable extensions in the Extensions documentation.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

---

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

Disabled knowledge base sources:

• Jira integration is disabled by default for public repositories

You can enable these sources in your CodeRabbit configuration.

📥 Commits

Reviewing files that changed from the base of the PR and between 217532a and 81718ae.

📒 Files selected for processing (1)

• docs/Developer-Guide_Extensions.md (1 hunks)

🧰 Additional context used

🪛 LanguageTool

docs/Developer-Guide_Extensions.md

[style] ~103-~103: If you’re making a request, consider inserting ‘please’ to sound more courteous and respectful.
Context: ...'ing of user extensions. ### FAQ #### Can you give me examples of some extensions shi...

(CAN_YOU)

🔇 Additional comments (3)

docs/Developer-Guide_Extensions.md (3)

101-115: LGTM! — Documentation enhancement looks well-structured.

The FAQ section adds practical value by providing concrete extension examples and clarifying how to opt out of specific hook functions. The content integrates well with the existing documentation and the tone is consistent.

Note: The static analysis tool flagged line 103 for politeness, but this is a false positive — the question format is appropriate for FAQ entries in documentation.

---

101-107: The extension links are external references to the build repository and do not need verification within the documentation repository.

The FAQ section correctly links to extensions in the armbian/build repository (github.com/armbian/build/blob/main/extensions/), not in the documentation repository. These are intended as external resource links. The documentation is functioning correctly by pointing developers to the actual extension implementations in the build repository.

---

108-115: The documentation already appropriately addresses the concern with an explicit "officially unsupported" disclaimer and recommends an alternative approach. Since this opt-out method is documented as officially unsupported, the documentation need not provide detailed verification of its effectiveness or guarantee timing behavior. The existing warnings and alternative recommendation are sufficient.

---

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.}

[EvilOlaf]

Perhaps mention the whole directory as well as those in armbian/os and/or armbian/community repository.