# How we (used to) structure our dbt projects

**URL:** <https://discourse.getdbt.com/t/how-we-used-to-structure-our-dbt-projects/355>\
**Category:** Archive\
**Created:** [May 10, 2019, 6:57pm UTC](https://discourse.getdbt.com/t/how-we-used-to-structure-our-dbt-projects/355 "2019-05-10T18:57:22Z")\
**Posts on this page:** 1\
**Showing post:** 31

<div class="post-metadata">

**Author:** ![joellabes](https://sea2.discourse-cdn.com/flex020/user_avatar/discourse.getdbt.com/joellabes/32/3980_2.png) [@joellabes](https://discourse.getdbt.com/u/joellabes)\
**Post date:** [November 19, 2021, 2:45am UTC](https://discourse.getdbt.com/t/how-we-used-to-structure-our-dbt-projects/355/31 "2021-11-19T02:45:52Z")

</div>

> [@ron.chipman](#):
>
> there is a lot of push in the documents around snapshots, and the use of them ‘directly from sources’, yet you make no mention of them in their outline

Snapshots don’t live in the `models` directory of a dbt project, so aren’t really in scope for this article. Have you looked at [Building models on top of snapshots](https://discourse.getdbt.com/t/building-models-on-top-of-snapshots/517) and the other articles it links to?

I see your [question in the community Slack](https://getdbt.slack.com/archives/C2JRRQDTL/p1634733705064300) didn’t get a heap of traction - I want to think a lot more about best practices for snapshots in the new year and will try to fold in some answers to that sort of thing 🤞

---

_[View the full topic](https://discourse.getdbt.com/t/how-we-used-to-structure-our-dbt-projects/355)._