# Do we have a better name than “Documentation Extensions”?

**URL:** <https://forums.swift.org/t/do-we-have-a-better-name-than-documentation-extensions/60273>\
**Category:** Swift-DocC\
**Created:** [September 13, 2022, 4:46pm UTC](https://forums.swift.org/t/do-we-have-a-better-name-than-documentation-extensions/60273 "2022-09-13T16:46:03Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![taylorswift](https://sea2.discourse-cdn.com/swift/user_avatar/forums.swift.org/taylorswift/32/43413_2.png) [@taylorswift](https://forums.swift.org/u/taylorswift)\
**Post date:** [September 13, 2022, 6:47pm UTC](https://forums.swift.org/t/do-we-have-a-better-name-than-documentation-extensions/60273/3 "2022-09-13T18:47:45Z")

</div>

> [@jack](#):
>
> A documentation extension extends the documentation for a symbol—it's meant to mirror Swift language feature name because it operates similarly.

well, we now have:

- [Dealing with Nested Types when Documenting Extensions with DocC - #6 by theMomax](https://forums.swift.org/t/dealing-with-nested-types-when-documenting-extensions-with-docc/60099/6)
- [Document Extensions to External Types Using DocC - #41 by theMomax](https://forums.swift.org/t/document-extensions-to-external-types-using-docc/56060/41)

which is becoming very confusing when transferring these concepts over into a codebase.

> [@jack](#):
>
> Are there other words besides 'extension' that describe the behavior more clearly?

i don’t know, but this was the reason for this thread, to brainstorm alternative terminology we can use for this idea

---

_[View the full topic](https://forums.swift.org/t/do-we-have-a-better-name-than-documentation-extensions/60273)._