-
Notifications
You must be signed in to change notification settings - Fork 17
Improve RFD site deployment for other orgs #189
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
base: main
Are you sure you want to change the base?
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
| script.defer = true; | ||
| script.setAttribute('data-domain', 'rfd.shared.oxide.computer'); | ||
| script.src = 'https://trck.oxide.computer/js/plausible.js'; | ||
| document.head.appendChild(script); |
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.
Should check this method isn't more aggressively blocked
|
|
||
| publicBanner: { | ||
| enabled: true, | ||
| learnMoreContent: ` |
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.
A little gross, but I ran into issues passing a ReactNode to the client
Enables other organizations to deploy and customize the RFD site while we continue upstream development. It'll still need a fork, but the overrides are localised so that merging upstream changes should be super easy.
Non-Vercel Deployment / Other Adapters
startscript for deployment.dockerignoreConfig System
site.config.tsfor organization customizationSiteConfigtype with organization identity, repository, search, banner, and feature flagsUI Updates
app/styles/overrides.cssfor custom styling