fix(docs): remove duplicate unscoped community-rail CSS rules

[weizhoublue]

Overview:

Details:

the mobile-only rule bodies appear twice: once unguarded at the top level, once correctly wrapped in their @media blocks. CSS cascade order lets the unguarded copy win everywhere.

// line 2002
.dynamo-welcome__community {
  position: absolute;
  top: -20rem;
  right: calc((100vw - 1200px) / -2 + 1rem);
  z-index: 30;
  display: flex;
  width: 242px;
  flex-direction: column;
  gap: 0.55rem;
}

....

// line 2141
.dynamo-welcome__community {
    position: static;
    width: min(100%, 720px);
    margin: 2rem auto 0;
    flex-direction: row;
  }
....  
  

In result, desktop browsers (>1360px) get the narrow-screen sidebar layout instead of the floating rail, and hover/scroll animations are disabled for all users, not just prefers-reduced-motion users.

The solution is to delete the stray unguarded duplicate, keep only the properly @media-scoped versions.

Where should the reviewer start?

Related Issues

⚠️ This section is required. Choose one path below and delete the other.

🔗 This PR is linked to an issue:

• Closes #XXXX

🚫 This PR is NOT linked to an issue:

• Confirmed — no related issue

---

Summary by CodeRabbit

• Style
  • Removed duplicate responsive and reduced-motion styling for the community notification rail.
  • Preserved its responsive layout and transition behavior.

[copy-pr-bot]

This pull request requires additional validation before any workflows can run on NVIDIA's runners.

Pull request vetters can view their responsibilities here.

Contributors can view more details about this message here.

[github-actions]

🌿 Fern Docs Preview: https://nvidia-preview-019fca3e-a829-769f-b061-1c5b11f528c6.docs.buildwithfern.com/dynamo/dev

[coderabbitai]

Walkthrough

Changes

Community rail CSS cleanup

Layer / File(s)	Summary
Remove duplicate community rail rules docs/fern/components/LandingStyles.tsx	Removed duplicate community rail sizing, layout, and reduced-motion transition rules. The later responsive media queries remain.

Estimated code review effort: 1 (Trivial) | ~2 minutes

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Description check	⚠️ Warning	The description explains the bug and fix, but required sections remain incomplete, including reviewer guidance and the related-issue selection.	Complete the Overview and reviewer-start sections, and select either the linked issue or no-related-issue option instead of leaving placeholders.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Title check	✅ Passed	The title clearly identifies the removal of duplicate unscoped community-rail CSS rules.

---

_{Comment @coderabbitai help to get the list of available commands.}

[devin-ai-integration]

✅ Devin Review: No Issues Found

Devin Review analyzed this PR and found no bugs or issues to report.

[weizhoublue]

@dagil-nvidia , hi
Please help review whether this PR makes sense, thanks

[rmccorm4]

/ok to test 7742369

[dagil-nvidia]

Verified and correct. Thank you for catching this.

The duplicates are mine: restoring the community rail in #12539 appended its rules to the end of `LANDING_CSS`, and the extraction matched rule blocks inside @media queries as well as the media blocks themselves. Every responsive override got emitted twice, once correctly wrapped and once naked. The naked copies then won on source order, so position: static; width: min(100%, 720px) beat the real rail and it dropped into normal flow as full-width cards under the hero.

Checked the result: one unscoped .dynamo-welcome__community left (position: absolute; width: 242px), with the two responsive overrides still scoped to max-width: 1360px and max-width: 640px. That is the right shape.

The indentation on the removed rules is the tell, four spaces with the brace at two, which is what a rule looks like after it has been lifted out of its @media wrapper.