# Extend documentation links in GitHub README.md file

**URL:** <https://gramps.discourse.group/t/extend-documentation-links-in-github-readme-md-file/4311>\
**Category:** Feedback\
**Created:** [October 21, 2023, 7:56pm UTC](https://gramps.discourse.group/t/extend-documentation-links-in-github-readme-md-file/4311 "2023-10-21T19:56:17Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![emyoulation](https://yyz2.discourse-cdn.com/free1/user_avatar/gramps.discourse.group/emyoulation/32/67_2.png) [@emyoulation](https://gramps.discourse.group/u/emyoulation)\
**Post date:** [October 21, 2023, 7:56pm UTC](https://gramps.discourse.group/t/extend-documentation-links-in-github-readme-md-file/4311/1 "2023-10-21T19:56:17Z")

</div>

Developer documentation is widely dispersed. While difficult, it is possible to become proficient finding User docs in the wiki, mail List and forum. But the developer docs tend to be more elusive.

For example, I note that the [Gramps Data Model](https://gramps-project.org/wiki/index.php/Gramps_Data_Model) and [API Methods](https://www.gramps-project.org/docs/#) are key references. But it usually takes me awhile to remember that the documentation tool used for the API is Sphinx then at least another 10 minutes to actually _find_ those docs.

Meanwhile, the GitHub repository’s link for Documentation is for basic User docs, not developer docs (or docs for beta testers or translators). Nor does it link to the [Developers](https://gramps-project.org/wiki/index.php/Category:Developers) category in the wiki.

The **[Documentation](https://github.com/gramps-project/gramps#documentation)** section of the README.md file of the Gramps-Project on GitHub:

> **[GitHub - gramps-project/gramps: Source code for Gramps Genealogical program](https://github.com/gramps-project/gramps#documentation)**
>
> Source code for Gramps Genealogical program. Contribute to gramps-project/gramps development by creating an account on GitHub.

---

<div class="post-metadata">

**Author:** ![emyoulation](https://yyz2.discourse-cdn.com/free1/user_avatar/gramps.discourse.group/emyoulation/32/67_2.png) [@emyoulation](https://gramps.discourse.group/u/emyoulation)\
**Post date:** [October 21, 2023, 8:10pm UTC](https://gramps.discourse.group/t/extend-documentation-links-in-github-readme-md-file/4311/2 "2023-10-21T20:10:57Z")

</div>

Kevin Dunn was working on a project to integrate Sphinx into MediaWiki. That [project was archived](https://bitbucket-archive.softwareheritage.org/projects/ke/kevindunn/sphinx-wiki.html) with about 250,000 other projects when the BitBucket [Mercurial Version Control service went offline in 2020](https://octobus.net/blog/2020-04-23-heptapod-and-swh.html).

But in [this posting](https://www.mail-archive.com/sphinx-dev@googlegroups.com/msg04240.html), he has an interesting note about calling Sphinx with Python with a Django example. Of course, the Bitbucket material is part of the archive, and not indexed on the Wayback Machine.

> If you prefer to call Sphinx directly from your Python code (i.e. not  
> via Python’s subprocess module), then take a look at line 1749 in this  
> Django file:  
> [http://bitbucket.org/kevindunn/ucommentapp/src/969d4da3da58/views.py](http://bitbucket.org/kevindunn/ucommentapp/src/969d4da3da58/views.py)

If some example of doing that could be found, it seems likely that the Help feature from @kku 's SuperTool might be expanded from merely being a APIl methods vocabulary list into being a real reference.

---

<div class="post-metadata">

**Author:** ![system](https://global.discourse-cdn.com/free1/uploads/gramps/original/1X/2ac1e712b7adf612e31ca08a55419f4cf37c0158.png) [@system](https://gramps.discourse.group/u/system)\
**Post date:** [November 20, 2023, 8:11pm UTC](https://gramps.discourse.group/t/extend-documentation-links-in-github-readme-md-file/4311/3 "2023-11-20T20:11:11Z")

</div>

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.