Update project links to point at current docs locations #719
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.
In the recent documentation reorg, we missed a couple of places where the old documentation project pages were referenced in surfaced content:
/docs/togaand/docs/briefcase/briefcaseand/project/briefcasepointed to/docs/briefcase(similar for toga, podium, and Python-Apple-support)projecttree were updated to point at adocsequivalent/docs/briefcaseproject page contained a reference tobeeware.readthedocs.ioas the tutorialThe last one was reported as #718.
Ultimately, in the current content layout, the old "project" pages (like
/docs/briefcase) should no longer exist. However, we can't completely remove them because so much of the page layout depends on having a database of "projects" to iterate over. This set of changes retains the project pages, but removes any links to them so they are at least hard to find; and if they are found, they'll point at correct content./me puts another notch in the "we need to get rid of lector" post...
Fixes #718
PR Checklist: