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

Move documentation to Doxygen comments #687

Open
ihhub opened this issue Oct 4, 2022 · 5 comments
Open

Move documentation to Doxygen comments #687

ihhub opened this issue Oct 4, 2022 · 5 comments
Labels
documentation Information related to API and project description improvement Upgrade existing feature
Milestone

Comments

@ihhub
Copy link
Owner

ihhub commented Oct 4, 2022

This is not scalable to keep a separate file for documentation. There are many tools in the wild and one of them is Doxygen which is designed just for this purpose.

@ihhub ihhub added improvement Upgrade existing feature documentation Information related to API and project description labels Oct 4, 2022
@ihhub ihhub added this to the 1.0 milestone Oct 4, 2022
@zafar-hussain
Copy link

hi @ihhub,

I looked into this issue, and a few points came up, namely

  1. multiple Api descriptions documents : can these be renamed eg., cuda's api_description file as cuda_api_description.md, reason is doxygen parses the directories, it lists all similar named doc together, and causes confusion, or these docs are to be removed.

  2. multiple readme.md, same as above. ignore the readme.md in the root, that will stay

  3. contributing.md needs a bit to tyding for doxygen

  4. should separate issues be raised for for each class documentation, it will be easier to keep track

  5. do you have any logo for penguinV, so that it can be used in the docs

  6. any preferred format like html, pdf, xml for the docs, or we are to only provide a docfile plus instructions for the user to to generate the docs in their preferred format, using doxygen

cheers

@ihhub
Copy link
Owner Author

ihhub commented Oct 24, 2022

Hi @zafar-hussain , documentation generation in Doxygen is based on comments in the source code. What previously was done is to update the documentation manually which absolutely not a proper approach. Doxygen allows to generate the documentation automatically.

Doxygen can be also configured which types of tiles to be scanned. I think the first step is to add Doxygen as a part of GitHub Actions pipeline at the least to generate documentation.
Answering your ideas:

  1. Yes, we can. It makes more sense.
  2. Readme.MD is picked by Github automatically. We need to see if it's possible to do such.
  3. Can you explain why? Doxygen is going to scan only the source code files
  4. It would be a lot of issues. It is better to create one with multiple checkboxes.
  5. Nope.
  6. For now just instructions. Once we are going to be close to release we will include it into an archive. Also we can generate these files as a part of GitHub Actions pipeline.

@zafar-hussain
Copy link

hi @ihhub

thanks for the reply,

for point 3, I allowed doxygen to parse *.md files too, and it created nice looking help pages from them too,

eg.
image

@ihhub
Copy link
Owner Author

ihhub commented Oct 28, 2022

Hi @zafar-hussain , looks great, How would you like to proceed with it?

@zafar-hussain
Copy link

Hi @ihhub,

Sorry, I can't work on this project due to lack of time.

Cheers

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Information related to API and project description improvement Upgrade existing feature
Projects
None yet
Development

No branches or pull requests

2 participants