Skip to content

feat: sponsors#2967

Draft
alexdln wants to merge 6 commits into
npmx-dev:mainfrom
alexdln:feat/sponsors
Draft

feat: sponsors#2967
alexdln wants to merge 6 commits into
npmx-dev:mainfrom
alexdln:feat/sponsors

Conversation

@alexdln

@alexdln alexdln commented Jun 27, 2026

Copy link
Copy Markdown
Member

🔗 Linked issue

🧭 Context

📚 Description

@vercel

vercel Bot commented Jun 27, 2026

Copy link
Copy Markdown
Contributor

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
npmx.dev Ready Ready Preview, Comment Jun 28, 2026 8:44am
2 Skipped Deployments
Project Deployment Actions Updated (UTC)
docs.npmx.dev Ignored Ignored Preview Jun 28, 2026 8:44am
npmx-lunaria Ignored Ignored Jun 28, 2026 8:44am

Request Review

@coderabbitai

coderabbitai Bot commented Jun 27, 2026

Copy link
Copy Markdown
Contributor

Important

Review skipped

Draft detected.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: f2d4fa8c-ea4f-4aea-9e77-73e9b12fa9f0

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

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

@github-actions

github-actions Bot commented Jun 27, 2026

Copy link
Copy Markdown

Lunaria Status Overview

🌕 This pull request will trigger status changes.

Learn more

By default, every PR changing files present in the Lunaria configuration's files property will be considered and trigger status changes accordingly.

You can change this by adding one of the keywords present in the ignoreKeywords property in your Lunaria configuration file in the PR's title (ignoring all files) or by including a tracker directive in the merged commit's description.

Tracked Files

File Note
i18n/locales/en.json Source changed, localizations will be marked as outdated.
Warnings reference
Icon Description
🔄️ The source for this localization has been updated since the creation of this pull request, make sure all changes in the source have been applied.

@codecov

codecov Bot commented Jun 27, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ All tests successful. No failed tests found.

📢 Thoughts on this report? Let us know!

Comment thread i18n/locales/en.json
"name": "Gold",
"price": "$1,000/month",
"description": "Everything in Silver, plus:",
"benefit_1": "We display your name in the footer on every page.",

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

I think for now we can say that gold will get the logo displayed as Gold sponsor in /about and the home footer. And same for Silver. So same as we merged in main.

Comment thread i18n/locales/en.json
Comment on lines +1330 to +1331
"benefit_1": "We display your logo at npmx meetups and talks related to npmx, where event organizers allow it.",
"benefit_2": "We publish a dedicated article when sponsorship begins, plus follow-up articles after 6 and 12 months. We're also happy to help you write an article for your own blog and share any info you need."

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

I would say something like "Let's talk" as each of these bigger sponsoring relationship may be unique in what we do. I think we should display the logos of every sponsor (also silver and gold, smaller) if we show them in a slide in a talk (but it is good to be flexible and don't commit to always show them as it depends on the conference or meetup).

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.

2 participants