-
Notifications
You must be signed in to change notification settings - Fork 14
Help center: Custom CSS & head injection #416
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
Conversation
✅ Deploy Preview for bump-content-hub ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
It is not mandatory, but it is an option. Another option is to request us to apply those changes, as soon as they have a Business subscription. |
Yes, I explained it in the article (that we can also handle it). But I wanted to be sure that it was indeed a reverse proxy that was needed (and not a simple proxy) if they want to handle it. |
ChristopheDujarric
left a comment
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.
Overall, I think it's key to first think in terms of "what the users want to achieve", and then "how they can achieve it". They have at first no idea how it will work for them to track doc views with their Google Analytics, but that is precisely want they want to do.
|
I added your change requests @ChristopheDujarric 🙏 |
Hey!
I added a new section describing how to inject content into the
headtag, and the CSS variables that can be used.We had that listing in the Embed mode page, but I think it makes sense to also have it "standalone", as users might want to customize their docs without embedding it.
I also updated the list of CSS variables based on the recent rework we dit on it.
❓I need one confirmation: I wrote that a reverse-proxy is mandatory to inject these customization options (unless we handle it on our end for the client). ✅