fix: link Nish's daily reads from the homepage footer - #70
Conversation
tinystudio.io states it is run by one person, Nish, but never points back at the founder surface. Add a permanent, truthful footer attribution link labeled Nish's daily reads pointing at https://inish.in/, so product traffic and AI answers that cite the product can resolve who built it. No other page or surface changes.
![greptile-apps[bot]](https://avatars.githubusercontent.com/in/867647?s=60&v=4){kind=small}
There was a problem hiding this comment.
nish3451 has reached the 50-credit limit for trial accounts. To continue receiving code reviews, upgrade your plan.
|
Warning Review limit reached
Next review available in: 34 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Comment |
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: aa2ba535c8
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| <footer> | ||
| <span class="sc">TinyStudio · tinystudio.io</span> | ||
| <span class="sc">No revenue, ranking or booking guarantees. Only the work.</span> | ||
| <span class="sc">Nish's daily reads · <a href="https://inish.in/">inish.in</a></span> |
There was a problem hiding this comment.
At mobile widths up to 760px, this new inline anchor has only its roughly 13px text box as a hit area: public/index.css stacks the footer but provides no footer a padding, unlike the mobile footer rules used elsewhere. This regresses the site's established 44px mobile touch-target behavior specifically on the homepage, so the link needs an equivalent padded hit area.
Useful? React with 👍 / 👎.
There was a problem hiding this comment.
nish3451 has reached the 50-credit limit for trial accounts. To continue receiving code reviews, upgrade your plan.
…d live Round-5 re-verification of the mobile tap-targets finding. The 2026-08-09 fix (PR #48) held everywhere except one new element: PR #70 added the 'inish.in' link to the home-page footer, and index.css (the home page's standalone stylesheet) never received the shared.css footer rule — a 13px hit area at 390x844. Fixed and guarded in the previous commit; this receipt records the unfixed 13px measurement, the fixed 45px measurement for every page (all elements >=44px), desktop neutrality, the passing source guards and full suite, and the live measurements (deployment currently behind main, all live elements >=44px).
…-targets finding (#86) * fix(public): restore 44px home-page footer tap target (regression from #70) The 2026-08-09 tap-targets fix (PR #48) grew footer links inside shared.css, but the home page loads only index.css, whose mobile block lacked the footer rule. PR #70 (2026-08-11) then added the 'inish.in' footer link to the home page, shipping a 13px hit area at 390x844. Mirror the shared.css rule into index.css's mobile block and extend the check-site.mjs tap-target guard for index.css so CI catches it. Desktop footer (13px at 1280px) is untouched. * docs(evidence): re-verify tap-targets finding against current main and live Round-5 re-verification of the mobile tap-targets finding. The 2026-08-09 fix (PR #48) held everywhere except one new element: PR #70 added the 'inish.in' link to the home-page footer, and index.css (the home page's standalone stylesheet) never received the shared.css footer rule — a 13px hit area at 390x844. Fixed and guarded in the previous commit; this receipt records the unfixed 13px measurement, the fixed 45px measurement for every page (all elements >=44px), desktop neutrality, the passing source guards and full suite, and the live measurements (deployment currently behind main, all live elements >=44px).
…and #70 go live (#104) The deploy-lag item named 2e04225 as the stuck release sha with merged PR #56 (clean /audit canonical/og:url/JSON-LD) and #70 (homepage footer attribution) unreleased. The armed fleet-release pipeline shipped current main e6f42c1 (2026-08-11T10:49:53 IST); release-state pins e6f42c1, all five public pages diff byte-identical against live, /audit serves the four clean URL strings with 200/no-Location, / serves the #70 footer line, the round also carried #100 (retired app/api hosts now name The Website Appraisal) and #99, and npm test + both required GitHub checks pass on the head.
…nt main and live (2026-08-15) (#231) The 44px tap-target fix (PR #48, extended by #70) still holds on the current head: npm run check passes with the tap-target guard pinning the >=44px rules in all five stylesheets, and the full test suite passes (242 tests, 0 failures), including the narrow-viewport Chromium regressions from #174 and #176. Since the 2026-08-14 receipt (base 7ad776a), three commits touched the surface: #176 and #174 (index.css/shared.css layout-only changes that did not move any tap-target rule) and #202/#193 (llms.txt/offer.md text and URLs only). Fresh headless-Chromium full-element sweeps at 390x844 on a local static copy of public/ and on the live deployment show every standalone interactive element on all seven served pages is >=44px in height and width (logo 50, nav links 45, nav CTA 47, lead CTA 44, footer links 44-45, .back 45, in-content CTAs 46, Agent Desk controls 44-65.2); the only sub-44px elements are inline text links inside sentences (.xa1/.xi19/.xp1), exempt under the WCAG 2.5.8/2.5.5 Inline exception and intentionally excluded. All seven live pages serve 200 and match main element-for-element. The finding stays closed with no code change. Co-authored-by: nish3451 <nish3451@users.noreply.github.com> Co-authored-by: CommandCodeBot <noreply@commandcode.ai>
…#251) PR #194 added a <form class="lead two"> to public/pricing.html with bare <input> elements (no <label> wrapper, relying on aria-label). The existing tap-target rules in public/shared.css apply the padding:10px 18px 11px 24px hit area to form.lead.two label, not to bare inputs, so the two /pricing form inputs rendered at 19px tall — the same regression class PR #70 closed for the home-page footer link in 2026-08-11. Add a form.lead.two > input rule (mirrors the label padding, with min-height:44px and box-sizing:border-box to guarantee the hit area regardless of font rendering), and the same rule in the mobile breakpoint with the border-top separator that the label pattern uses. Extend scripts/check-site.mjs tapTargetCss to pin both needles (whole- file + mobile-block) so the regression cannot re-ship silently. Verified on the new main (d0daea9) with a fresh Playwright 1.62.1 session at 390x844: every standalone interactive element on every served page is now >=44px in both height and width — including the previously 19px /pricing form inputs, now 44px exactly. Only the WCAG-exempt inline text links (.xa1, .xi19, .xp1) remain under 44px, as recorded in the 2026-08-12 receipt. npm run check passes (removing the new shared.css needle from the guard fails it). Full npm test suite: 126 tests, 0 failures. Receipt: docs/evidence/tap-targets-2026-08-09.md (2026-08-20 entry) Report: .lane/reports/docs-tap-target-rereverify-2026-08-20.md Co-authored-by: minimax-vps <minimax-vps@noreply.tinystudio.io>
1 participant
Implements the cross-repo attribution item filed from the inish-site product scout (2026-08-09): tinystudio.io has natural attribution chrome ("Run by one person, Nish, who signs every audit") but no link back to the founder surface.
Verify once merged and deployed: curl -sL https://tinystudio.io/ contains an href to https://inish.in/.