# Beman template directory structure

**URL:** <https://discourse.bemanproject.org/t/beman-template-directory-structure/133>\
**Category:** Beman Project Development\
**Created:** [June 11, 2024, 6:07pm UTC](https://discourse.bemanproject.org/t/beman-template-directory-structure/133 "2024-06-11T18:07:32Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![dsankel](https://yyz1.discourse-cdn.com/flex029/user_avatar/discourse.bemanproject.org/dsankel/32/5_2.png) [@dsankel](https://discourse.bemanproject.org/u/dsankel)\
**Post date:** [June 17, 2024, 3:39pm UTC](https://discourse.bemanproject.org/t/beman-template-directory-structure/133/2 "2024-06-17T15:39:31Z")

</div>

I moved your post to the top level since this is a sizable topic in itself.

I like these ideas.

@ramey, why does your “should include” have `/paper` and the “advocate for” have `doc/paper`?

It seems like some Beman libraries will include the source for the paper they implement, but others will not. I like the idea of having a link to the official paper through wg21.link in the top level `README.md` as recommended by [[README.IMPLEMENTS]](https://discourse.bemanproject.org/t/deciding-on-a-project-logo/102/11). If 99% of users access the paper through that link, I think something like your second suggestion (putting the paper in doc/paper) makes the most sense.

I like the idea of putting `examples/` in the top level (as opposed to `src/examples`) since it will be immediately obvious for someone looking at the github repository where they can find some example code.

---

_[View the full topic](https://discourse.bemanproject.org/t/beman-template-directory-structure/133)._