Skip to content

docs(rock5b+): list Quectel LTE EC25 as a supported accessory#1928

Merged
Milir-Radxa merged 1 commit into
radxa-docs:mainfrom
tangzz-radxa:docs/rock5b-plus-accessories-ec25-20260713
Jul 13, 2026
Merged

docs(rock5b+): list Quectel LTE EC25 as a supported accessory#1928
Milir-Radxa merged 1 commit into
radxa-docs:mainfrom
tangzz-radxa:docs/rock5b-plus-accessories-ec25-20260713

Conversation

@tangzz-radxa

Copy link
Copy Markdown
Contributor

背景

客户在 support 邮件里问"ROCK 5B+ 支持什么 4G 模块"。我们 docs 里其实已经有 Quectel EC25-AU 的完整配置指南(docs/rock5/rock5b/getting-started/interface-usage/pcie-b-key.md),但只挂在「配件 / 外设」系列 (docs.radxa.com/accessories/peripherals/quectel-lte-ec25),没有出现在 ROCK 5B+ 自己的配件列表页 (docs.radxa.com/rock5/rock5b/accessories)。结果就是客户/同事打开 5B+ 配件页时根本看不到这个选项。

改动

docs/rock5/rock5b/accessories/README.md 的配件表格里「无线模块」分类下增加一行:

查看详情 暂时跳 docs guide 而非 radxa.com/products/...,原因是 radxa.com 主站目前没有 EC25 配件的产品页,等主站补上产品页之后可以再单独把链接换回去。

影响范围

  • 文件:
    • docs/rock5/rock5b/accessories/README.md(中文)
    • i18n/en/docusaurus-plugin-content-docs/current/rock5/rock5b/accessories/README.md(英文同步)
  • 仅 ROCK 5B+ 配件列表页
  • 不改其它产品
  • 不改 EC25 本身的配置文档

验证

  • python3 scripts/github_pr_guard.py check --repo-path ~/radxa-docs/contents --fetch → ok: true
    • 1 commit, 2 files, scope docs/rock5/rock5b
    • 中英双语都已更新
  • 渲染后表格新增 1 行,不会影响其他行

Add a 4G/LTE row in the ROCK 5B+ accessories table for the
Quectel LTE EC25-AU module. The 'view details' link points to
the M.2 B Key setup guide (pcie-b-key) since the radxa.com
product page for this accessory is not yet available.

This addresses a docs gap surfaced by a customer asking which
4G modules the ROCK 5B+ supports: the EC25 was only listed
under peripherals and not in the per-product accessories page.

Sync CN and EN.
@Milir-Radxa Milir-Radxa merged commit 284bb6d into radxa-docs:main Jul 13, 2026
3 of 6 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants