Skip to content
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

update How we structure guide to account for dbt Mesh #5424

Open
1 task done
bethanyhipple-dbtlabs opened this issue May 1, 2024 · 0 comments
Open
1 task done

update How we structure guide to account for dbt Mesh #5424

bethanyhipple-dbtlabs opened this issue May 1, 2024 · 0 comments
Labels
content Improvements or additions to content improvement Use this when an area of the docs needs improvement as it's currently unclear

Comments

@bethanyhipple-dbtlabs
Copy link
Contributor

Contributions

  • I have read the contribution docs, and understand what's expected of me.

Link to the page on docs.getdbt.com requiring updates

https://docs.getdbt.com/best-practices/how-we-structure/6-the-rest-of-the-project#project-splitting

What part(s) of the page would you like to see updated?

The project splitting part of the "how we structure our project" guide advises users to not split projects unless absolutely necessary. The rational here gives the example of needing to use private packages to make the project dependencies work. However with dbt Mesh now available, we should update our stance on project splitting.

Additional information

No response

@bethanyhipple-dbtlabs bethanyhipple-dbtlabs added content Improvements or additions to content improvement Use this when an area of the docs needs improvement as it's currently unclear labels May 1, 2024
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 improvement Use this when an area of the docs needs improvement as it's currently unclear
Projects
None yet
Development

No branches or pull requests

1 participant