-
Notifications
You must be signed in to change notification settings - Fork 30
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
First draft Nebari landing page #207
Conversation
✅ Deploy Preview for nebari-docs ready!
To edit notification comments on pull requests, go to your Netlify site settings. |
Oh, also |
Hmm, how do we preview the landing page on Netlify with this redirect? Would it be better if I park it at |
Thank you, @gabalafou! This is looking really good!
I think we can have each section's background color be full-screen-width? @trallard can confirm :) Right now, it looks perfect on my macbook-screen, but I see the following on my monitor:
I clicked on the Nebari logo in the top left corner, and it took me to the landing page :) |
Oh nice, thanks for looking at this @pavithraes! I went ahead and made each section's background span the full page width. |
Hey @gabalafou, this looks great already 🎉 🙏🏽 thanks for working on this... now onto the known issues
Let's leave the header we have, as we need the search function
will get back to this tomorrow
Yeah there is no dark mode - I am not sure if we can remove the toggle on the home page only Re icons: I see the same as you, @gabalafou - will inspect the code + svgs tomorrow as it is too late for me now 😴 |
Scratch that. I was using some older pre-commit hook or something. For the record, when I first tried to run [ERROR] Cowardly refusing to install hooks with `core.hooksPath` set.
hint: `git config --unset-all core.hooksPath` Not knowing what that was about, I skipped it. Then I got errors when I tried to commit. Then I went back and ran the suggested |
Ah I have seen that |
@pavithraes or @kcpevey I cannot remember who was getting the screenshots for the main page - do we have this? we definitely need to replace the stock image in the landing page |
docs/src/pages/homepage.module.css
Outdated
} | ||
.getStartedLink2:hover { | ||
text-decoration: none; | ||
color: #fff; |
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.
is there a particular reason why you swap colour from --ifm-color-white
to #fff
?
I think the colour difference is barely there 👀
For the underline you can use --nebari-links-dark
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.
I'll look into it.
docs/src/pages/homepage.module.css
Outdated
justify-items: center; | ||
} | ||
|
||
.integrationsItem { |
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.
I am not sure why logos are rendering funnily - I wonder if having a div for the logo and a div for the name would make a difference?
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.
I'll give that a try.
I'm not sure, but maybe https://docusaurus.io/docs/next/api/themes/configuration#use-color-mode can help? |
I'm happy to get this. We need to create the demo video for PyData NYC, we can have a trimmed-version of that as a GIF for the landing page. |
Co-authored-by: Tania Allard <taniar.allard@gmail.com>
@pavithraes thanks for the tip! But I think what I need to do is add some override styles to the CSS, as the Styling and Layout - Dark Mode section of the Docusaurus docs suggests. |
@gabalafou you are correct there - e.g.
|
I went down a little rabbit hole. The reason the inline SVGs aren't working is because of the way Docusaurus has configured its SVG loader internally. Docusaurus uses the Webpack loader for SVGR. SVGR in turn uses SVGO. By default, SVGO minifies SVG ids. Some of these SVG logos uses internal identifiers. When those ids get minified to single characters (like "a", "b", "c"), they clash on the page. SVGO has an option to prefix ids, but Docusaurus has not turned that option on. I created a minimal reproduction of the bug. You can comment out one SVG at a time from the source code, and see that when only one SVG is on the page, it renders properly. But when both are on the page, one clashes with the other. I'm not sure how to fix it. I tried adding a plugin to Docusaurus that overwrites the Webpack config, but my attempt didn't work. I've opened an issue with Docusaurus: For now, I'm just going to replace the conflicting inline SVGs with |
- rename file: index.module.css - some alt text fixes - fix clashing logos - fix styles changing when dark mode is toggled on
docs/docusaurus.config.js
Outdated
{ | ||
label: "Home", | ||
position: "right", | ||
to: "/", | ||
}, |
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.
Maybe I should remove this until the home page is totally ready to deploy.
My original thinking was that I would build the Nebari landing page in two PRs. The first PR puts up a rough draft. The second PR polishes it. But it seems like we're going to fix everything in this PR before we merge it in? How would you prefer to go about this @trallard?
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.
I thought we had agreed to fix the background images + footer + dark/light colour inconsistencies in subsequent PRs to get this merged ASAP.
The one outstanding item would be to replace the mock dashboard #212 has discussions about this, and @pavithraes and I can sync about this tomorrow morning.
Right now, the images for the integrations - which was the main blocking for me seem to be working somehow. (tested in Brave - private and not, Safari and Chrome or maybe I got lucky).
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.
edit your img
fix did the trick
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.
Other than replacing the mock dashboard in the "Get started with nebari section" this can be merged and iterated over.
docs/src/pages/index.jsx
Outdated
@@ -142,16 +145,16 @@ export default function HomePage() { | |||
<div className={styles.platformsRight}> | |||
<ul className={styles.platformsList}> | |||
<li className={styles.platformsItem}> | |||
<AwsSvg /> |
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.
aha this seems to have made the trick!
docs/src/pages/index.jsx
Outdated
@@ -166,8 +169,8 @@ export default function HomePage() { | |||
href="/docs/category/get-started" | |||
className={styles.getStartedLink2} | |||
> | |||
Learn how to deploy a Nebari instance | |||
<RightArrowSvg /> | |||
Learn how to deploy |
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.
Did the "a nebari instance" bit get dropped on purpose?
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.
No, good catch!
@@ -2,18 +2,25 @@ | |||
|
|||
Styles for the Nebari home page | |||
|
|||
Note: only use color variables like --ifm-color-white in this file and not |
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.
nifty ✨ - and this gives us the correct colours all the time
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.
This looks amazing! Great work @gabalafou !
The only issue that jumped out at me was that the landing page was still redirecting to the old docs home page. I couldn't tell where the conversation left off on that and I know you're aware so I'll go ahead and approve.
This is my first draft at the Nebari landing page. I figured it would be better to get some code up now and then we can fix all of the outstanding issues in a subsequent PR.
Known issues: