# Sphinx Fortran Domain - a sphinx extension for documenting Fortran projects

**URL:** <https://fortran-lang.discourse.group/t/sphinx-fortran-domain-a-sphinx-extension-for-documenting-fortran-projects/11196>\
**Category:** Announcements\
**Created:** [October 25, 2026, 9:32am UTC](https://fortran-lang.discourse.group/t/sphinx-fortran-domain-a-sphinx-extension-for-documenting-fortran-projects/11196 "2026-10-25T09:32:19Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![hkvzjal](https://yyz2.discourse-cdn.com/free1/user_avatar/fortran-lang.discourse.group/hkvzjal/32/3055_2.png) [@hkvzjal](https://fortran-lang.discourse.group/u/hkvzjal)\
**Post date:** [October 25, 2026, 9:32am UTC](https://fortran-lang.discourse.group/t/sphinx-fortran-domain-a-sphinx-extension-for-documenting-fortran-projects/11196/1 "2026-10-25T09:32:19Z")

</div>

Hello everyone,

While the project has been public for a while I haven’t officially announced it here :

> **[Sphinx Fortran Domain — Sphinx Fortran Domain 0.2.2](https://fortran-lang.github.io/sphinx-fortran-domain/)**

With this extension, all the nice features of Sphinx are easily usable to create beautiful documentation out of Fortran source codes.

You’ll find some examples here :

> **[Examples — Sphinx Fortran Domain 0.2.2](https://fortran-lang.github.io/sphinx-fortran-domain/examples/index.html)**

One can also use this extension mixed with those for other languages if needing to document a mixed language project.

Give it a spin with your own projects and let me know, contributions are more than welcomed here :

> **[GitHub - fortran-lang/sphinx-fortran-domain](https://github.com/fortran-lang/sphinx-fortran-domain)**
>
> Contribute to fortran-lang/sphinx-fortran-domain development by creating an account on GitHub.

**Note** : the extension itself is not a parser, it can currently use either FORD or a regex based parser to do the job, other parser can be added as well. The parser can be set on the `conf.py` file at the source of the documentation section of your project.

Cheers,

---

<div class="post-metadata">

**Author:** ![fxm](https://yyz2.discourse-cdn.com/free1/user_avatar/fortran-lang.discourse.group/fxm/32/5726_2.png) [@fxm](https://fortran-lang.discourse.group/u/fxm)\
**Post date:** [October 25, 2026, 10:59am UTC](https://fortran-lang.discourse.group/t/sphinx-fortran-domain-a-sphinx-extension-for-documenting-fortran-projects/11196/2 "2026-10-25T10:59:02Z")

</div>

Great work, @hkvzjal. I’m already using it for new projects I started.

---

<div class="post-metadata">

**Author:** ![linwaytin](https://avatars.discourse-cdn.com/v4/letter/l/898d66/32.png) [@linwaytin](https://fortran-lang.discourse.group/u/linwaytin)\
**Post date:** [October 25, 2026, 8:28pm UTC](https://fortran-lang.discourse.group/t/sphinx-fortran-domain-a-sphinx-extension-for-documenting-fortran-projects/11196/3 "2026-10-25T20:28:58Z")

</div>

How is this compared to [GitHub - SciFortran/sphinxfortran\_ng: An improved version of the original sphinx-fortran python module · GitHub](https://github.com/SciFortran/sphinxfortran_ng) ?

---

<div class="post-metadata">

**Author:** ![hkvzjal](https://yyz2.discourse-cdn.com/free1/user_avatar/fortran-lang.discourse.group/hkvzjal/32/3055_2.png) [@hkvzjal](https://fortran-lang.discourse.group/u/hkvzjal)\
**Post date:** [October 25, 2026, 8:59pm UTC](https://fortran-lang.discourse.group/t/sphinx-fortran-domain-a-sphinx-extension-for-documenting-fortran-projects/11196/4 "2026-10-25T20:59:23Z")

</div>

Last time I tested that project it couldn’t build documentation for the projects I work with. Also, they build on top of `numpy.f2py` which imposes a large set of limitations.

---

<div class="post-metadata">

**Author:** ![jacobwilliams](https://yyz2.discourse-cdn.com/free1/user_avatar/fortran-lang.discourse.group/jacobwilliams/32/10_2.png) [@jacobwilliams](https://fortran-lang.discourse.group/u/jacobwilliams)\
**Post date:** [October 25, 2026, 9:11pm UTC](https://fortran-lang.discourse.group/t/sphinx-fortran-domain-a-sphinx-extension-for-documenting-fortran-projects/11196/5 "2026-10-25T21:11:17Z")

</div>

Is time to vibe code the entire documentation-generation stack into Fortran. 😬

---

<div class="post-metadata">

**Author:** ![certik](https://yyz2.discourse-cdn.com/free1/user_avatar/fortran-lang.discourse.group/certik/32/4_2.png) [@certik](https://fortran-lang.discourse.group/u/certik)\
**Post date:** [October 26, 2026, 1:09am UTC](https://fortran-lang.discourse.group/t/sphinx-fortran-domain-a-sphinx-extension-for-documenting-fortran-projects/11196/6 "2026-10-26T01:09:58Z")

</div>

I would just call it programming. Programming, going forward, means code generated by AI agents, unless specified otherwise. The result can be completely sloppy, in which case you can call it vibe coding. Or the final quality can be equivalent (or better than) what you would write by hand, in which case we can just call it programming.

So: it’s time to _program_ the entire documentation-generation stack into Fortran.
