Skip to content

Conversation

@matthewshaver
Copy link
Contributor

@matthewshaver matthewshaver commented Nov 25, 2025

What are you changing in this pull request and why?

Refactoring the install fusion page to get started

Checklist


🚀 Deployment available! Here are the direct links to the updated files:

@matthewshaver matthewshaver requested a review from a team as a code owner November 25, 2025 16:16
@vercel
Copy link

vercel bot commented Nov 25, 2025

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Preview Updated (UTC)
docs-getdbt-com Ready Ready Preview Nov 26, 2025 1:21am

@github-actions github-actions bot added content Improvements or additions to content Docs team Authored by the Docs team @dbt Labs labels Nov 25, 2025
Copy link
Collaborator

@runleonarun runleonarun left a comment

Choose a reason for hiding this comment

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

@matthewshaver I really like these changes! A few additional thoughts:

  1. Can we also add the Get started with Fusion under Get Started? I feel like this is another pathway that misses an opportunity to share Fusion content.
  2. The https://docs-getdbt-com-git-fusion-get-started-dbt-labs.vercel.app/docs/get-started-dbtdbt Quickstarts under Get started don't show any Fusion content, and is a good place for your new guides!

id: install-dbt-extension
description: "Installation instructions for the dbt extension."
sidebar_label: "Install the dbt extension"
sidebar_label: "Install the VS Code extension + Fusion"
Copy link
Collaborator

Choose a reason for hiding this comment

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

This distinction is super helpful!

---
title: "Configure your local setup"
sidebar_label: "Configure your local setup"
title: "Configure your local environment"
Copy link
Collaborator

Choose a reason for hiding this comment

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

+1


Ready to get started using the <Constant name="fusion_engine" />? Whether you're using dbt today or just getting started, we have the resources to help you get up and running

## Already using dbt? Start here
Copy link
Collaborator

Choose a reason for hiding this comment

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

I wonder if we should put the "New to dbt?" first. 🤔 Feels like new should come first then seasoned.

Thinking about how we can make both of the above visible on first glance, the note at the top feels ginormous. Can we condense it?

Copy link
Contributor Author

@matthewshaver matthewshaver Nov 26, 2025

Choose a reason for hiding this comment

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

@runleonarun both really good points. I was trying to make it formatted similarly to the welcome page on our site for consistency, but we've all talked about how those sections are hidden off-screen too. Two thoughts there:

  1. We make the headers smaller
  2. We lose the H1 header on this page entirely and make it only the two options visible

Which way would you lean?

As for the order, I totally agree - my only thought was that we put existing users first during this portion of the preview program while they're our focus. Once we shift to net new, we could switch them up, but maybe that's too much maintenance.

I was even thinking we potentially add a note in the "New customer" section that states they may want to start with the most recent version of GA Core since Fusion is still preview. Thoughts there?

Copy link
Collaborator

Choose a reason for hiding this comment

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

Maybe #1 because I'm not sure we can remove the H1 - it's page title and shows up if we remove it. We need it to show the preview pill.

my only thought was that we put existing users first during this portion of the preview program while they're our focus. Once we shift to net new, we could switch them up, but maybe that's too much maintenance.

Actually that makes a lot of sense.

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

Labels

content Improvements or additions to content Docs team Authored by the Docs team @dbt Labs

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants