docs: link the four remaining website guides from the README - #500
Open
DennisAlund wants to merge 1 commit into
Open
docs: link the four remaining website guides from the README#500DennisAlund wants to merge 1 commit into
DennisAlund wants to merge 1 commit into
Conversation
Each documented problem in the README now offers both links: Meta's canonical page, and the Flutter-specific answer on oddbit.id. Four Meta links had no guide beside them, so this completes the pairing across all six published guides. Added, one per location: - Documentation list, Meta App Events overview -> what Facebook App Events covers in Flutter - Setup step 2, client token -> where the Facebook client token goes - Swift Package Manager section -> SPM setup for this plugin - Dependencies on Facebook SDK -> which Facebook SDK version you actually get Meta's link stays visible next to each guide link. Pretending Meta has no documentation would cost credibility, and the README keeps the verdict in every case, so a reader who never clicks through is still unblocked. The existing shortlinks ikt, un7, s73, jex and rhg are deliberately unchanged. Every slug carries its own click counter, so reusing a README slug on the website, or a guide slug in the README, would merge guide click-through into the README baselines for exactly the destinations these guides exist to displace. The tagline on line 9 also links rhg and is left alone: it is positioning rather than a documented problem. Verified all six guide pages return 200 with full-size bodies, and that the four fbae-guide-* slugs resolve to the right destinations, checked through the shortener API rather than by fetching the slugs so the baseline counters stay clean.
Contributor
There was a problem hiding this comment.
Pull request overview
This PR updates the repository README to link four remaining Flutter-specific website guides next to the corresponding existing Meta documentation links, completing the README-side cross-linking for all published guides.
Changes:
- Adds a Flutter-specific guide link alongside the Meta “App Events overview” link in the Documentation section.
- Adds Flutter-specific guide links for: client token placement/diagnosis, Swift Package Manager setup, and resolved Facebook SDK version behavior.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Completes the README side of the website guide programme. Four Meta links had no Flutter-specific answer beside them; now all six published guides are linked from the problem they solve.
What changed
rhgfbae-guide-app-eventsjexfbae-guide-client-tokens73fbae-guide-spmikt,un7fbae-guide-sdk-versionsSix lines added, one line modified. No code, no version change.
Rules followed
rhgand is deliberately untouched: positioning, not a documented problem.Measurement integrity
The existing shortlinks
ikt,un7,s73,jexandrhgare unchanged. Every slug carries its own click counter, so reusing a README slug on the website, or a guide slug in the README, would merge guide click-through into the README baselines for exactly the destinations these guides exist to displace. The fourfbae-guide-*slugs were all at 0 clicks when this branch was cut, giving a clean before-number for the 30-day read.Verification
fbae-guide-*slugs exist as custom primary slugs pointing at the right guide URLs. Checked through the shortener API, not by fetching the slugs, so no counters were polluted.Note for the maintainer
docs/WEBSITE-HANDOFF-2.mdstates "NoCo-Authored-Bytrailer in commit messages, per this repo'sCLAUDE.md".CLAUDE.mddoes not say that, and recent commits (995e069,09902dc,3ab9184) all carry the trailer. This commit follows the handoff and omits it, per maintainer decision. Worth either recording the rule inCLAUDE.mdor correcting the handoff, so the next person does not hit the same ambiguity.