# \[ACCEPTED\] Template or Boilerplate Feature

**URL:** <https://community.fibery.io/t/accepted-template-or-boilerplate-feature/306>\
**Category:** Ideas & Features\
**Created:** [August 24, 2019, 1:46pm UTC](https://community.fibery.io/t/accepted-template-or-boilerplate-feature/306 "2019-08-24T13:46:04Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![rickcogley](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/rickcogley/32/274_2.png) [@rickcogley](https://community.fibery.io/u/rickcogley)\
**Post date:** [August 24, 2019, 1:46pm UTC](https://community.fibery.io/t/accepted-template-or-boilerplate-feature/306/1 "2019-08-24T13:46:04Z")

</div>

We would need to create entities which are similar to previous ones or, a boilerplate entity, for QC reasons. For example:

- populate a guide in the wiki with certain decided sections
- populate a task or user story with a checklist and other settings, to help guide it

Worst case but basic: ability to copy paste entities the user somehow designates as templates / boilerplates, such as by putting them into a folder.

Better: some skillful way to insert your templates / boilerplates.

Github has something similar in “saved replies”:

 ![image](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/9/91acacc80f7469fc6dd00eb7f84e14330f7066da.png)

---

<div class="post-metadata">

**Author:** ![mdubakov](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/mdubakov/32/10_2.png) [@mdubakov](https://community.fibery.io/u/mdubakov)\
**Post date:** [August 26, 2019, 11:33am UTC](https://community.fibery.io/t/accepted-template-or-boilerplate-feature/306/2 "2019-08-26T11:33:27Z")

</div>

Yeah, templates should be added eventually.