# New documentation plugin in development

**URL:** https://meta.discourse.org/t/new-documentation-plugin-in-development/321764
**Category:** Announcements
**Tags:** documentation, doc-categories
**Created:** [August 26, 2024, 11:00pm UTC](https://meta.discourse.org/t/new-documentation-plugin-in-development/321764 "2024-08-26T23:00:33Z")
**Posts on this page:** 1
**Showing post:** 15

<div class="post-metadata">

### Author: ![tvavrda](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/tvavrda/32/480674_2.png) [@tvavrda](https://meta.discourse.org/u/tvavrda)
#### Post date: [February 15, 2025, 10:58pm UTC](https://meta.discourse.org/t/new-documentation-plugin-in-development/321764/15 "2025-02-15T22:58:04Z")

</div>

> [@fredrikj](#):
>
> I suppose using [meta.discourse.org](http://meta.discourse.org) as an issue tracker gives the project an opportunity for “dogfooding” Discourse. And all other issue trackers have their own faults, so it’s a pain having to choose one. But to me Discourse - while being excellent as a forum for questions and discussions - is very lacking as an issue tracker.

We use Discourse as an issue tracker. Better said – I try to force my team to use Discourse as an issue tracker :slight_smile: And a wiki, and a forum, and a **documentation** … I suspect CDCK team to have another “secret” Discourse site where they track their stuff internally, using some interesting plug-ins, no-one has…

No matter how good the issue tracker is here, the community cannot be compared to anything else I know. In the end it’s the people who develop the software, not the technology behind it. And they rock! :metal:

And I like the documentation plugin a lot. :heart:

Now with all my praise, would it be possible to approve my [PR](https://github.com/discourse/discourse-doc-categories/pull/29)? :smiley:

---

_[View the full topic](https://meta.discourse.org/t/new-documentation-plugin-in-development/321764)._
