Skip to content

Fix broken link to existing apps migration guide#390

Closed
Elishaokon13 wants to merge 6 commits intobase:masterfrom
Elishaokon13:master
Closed

Fix broken link to existing apps migration guide#390
Elishaokon13 wants to merge 6 commits intobase:masterfrom
Elishaokon13:master

Conversation

@Elishaokon13
Copy link
Contributor

What changed? Why?

Fixed broken link in the Mini Apps overview page. The link /mini-apps/quickstart/existing-apps/install was pointing to a non-existent file, causing a 404 error for users trying to learn about integrating existing web applications into Mini Apps.

Changed the link from:

  • /mini-apps/quickstart/existing-apps/install (broken)

To:

  • /mini-apps/quickstart/migrate-existing-apps (working)

This ensures users can properly access the migration guide for converting existing web applications into Mini Apps.

Notes to reviewers

  • Simple one-line fix correcting a broken internal link
  • The target file /mini-apps/quickstart/migrate-existing-apps.mdx exists and contains the relevant content
  • No content changes, just URL correction
  • This was referenced in the Note callout on line 9 of the overview page

How has it been tested?

  • ✅ Verified the target file /mini-apps/quickstart/migrate-existing-apps.mdx exists
  • ✅ Confirmed the broken link /mini-apps/quickstart/existing-apps/install was indeed non-existent
  • ✅ Tested the corrected link points to the correct migration guide
  • ✅ No other references to the broken path were found in the codebase

Fixes: #386

@cb-heimdall
Copy link
Collaborator

cb-heimdall commented Sep 25, 2025

🟡 Heimdall Review Status

Requirement Status More Info
Reviews 🟡 0/1
Denominator calculation
Show calculation
1 if user is bot 0
1 if user is external 0
2 if repo is sensitive 0
From .codeflow.yml 1
Additional review requirements
Show calculation
Max 0
0
From CODEOWNERS 0
Global minimum 0
Max 1
1
1 if commit is unverified 0
Sum 1

@ericbrown99
Copy link
Collaborator

Thanks, just saw this PR. We have a fix being merged now. Appreciate you taking the time to update this, will close since its a duplication

@Elishaokon13
Copy link
Contributor Author

Thank you, Eric!

madisoncarter1234 pushed a commit to madisoncarter1234/docs that referenced this pull request Oct 27, 2025
<!-- start pr-codex -->

## PR-Codex overview
This PR updates the documentation regarding the specifications for valid
frame URLs, particularly clarifying the role of the manifest file and
its optional nature.

### Detailed summary
- Clarified that a valid frame URL includes an embed tag in its HTML
`<head>` and may optionally include a manifest file.
- Changed wording to specify that frames should provide a JSON manifest
file at the URI `/.well-known/farcaster.json`.

> ✨ Ask PR-Codex anything about this PR by commenting with `/codex {your
question}`

<!-- end pr-codex -->
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