Fix landing page table and roadmap tags, lead Get involved with contribution - #289
Merged
Akshat0694 merged 4 commits intoSep 2, 2026
Merged
Conversation
The comparison table is ruled horizontally only and its cells start at the measure with no left padding, but Infima's defaults were still supplying a 1px border on all four sides of every cell plus zebra striping. The result was a bordered grid the design never asked for, with the text jammed against the vertical rules. Reset the borders, row backgrounds and display so border-collapse applies.
The tag trailed the title inline, so it landed wherever each title happened to stop and the four sat at four different offsets. Give it its own column so they line up down the strip, and fall back to the inline treatment on a phone, where the rows go full width and there is nothing to line up against.
The block promoted four links as equally weighted buttons, so nothing in it was ranked, and the loudest element was a star. Its own copy says a bug report is worth more than a star, so the layout was arguing against the text; starring is also not contributing. Give it one button, the good-first-issue list, and drop the rest to plain text running from the ask that takes real work down to the one that costs nothing. Promote the label to a heading, and caption the contributor row, which otherwise loses its label to that heading and reads as decoration.
Four clauses and forty-four words wrapped the announcement strip onto two lines, which is more than a banner gets read for. Keep the two things the tool is for and drop the rest, which the page it links to already covers.
larisoncarvalho
requested review from
Akshat0694,
arunim2405 and
refeed
as code owners
September 2, 2026 16:22
|
❌ The last analysis has failed. |
Codecov Report✅ All modified and coverable lines are covered by tests. 🚀 New features to boost your workflow:
|
Akshat0694
approved these changes
Sep 2, 2026
Akshat0694
added a commit
that referenced
this pull request
Sep 3, 2026
* docs: promote the new landing pages to the published site The pages built in tirith-internal as an isolated preview under documentation/new-landing-page/ become documentation/ itself, replacing the single-page landing site. Only documentation/ is built by deploy_docs.yml, so this is what makes them the published site rather than a preview nothing runs. The preview read the real site across a folder boundary. Those paths are now the site's own: staticDirectories drops to the default single root with the brand assets moved into documentation/static/img/, and the docs preset takes ./docs and ./sidebars.js directly rather than ../docs and ../sidebars.js. Five pages, replacing one: the landing page, Learn with the browser playground, Skills, At scale (the commercial page, previously Fleet), and the logo page reachable only from the landing footer. The Skills page instructs a reader to curl .claude/skills/tirith-policies/ and .cursor/rules/tirith-policies.mdc from this repository's main branch, and every file it lists links into that folder. Neither existed here, so the page shipped install instructions that 404. The skill pack is self-contained and meant to be copied into any project, so it moves here with the page that advertises it. docs/Tirith Logo.html comes across for the same reason: brand/README.md links to it as the source of truth for the mark's geometry, and three source files cite it. Its relative link is repointed for the shallower location. Also brings the public documentation the pages link to: editor-and-local.md, a link target the build would otherwise reject under onBrokenLinks: 'throw', plus the Bitbucket, Jenkins and pre-commit CI sections, the 1.2.0 install pins, and the issue-template links. deploy_docs.yml gains the PostHog and HubSpot environment. Every value is optional and unset means the analytics script never loads and the At scale form disables itself and says why -- which is the right behaviour on a fork. The documentation README was the stock Docusaurus scaffold telling readers to use yarn, which is wrong: package-lock.json is the committed lockfile and both docs workflows say so. It now describes the pages, the environment, the brand assets and the playground's documented limits. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> * docs: keep the stray yarn.lock out of the site folder The preview folder carried this rule in its own .gitignore; promoting it into documentation/ kept that folder's .gitignore, not the preview's, so the rule was lost. A `docusaurus start` then wrote a 352KB yarn.lock into documentation/, untracked and one `git add -A` away from being committed. That matters more than a stray file: package-lock.json is the committed lockfile, both docs workflows run `npm ci`, and a yarn.lock beside it invites exactly the resolve-fresh install the workflow comments warn against. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> * Add documentation for Tirith and update TUI banner text - Introduced llms.txt for comprehensive documentation on Tirith, covering installation, usage, policy writing, and integration. - Added a robots.txt file to manage crawler access and document intended policies. - Updated TUI banner and subtitle to reflect "Open-source IaC governance" instead of "Policy as Code". * Update banner text in app.py to reflect new branding * docs: update SKILL.md, debug-ci.md, install.md, pipelines.md, schema.md, validate.md, verdicts.md, and tirith-policies.mdc for clarity and accuracy * docs: enhance documentation for Tirith policies, including exit codes, validation methods, and pipeline integration * fix: clean up whitespace and formatting in generate-llms-full.py * feat: add contributor generation script and update contributor data in documentation * docs: update logo alt text for accessibility and improve button styles in roadmap * docs: update analytics configuration and remove deprecated HubSpot form references * Fix landing page table and roadmap tags, lead Get involved with contribution (#289) * fix: clear Infima's default table styling from the at-scale comparison The comparison table is ruled horizontally only and its cells start at the measure with no left padding, but Infima's defaults were still supplying a 1px border on all four sides of every cell plus zebra striping. The result was a bordered grid the design never asked for, with the text jammed against the vertical rules. Reset the borders, row backgrounds and display so border-collapse applies. * fix: align the status tags in the home page roadmap strip The tag trailed the title inline, so it landed wherever each title happened to stop and the four sat at four different offsets. Give it its own column so they line up down the strip, and fall back to the inline treatment on a phone, where the rows go full width and there is nothing to line up against. * style: lead the get involved block with contribution, not the star The block promoted four links as equally weighted buttons, so nothing in it was ranked, and the loudest element was a star. Its own copy says a bug report is worth more than a star, so the layout was arguing against the text; starring is also not contributing. Give it one button, the good-first-issue list, and drop the rest to plain text running from the ask that takes real work down to the one that costs nothing. Promote the label to a heading, and caption the contributor row, which otherwise loses its label to that heading and reads as decoration. * docs: cut the tirith ui banner to one line Four clauses and forty-four words wrapped the announcement strip onto two lines, which is more than a banner gets read for. Keep the two things the tool is for and drop the rest, which the page it links to already covers. --------- Co-authored-by: Larison Carvalho <larisoncarvalho@gmail.com> Co-authored-by: Claude Opus 5 <noreply@anthropic.com>
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
2 participants
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.
Pull Request Template
Description
What changes are being made?
table-layout: fixedand sized the middle column to its content, so the three columns are separated by even gutters (58–62px / 60px, previously 61px / 179px).6c6c811and restyled it: one button instead of four, promoted the label to a heading, and captioned the contributor row. The button is now the good-first-issue list rather than the star.tirith uibanner. Cut from 44 words to 17 so it stops wrapping onto two lines.Why are these changes necessary?
Which issues or tickets does this PR close or relate to?
Type of Change
Checklist
npm run buildpasses clean: no broken links, both bundles compile.Screenshots or Recordings (if applicable)
Verified in the browser rather than by eye alone; measurements at a 1280px viewport.
Table gutters hold across the desktop range: 58/60 at 880px (just above the 860px stacking breakpoint), 62/60 at 1280, 74/60 at 1500. No cell overflow and no horizontal scroll at the narrowest desktop width. Mobile stacking is unchanged.
Additional Information
docs/promote-landing-pages, notmain. Targeting that branch keeps this diff to the three files it actually touches. Againstmainit would drag in the whole promote-landing-pages changeset.6c6c811to pick up the contributor script, and force-pushed. The only commits replaced were earlier versions of the two commits in this PR; no one else's work was on the branch, and no PR was open at the time.Watch for releaseswas briefly dropped as duplicating the star, then kept. As a text link it no longer competes, and the note copy references it by name.