Repository navigation
docs(seo): cross-link docs pages to www how-to guides and fix footer privacy link - #262
Draft
nicolasiscoding wants to merge 2 commits into
Draft
nicolasiscoding wants to merge 2 commits into
nicolasiscoding wants to merge 2 commits into
Conversation
…privacy link Add a Learn more admonition to 20 docs pages pointing to their www.turbodocx.com/resources how-to counterpart, link the docs home to the free signature maker and the developer guides index, and point the footer Privacy Policy link at /termsofservice/privacy-policy instead of the Terms of Service URL.
The page says signature setups work for Word, PowerPoint and PDF, so the link text no longer limits it to Word or PowerPoint.
This branch was successfully deployed
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.
What changed and why
The docs site and www.turbodocx.com now link to each other. www pages can send readers and authority to the docs, and the docs can send readers to the shorter how-to guides on www.
:::info Learn moreadmonition near the top. Each one links to the matching how-to guide underwww.turbodocx.com/resources. For the three mapped URLs that point at a section anchor (signing order, image variables, Wrike reminders/voids), I put the admonition at the top of that section, not the top of the page, on purpose. The anchor text is the H1 of each www page, taken from TurboDocx/DotCom#425. One exception: the Signature-Setups-on-Templates box says "How to Save a Signature Setup on a Template" instead of the www H1 ("...on a Word or PowerPoint Template"). The docs page says setups also work for PDF templates, so the shorter text avoids contradicting the sentence right above the box. (Reviewer change; the DotCom#425 H1 may want the same fix.)https://www.turbodocx.com/termsofservice/privacy-policy, which returns 200 and is titled "Privacy Policy". That is also the URL the www footer uses (components/Footer.tsxon DotCom staging)./tools/digital-signature-maker). TurboDocx/DotCom#419 makes that the single owner URL for the signature-tool cluster./guides).All www links are plain URLs with no UTM parameters, matching the existing in-body www links in the docs.
Merge order
Merge this after TurboDocx/DotCom#425 is live in production. That PR ships the www how-to pages. When I checked today (2026-10-24), 19 of the 20 counterparts return 404:
The footer and home-page targets (
/termsofservice/privacy-policy,/tools/digital-signature-maker,/guides) are live today and return 200.Ticket checklist (Docs#256)
Overlap with open PRs
Several open PRs edit the same files. I placed each insertion away from their hunks so the merges should be clean:
:::noteblock, outside fix(seo): docs indexability fixes and query-matched page titles #260's changes.## Overviewand in the Reminders section, away from their hunks.Whichever PR merges second may still need a trivial rebase.
Verification run
setting-signing-order,image,reminders-re-sends-and-voiding-optional) exist in the live HTML.footerItems.jsonparses as valid JSON.git diff origin/develop -U0 | grep '^+' | grep —returns nothing). Existing em-dashes in these files are left alone: out of scope, and they would collide with the open PRs.<div>(Setting-up-TurboSign) and the section-level one (Additional-Information): each renders astheme-admonition-info, with no literal:::text./termsofservice/privacy-policy.Not verified
Owner questions
/tools/digital-signature-makeras "the free signature tool". Should it point to/free-electronic-signatureinstead? That page is the free plan for signing documents, which is a different offer.Part of #256
Closes #261