Link the security policy from the site footer - #2
Open
FurkaanBoraa wants to merge 1 commit into
Open
Conversation
The site made security claims (no network access, no analytics, one readable source file) with nowhere to send a reader who wanted the detail. SECURITY.md is now that detail, so it should be reachable from the page. Placed in the footer next to "Source on GitHub" rather than in a new section: the two links point at the same repository and belong together, and a policy link is what a footer is for. The site has no top nav to add it to — the header is a brand row with a single link.
This was referenced Jul 20, 2026
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
1 participant
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.
Answers question 4 from the 8-PR mail — you said yes, so here it is.
The page already makes security claims: "No network, no analytics" in the hero facts, "Honest & auditable" in the features grid, and an FAQ answer about the Accessibility permission. Until now none of them led anywhere.
SECURITY.mdis the long form of exactly those claims, so a reader who wants to check rather than trust now has a way through.Placement
Footer, immediately after Source on GitHub:
Both links point at the app repository, so they read as a pair. A policy link is also conventionally a footer link — that is where people look for it, and GitHub itself files
SECURITY.mdunder the repo rather than the front door.No new section, and no top nav to add it to: the header is a brand row with one link (
github.com/RectZones ↗), and turning that into a menu for a single addition would be a bigger change to your design than the link is worth.The href is cross-repo (
RectZones/RectZones/blob/main/SECURITY.md) — deliberate. The policy lives with the code it describes; copying it into this repo would give us two versions to keep in sync and one of them would eventually be wrong.Verification
Served the built page locally and clicked the link in a browser rather than only reading the diff:
footer a— muted + underline, identical to its siblingshttps://github.com/RectZones/RectZones/blob/main/SECURITY.md, page rendersNo CSS changed — the existing
footer arule covers it, so there is nothing new to maintain.Two things for you to decide, not done here
Contextual links. The "Honest & auditable" card and the "What permissions does RectZones need?" FAQ answer are where a security-minded reader actually is when the question forms; the footer is where they end up only if they keep scrolling. Linking from one or both would catch them earlier. I left it alone because you said match the existing structure, and I would rather you choose than find extra links in your copy.
The site still says "one Objective-C file" — hero facts, the Honest & auditable card body, and the FAQ permissions answer all say it. After #8 that is no longer true: the logic moved out of
main.m, andsrc/now holdsmain.m,rzcore.mandrzcore.h. Small, but it is a factual claim on a page that trades on being checkable, and it now sits one click from a security policy. Out of scope for this PR; happy to open a separate one.Note
Opened from a fork — I have
pullonly on this repo. This is the second one through that route; the first was the Railway 301.