# Discussion: Content Organization Best Practice

**URL:** <https://discourse.gohugo.io/t/discussion-content-organization-best-practice/6360>\
**Category:** support\
**Created:** [April 27, 2017, 12:15pm UTC](https://discourse.gohugo.io/t/discussion-content-organization-best-practice/6360 "2017-04-27T12:15:10Z")\
**Posts on this page:** 1\
**Showing post:** 9

<div class="post-metadata">

**Author:** ![marcojakob](https://yyz2.discourse-cdn.com/flex036/user_avatar/discourse.gohugo.io/marcojakob/32/303_2.png) [@marcojakob](https://discourse.gohugo.io/u/marcojakob)\
**Post date:** [May 15, 2017, 10:13am UTC](https://discourse.gohugo.io/t/discussion-content-organization-best-practice/6360/9 "2017-05-15T10:13:37Z")

</div>

@jgreely Yes, externally hosting binary assets is a valid case that I have also been thinking about using for some of my larger projects. Like you said, let’s call this _Strucutre C_:

# Structure C

Keeping most **binary assets in external storage** (like S3, Cloudinary, .etc.) instead of keeping them inside the Hugo folder structure.

* * *

#### Pros

- **Keep Git repo small** : Most Hugo projects are stored in a Git repo. Even if Git is not ideal for storing binary assets this is no problem for smaller projects. But if a project gets larger (let’s say over ~600MB) keeping everything in a Git repo might slow down everything.
- Very fast build process (especially helpful for things like continuous deployment - [Netlify](https://www.netlify.com) and the like).
- Asset pipeline (like resizing images) can be handled by scripts or completely outsorced to platforms like [Cloudinary](http://cloudinary.com/) or [imgix](https://www.imgix.com/).

#### Cons

- Setup is complicated. Instead of one place for the entire site, content it is spread out over two platforms.
- Managing assets in an external storage can be a pain (same with static folder in _Structure A_): If we put all images in one storage it is difficult to tell which images are still in use and which images  
could be deleted. We could replicate the entire structure of the content for images but this is also a lot of work to maintain.
- References to images are long and may lead to mistakes  
(for example `https://my-external-storage.on-amazon-s3.com/my-bucket/12341232344234.jpg`).

* * *

#### CONTENT

No assets in the content folder.

```auto
├── content/
    └── _index.md
    └── about/
    │ └── _index.md
    └── blog/
        ├── _index.md
        ├── firstpost.md
        └── secondpost.md

```

#### STATIC

Static folder is almost empty. Most assets are stored in an external storage.

---

_[View the full topic](https://discourse.gohugo.io/t/discussion-content-organization-best-practice/6360)._