Add Nebari landing page

[trallard]

Reference Issues or PRs

#182

What does this implement/fix?

Put an x in the boxes that apply

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds a feature)
• Breaking change (fix or feature that would cause existing features to not work as expected)
• Documentation Update
• Code style update (formatting, renaming)
• Refactoring (no functional changes, no API changes)
• Build related changes
• Other (please describe):

Testing

• Did you test the pull request locally?
• Did you add new tests?

Documentation

Access-centered content checklist

Text styling

• The content is written with plain language (where relevant).
• If there are headers, they use the proper header tags (with only one level-one header: H1 or # in markdown).
• All links describe where they link to (for example, check the Nebari website).
• This content adheres to the Nebari style guides.

Non-text content

• All content is represented as text (for example, images need alt text, and videos need captions or descriptive transcripts).
• If there are emojis, there are not more than three in a row.
• Don't use flashing GIFs or videos.
• If the content were to be read as plain text, it still makes sense, and no information is missing.

Any other comments?

[gabalafou]

I have some review remarks, but I'm not familiar enough yet with this repo to really review this PR.

I checked the preview deploy URL. I didn't spot any broken links, but I didn't check thoroughly.

All in all, these changes make sense to me.

[trallard]

To clarify - this PR is for you @gabalafou to work off or the landing page (rather than reviewing the PR thoroughly).
Mostly since adding the landing page requires changes to how we handle other routes on the site (and cannot be done directly in main as we have no landing page right now).

No need to check for broken links manually as our build setup will throw any broken links automatically.

[pavithraes]

Notes from our discussion from Friday.

It'll be good to merge this PR soon because we introduce the /doc subdirectory here that impacts all of our cross-links. :)

Adding it to the milestone!

[gabalafou]

Okay, so I'm taking over this PR. I'm going to fix the merge conflicts now. Then shall we merge it in?

[trallard]

It's not ready for merge as is - would need to add an interim landing page. Or the final landing page.

I can deal with conflicts.

[gabalafou]

@trallard I already fixed the conflicts. 🪄😃 Is there a way we can change this PR so that it both creates a space for me to work in while I build the landing page but without replacing the existing landing page? That way we can merge this PR in sooner rather than later?

[netlify]

✅ Deploy Preview for nebari-docs ready!

Name	Link
🔨 Latest commit	418c140
🔍 Latest deploy log	https://app.netlify.com/sites/nebari-docs/deploys/635bf19746f588000b317610
😎 Deploy Preview	https://deploy-preview-184--nebari-docs.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site settings.

[trallard]

@trallard I already fixed the conflicts. 🪄😃 Is there a way we can change this PR so that it both creates a space for me to work in while I build the landing page but without replacing the existing landing page? That way we can merge this PR in sooner rather than later?

Ok I had to do some work on the configuration + add redirects to have a "hidden" landing page.
But that means we can merge and you can start working off main 🥇

@kcpevey and/or @pavithraes - this allows us to merge right now and have the foundation for Gabriel to work on the landing page.

Also this Closes #199

[kcpevey]

Looks good to me! Just had a few comments/suggestions

[pavithraes]

🎉