# Multiple archetypes, one folder?

**URL:** <https://discourse.gohugo.io/t/multiple-archetypes-one-folder/19046>\
**Category:** support\
**Created:** [June 4, 2019, 8:24pm UTC](https://discourse.gohugo.io/t/multiple-archetypes-one-folder/19046 "2019-06-04T20:24:11Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![dixonge](https://yyz2.discourse-cdn.com/flex036/user_avatar/discourse.gohugo.io/dixonge/32/8756_2.png) [@dixonge](https://discourse.gohugo.io/u/dixonge)\
**Post date:** [June 4, 2019, 8:24pm UTC](https://discourse.gohugo.io/t/multiple-archetypes-one-folder/19046/1 "2019-06-04T20:24:11Z")

</div>

After getting my existing content mostly ship-shape, I am now moving forward to future content. I like the idea of archetypes vs. just copying blank draft posts. But if I try using an archetype and I specify this archetype from the command line (for example, `hugo new books/reamde.md` it creates this new file in the content/books folder. But I want all of my blog posts (including book reviews) in the /content/posts folder.

How can I specify the /posts folder when creating a new file? I intend on having several archetype files, but want all the content in the same folder.

---

<div class="post-metadata">

**Author:** ![dixonge](https://yyz2.discourse-cdn.com/flex036/user_avatar/discourse.gohugo.io/dixonge/32/8756_2.png) [@dixonge](https://discourse.gohugo.io/u/dixonge)\
**Post date:** [June 4, 2019, 8:29pm UTC](https://discourse.gohugo.io/t/multiple-archetypes-one-folder/19046/2 "2019-06-04T20:29:19Z")

</div>

aaaaaand, of course I find the answer only after posting the question _sigh_

`hugo new -k books posts/reamde.md`

That does what I wanted.

---

<div class="post-metadata">

**Author:** ![Leopo](https://yyz2.discourse-cdn.com/flex036/user_avatar/discourse.gohugo.io/leopo/32/8580_2.png) [@Leopo](https://discourse.gohugo.io/u/Leopo)\
**Post date:** [June 4, 2019, 8:44pm UTC](https://discourse.gohugo.io/t/multiple-archetypes-one-folder/19046/3 "2019-06-04T20:44:33Z")

</div>

I was in a similar situation of answering my question. This is useful regardless.