Skip to content

docs(providers): add provider stubs and support matrix#685

Open
khuyentran1401 wants to merge 8 commits into
mainfrom
docs/provider-stubs
Open

docs(providers): add provider stubs and support matrix#685
khuyentran1401 wants to merge 8 commits into
mainfrom
docs/provider-stubs

Conversation

@khuyentran1401

@khuyentran1401 khuyentran1401 commented Jun 10, 2026

Copy link
Copy Markdown
Collaborator

Reference Issues or PRs

Fixes #629.

The support matrix links to a Hetzner page that #679 introduces, so #679 should merge first to keep the broken-link check green.

What does this implement/fix?

  • Adds a Providers section with a support matrix landing page that shows which deploy targets are usable today (AWS, Hetzner) and which are planned (GCP, Azure, Local), linking each to its page.
  • Adds stub pages for the three planned providers, each carrying a uniform "Planned, not yet implemented" banner that links to its scaffolding and invites contributions.
  • Extracts that banner into a shared <PlannedProvider /> component so the three pages cannot drift apart.
  • Shortens the AWS page title to "AWS" for sidebar consistency.

Testing

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

Verified locally by building the docs and confirming the Providers section, matrix links, and the shared banner render correctly.

@netlify

netlify Bot commented Jun 10, 2026

Copy link
Copy Markdown

Deploy Preview for nebari-docs2 ready!

Name Link
🔨 Latest commit e8432d8
🔍 Latest deploy log https://app.netlify.com/projects/nebari-docs2/deploys/6a2a2284cac2070007101e41
😎 Deploy Preview https://deploy-preview-685--nebari-docs2.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.
🤖 Make changes Run an agent on this branch

To edit notification comments on pull requests, go to your Netlify project configuration.

@andrewfulton9 andrewfulton9 left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This looks good to me. I was able to build and serve it locally and everything works as expected. My only comment is that we will have to stay on top of keeping the providers page up to date with the number of production deploy targets are ready and updating the table but I'm not sure if there is a good way around that.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: Todo 📬

Development

Successfully merging this pull request may close these issues.

Provider stubs: GCP, Azure, and Local placeholder pages

2 participants