nebari-dev / nebari-dev/nebari-docs

Update homepage

Open
#445 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

area: documentation 📖 impact: high 🟥
Dominant language
No language data
Stars
21
Forks
40
Avg merge
19h 50m
Merged PRs (30d)
6

Description

Preliminary Checks
Summary

Nebari homepage (https://www.nebari.dev) content was authored ~2 years ago. Nebari has changed and improved significantly since hence, and we should update the messaging accordingly.

Steps to Resolve this Issue

Non-exhaustive list of improvements:

  1. Add more details about "what" Nebari is, i.e., mention JupyterHub more clearly
  2. Cover https://github.com/nebari-dev/nebari-docs/issues/323
  3. Re-visit "why choose nebari" -- clearly note environment management
  4. Remove jitsi from integrations list
  5. Update the GIF to use new JHub Apps launcher
  6. Mention extensibility (plugin mechanism)
  7. In the deployment options, add bare metal and other supported options
  8. TBD

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the current homepage at https://www.nebari.dev and review nebari-docs issue #323 for related requirements. Update the messaging to cover JupyterHub, environment management, extensibility, deployment options, integrations, and the new JupyterHub Apps launcher GIF; the listed items and any finalized TBD requirements should be reflected when done.

Written by the indexing model from the issue text.

Assessment

Tech stack
jupyter
Domain
content, documentation
Issue type
Documentation
Difficulty
3/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.