Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Build man pages for the CLI #108

Open
Cadair opened this issue Jul 31, 2022 · 4 comments
Open

Build man pages for the CLI #108

Cadair opened this issue Jul 31, 2022 · 4 comments
Labels
documentation An improvement to the documentation enhancement A new feature or other enhancement to the library good first issue help wanted

Comments

@Cadair
Copy link
Owner

Cadair commented Jul 31, 2022

Maybe with sphinx?

@Cadair Cadair added enhancement A new feature or other enhancement to the library help wanted good first issue documentation An improvement to the documentation labels Jul 31, 2022
@Reith77
Copy link

Reith77 commented Jul 31, 2022

Hi, I'm new to Github and would like to contribute

I think I can make a man page for parfive, should I just fork the repo, create a man page and add it to the root of the repo ?

@Cadair
Copy link
Owner Author

Cadair commented Jul 31, 2022

Hello @Cantej 👋

My thoughts here are that I would like to have more detailed info available primarily to people who want to use the CLI. Given our documentation is built using sphinx, which already contains some information on the CLI, and any new information we put in the man pages should be available in the web docs as well. I was planning on using sphinx's man page output generator.

From a quick look over sphinx's manual page options it looks like you can select a subtree of your docs to be the man page(s), so maybe the best flow here would be:

  1. Make a new rst file in the docs folder dedicated to the CLI.
  2. Write the kind of things you would expect in a man page detailing the CLI options etc.
  3. Test using sphinx with the man page builder to build a man page in the format expected.

Let us know if you have any questions, and feel free to write as much or as little in the documentation as you want, getting the infrastructure working would be a great contribution in itself.

@Reith77
Copy link

Reith77 commented Aug 3, 2022

Hi,

I may not actually be able to do this, if someone else would like to take this up, please feel free

@exitflynn
Copy link

exitflynn commented Feb 11, 2023

i'm looking into this! 🤠

edit: i wasn't able to make progress on this for a while due to health reasons, i've begun working on this now. figured, i should let it be known.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation An improvement to the documentation enhancement A new feature or other enhancement to the library good first issue help wanted
Projects
None yet
Development

No branches or pull requests

3 participants