Skip to content

Conversation

@jvelasc2
Copy link
Contributor

@jvelasc2 jvelasc2 commented Oct 17, 2025

projects: wethlink: Added readme document

PR Type

  • Bug fix (change that fixes an issue)
  • New feature (change that adds new functionality)
  • Breaking change (has dependencies in other repos or will cause CI to fail)

PR Checklist

  • I have followed the Coding style guidelines
  • I have complied with the Submission Checklist
  • I have performed a self-review of the changes
  • I have commented my code, at least hard-to-understand parts
  • I have build all projects affected by the changes in this PR
  • I have tested in hardware affected projects, at the relevant boards
  • I have signed off all commits from this PR
  • I have updated the documentation (wiki pages, ReadMe etc), if applies

amiclaus
amiclaus previously approved these changes Oct 21, 2025
@buha
Copy link
Contributor

buha commented Oct 27, 2025

this one's a bit more particular than others, it has a proper doc on the wiki and that needs to be ported here:
https://wiki.analog.com/resources/eval/user-guides/admv96s-wgbe-ek1

if you search admv96s in wiki, you'll get 4 results, all of them need to be imported as sphinx doc, with the attachments

@jvelasc2
Copy link
Contributor Author

Hi @buha ,
I’ve converted all the HW and SW User Guide pages for the ADMV96S-WGBE-EK1 into RST format and compiled them into a single document within the README for the Wethlink example project.

Could you please confirm if this approach is okay? If there’s a preferred method or a better way to organize this documentation, I’d appreciate your guidance.

Thanks,
Joyce

@jvelasc2 jvelasc2 force-pushed the wethlink-proj-readme branch from cf626ac to 71d39a5 Compare November 10, 2025 04:11
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.

3 participants