Skip to content

docs: fix C4A-Script documentation links in the tutorial READMEs - #2330

Open
pratikgx wants to merge 1 commit into
unclecode:developfrom
pratikgx:fix-c4a-script-doc-links
Open

pratikgx wants to merge 1 commit into
unclecode:developfrom
pratikgx:fix-c4a-script-doc-links

Conversation

@pratikgx

@pratikgx pratikgx commented Oct 3, 2026

Copy link
Copy Markdown

Summary

The "C4A-Script Documentation" and "API Reference" links at the end of both C4A-Script tutorial READMEs are broken.

  • docs/examples/c4a_script/tutorial/README.md: ../../md_v2/... resolves to docs/examples/md_v2/..., which doesn't exist. Now ../../../md_v2/....
  • docs/md_v2/apps/c4a-script/README.md: the same links resolve to docs/md_v2/md_v2/.... Since this copy already sits inside md_v2/, they're now ../../core/c4a-script.md and ../../api/c4a-script-reference.md. That also fixes them on the docs site, as the file is inside the mkdocs folder.

List of files changed and why

  • docs/examples/c4a_script/tutorial/README.md: fix 2 relative links
  • docs/md_v2/apps/c4a-script/README.md: fix 2 relative links

How Has This Been Tested?

Docs only. Both targets (docs/md_v2/core/c4a-script.md and docs/md_v2/api/c4a-script-reference.md) exist on develop, and every relative link in both files now resolves.

Checklist:

  • My code follows the style guidelines of this project
  • I have performed a self-review of my own code
  • I have commented my code, particularly in hard-to-understand areas
  • I have made corresponding changes to the documentation
  • I have added/updated unit tests that prove my fix is effective or that my feature works
  • New and existing unit tests pass locally with my changes

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.

1 participant