# Customizing Documentation

**URL:** <https://discuss.hashicorp.com/t/customizing-documentation/26721>\
**Category:** Plugin Development\
**Created:** [July 13, 2021, 6:47pm UTC](https://discuss.hashicorp.com/t/customizing-documentation/26721 "2021-07-13T18:47:11Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![SJrX](https://sea2.discourse-cdn.com/hashicorp/user_avatar/discuss.hashicorp.com/sjrx/32/19356_2.png) [@SJrX](https://discuss.hashicorp.com/u/SJrX)\
**Post date:** [July 13, 2021, 6:47pm UTC](https://discuss.hashicorp.com/t/customizing-documentation/26721/1 "2021-07-13T18:47:11Z")

</div>

Hello,

We’ve recently released a new provider that was based on [the provider scaffolding](https://github.com/hashicorp/terraform-provider-scaffolding) project. However one thing we aren’t clear on is as we go forward how we manage documentation.

The AWS provider has lots of customizations to it’s markdown, to make it easier and more self contained. If we run anything to generate documentation new resources all the existing stuff gets overridden.

Is there something obvious I’m missing, I’m relatively new to go tooling in general. If we make a new resource or update a provider how are we suppose to manage the documentation.

---

<div class="post-metadata">

**Author:** ![paddy](https://sea2.discourse-cdn.com/hashicorp/user_avatar/discuss.hashicorp.com/paddy/32/4484_2.png) [@paddy](https://discuss.hashicorp.com/u/paddy)\
**Post date:** [August 6, 2021, 6:31pm UTC](https://discuss.hashicorp.com/t/customizing-documentation/26721/2 "2021-08-06T18:31:14Z")

</div>

Are you talking about [terraform-plugin-docs](https://github.com/hashicorp/terraform-plugin-docs)?