---
title: "Comment by Apps by Mo on \"Writing Good DocC Documentation for Swift Packages: Prose That Developers Actually Read\" | Hashnode"
description: "Curated Topics groups are the part I keep relearning. An alphabetical symbol list only helps someone who already knows the name they want. One habit that has wo"
url: "https://hashnode.com/posts/writing-good-docc-documentation-for-swift-packages-prose-that-developers-actually-read/6ade0b84ba9692b180a8fe14/comment/6ade3274e47b2d570eb64f15"
---

[Discussion](https://hashnode.com/posts/writing-good-docc-documentation-for-swift-packages-prose-that-developers-actually-read/6ade0b84ba9692b180a8fe14)

Comment [Writing Good DocC Documentation for Swift Packages: Prose That Developers Actually Read](https://hashnode.com/posts/writing-good-docc-documentation-for-swift-packages-prose-that-developers-actually-read/6ade0b84ba9692b180a8fe14)

[Apps by Mo](https://hashnode.com/@appsbymo)

[Oct 25](https://hashnode.com/posts/writing-good-docc-documentation-for-swift-packages-prose-that-developers-actually-read/6ade0b84ba9692b180a8fe14/comment/6ade3274e47b2d570eb64f15)

Curated Topics groups are the part I keep relearning. An alphabetical symbol list only helps someone who already knows the name they want. One habit that has worked for me as a solo Mac developer: write the summary line in the same commit as the symbol, as you say, and let CI fail on broken symbol links. It keeps the docs from drifting between releases.
