Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

🔗 Broken links found on developer.adobe.com (developer-distribute)

Open Beginner friendly
#56 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
75/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Domain
documentation

Research direction

Open src/pages/guides/zxp/coming-soon.md:79 and src/pages/guides/zxp/distribution.md:85, then check the reported external URL and its current destination. Update the broken references as appropriate so both links resolve successfully; the issue is done when the link-health check no longer reports either URL.

Written by the indexing model from the issue text.

Description

Automated link-health check for pages published under /developer-distribution/creative-cloud/docs (checked against prod).
2 link(s) in this repo's src/pages currently return a 404.

@melissag-ensemble — flagging you as this repo's most recent contributor.

Source (file:line) Type Broken link
src/pages/guides/zxp/coming-soon.md:79 external https://blog.developer.adobe.com/request-for-information-plugin-developers-please-help-us-merge-your-accounts-edfd2d408615
src/pages/guides/zxp/distribution.md:85 external https://blog.developer.adobe.com/request-for-information-plugin-developers-please-help-us-merge-your-accounts-edfd2d408615

False positive? Close this issue (a note on why, or a bug against AdobeDocs/adp-devsite-scripts, helps us fix the checker). We won't re-file these links — only genuinely new ones can reopen it. To disable the automated link-health check for this repository, add the label link-health: ignore.
Filed by adp-devsite-scripts/broken-link-bot. Updates each run; auto-closes when all links resolve.

Dominant language
JavaScript
Stars
2
Forks
18
PR merge metrics
No merged PRs in 30d

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from AdobeDocs/developer-distribute

All issues in AdobeDocs/developer-distribute

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.