Skip to content

Commit

Permalink
Adjust package documentation
Browse files Browse the repository at this point in the history
  • Loading branch information
jzhu13 committed Oct 25, 2024
1 parent d99c18c commit 4f729b7
Showing 1 changed file with 2 additions and 1 deletion.
3 changes: 2 additions & 1 deletion website/docs/docs/build/packages.md
Original file line number Diff line number Diff line change
Expand Up @@ -20,9 +20,10 @@ In dbt, libraries like these are called _packages_. dbt's packages are so powerf
* Models to understand [Redshift](https://hub.getdbt.com/dbt-labs/redshift/latest/) privileges.
* Macros to work with data loaded by [Stitch](https://hub.getdbt.com/dbt-labs/stitch_utils/latest/).

dbt _packages_ are in fact standalone dbt projects, with models and macros that tackle a specific problem area. As a dbt user, by adding a package to your project, the package's models and macros will become part of your own project. This means:
dbt _packages_ are in fact standalone dbt projects, with models, macros, and more that tackle a specific problem area. As a dbt user, by adding a package to your project, all of the package's resources will become part of your own project. This means:
* Models in the package will be materialized when you `dbt run`.
* You can use `ref` in your own models to refer to models from the package.
* You can use `source` to refer to sources in the package.
* You can use macros in the package in your own project.
* It's important to note that defining and installing dbt packages is different from [defining and installing Python packages](/docs/build/python-models#using-pypi-packages)

Expand Down

0 comments on commit 4f729b7

Please sign in to comment.