Skip to content

docs: reduce prominence of enterprise notes#457

Open
enyst wants to merge 5 commits intomainfrom
docs/soften-enterprise-contrib-notes
Open

docs: reduce prominence of enterprise notes#457
enyst wants to merge 5 commits intomainfrom
docs/soften-enterprise-contrib-notes

Conversation

@enyst
Copy link
Copy Markdown
Collaborator

@enyst enyst commented Apr 15, 2026

Summary

  • replace the prominent enterprise restriction warning on the contributing page with regular inline copy
  • soften the duplicate enterprise note in the License section

Why

The current message is important, but the warning callout makes it more visually prominent than needed on the contributing page. This keeps the guidance while reducing emphasis.

Notes

  • no tests run; docs-only change

This PR was created by an AI assistant (OpenHands) on behalf of the user.

Co-authored-by: openhands <openhands@all-hands.dev>
Copy link
Copy Markdown
Contributor

@all-hands-bot all-hands-bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🟢 Good taste - Sensible UX improvement that reduces unnecessary alarm while maintaining the same information. The shift from a warning callout to inline text with casual tone makes the contributing page more welcoming without losing clarity about the enterprise directory restriction.

Comment thread overview/contributing.mdx Outdated
Comment thread overview/contributing.mdx Outdated
Co-authored-by: openhands <openhands@all-hands.dev>
@mintlify
Copy link
Copy Markdown

mintlify bot commented Apr 15, 2026

Preview deployment for your docs. Learn more about Mintlify Previews.

Project Status Preview Updated (UTC)
all-hands-ai 🟢 Ready View Preview Apr 15, 2026, 8:42 PM

💡 Tip: Enable Workflows to automatically generate PRs for you.

Co-authored-by: openhands <openhands@all-hands.dev>
@enyst enyst changed the title docs: reduce prominence of enterprise contribution notes docs: reduce prominence of enterprise notes Apr 15, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants