From 1070d16a7c3027e7c05992a8f3ab01b11e2236cb Mon Sep 17 00:00:00 2001 From: Louie S Date: Tue, 16 Jan 2024 10:08:35 -0500 Subject: Added page about dash docsets --- dash-docset-contributions.html | 40 ++++++++++++++++++++++++++++++++++++++++ 1 file changed, 40 insertions(+) create mode 100644 dash-docset-contributions.html (limited to 'dash-docset-contributions.html') diff --git a/dash-docset-contributions.html b/dash-docset-contributions.html new file mode 100644 index 0000000..bb9038a --- /dev/null +++ b/dash-docset-contributions.html @@ -0,0 +1,40 @@ +

Dash/Zeal Docset Contributions

+

I package docsets for documentation generally unavailable through Dash/Zeal docsets.

+

My Dash docsets are based on a common generation template.
Dash docsets maintained by me include:

+ +

* indicates that the docset creation script could use improvement, usually in indexing index entries
^ indicates that a new version needs to be packaged, uploaded to the releases tab of the repo, and pushed to Dash-User-Contributions

+

I also have several unofficial Dash docsets that I maintain, but do not intend to contribute to Dash-User-Contributions, usually because my docset diverges from one that was already contributed or there is already an official version of the docset:

+ +

Additional docsets I have desire to package in the future include:

+ +

"WIP" indicates that some working model exists, but has not yet been successfully pushed to Dash-User-Contributions

+
+

Regarding GNU project docsets

+

It has been tiring to manage the high redundancy of the code in my various docset generation repos. This is especially true among GNU project docsets, and I believe it would be beneficial to contain all of these in a single repo. A few things to note:

+
    +
  1. I would have to find a different solution to uploading compiled docsets, since I currently use the "releases" page of each repo. Github Pages, maybe?
  2. +
  3. There are certain edge cases in certain repos that may make things annoying. I would either have to account for these on a case by case basis or build a better infrastructure.
  4. +
+

For now, this remains an idea that I will need to brainstorm further...

-- cgit