-
-
Notifications
You must be signed in to change notification settings - Fork 4.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
docs: Switch to Ethical Ads #18090
docs: Switch to Ethical Ads #18090
Conversation
✅ Deploy Preview for docs-eslint ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
@@ -4,6 +4,15 @@ | |||
} | |||
} | |||
|
|||
.docs-ad { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
we had a wrapper in the main page to avoid shift of content when ad pops up. Seems like docs didn't have it so added this.
We are ready to roll this out pending the removal of the unnecessary comments. |
Once merged, we should also merge this: eslint/eslint.org#522 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, thanks!
I'm leaving this open if @nzakas wants to take another look before merging, and because ideally this should be merged just before we start today's release so that the docs sites are updated around the same time (eslint.org/docs/head
right before and eslint.org/docs/next
right after the release).
What about eslint.org/docs/latest
? Looks like we should prepare another PR that should target the latest
branch?
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM. I'll let @mdjermanovic merge just before the release.
Since we've already merged #18102 and the new ads are live on |
Oops, yes. :) |
Prerequisites checklist
What is the purpose of this pull request? (put an "X" next to an item)
[x] Documentation update
[ ] Bug fix (template)
[ ] New rule (template)
[ ] Changes an existing rule (template)
[ ] Add autofix to a rule
[ ] Add a CLI option
[ ] Add something to the core
[ ] Other, please explain:
What changes did you make? (Give an overview)
Is there anything you'd like reviewers to focus on?
nope