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

No "Code documentation" section/chapter #320

Open
EpicEric opened this issue Sep 5, 2018 · 6 comments
Open

No "Code documentation" section/chapter #320

EpicEric opened this issue Sep 5, 2018 · 6 comments
Labels
good first issue Good for newcomers help wanted Extra attention is needed

Comments

@EpicEric
Copy link
Contributor

EpicEric commented Sep 5, 2018

Currently, all information there is on creating code documentation is hidden in appendices/whitespace.md, and only mentions how to add docstrings.

This should either be a new section in "Appendices", or an entirely new chapter, as it makes it easier to use and contribute to Pony libraries. Some information I'd expect to find:

  • Adding docstrings to Pony code
  • Generating Markdown from Pony sources
  • Generating Mkdocs from Markdown
  • Deploying to main.actor
@EpicEric
Copy link
Contributor Author

Updated to reflect the addition of main.actor

@SeanTAllen
Copy link
Member

@EpicEric would you be up for taking this on?

@EpicEric
Copy link
Contributor Author

EpicEric commented Mar 3, 2019

As I see it, documentation generation is not stable for non-stdlib use as of right now (ponylang/ponyc#2774), and the (partial) solution to that through main.actor is also not done, so I'd hold out on this part of the issue.

What can be done as a starting point for now is refactoring out the docstrings part from the Whitespace section, possibly as a new Appendix section for the time, thus improving its visibility.

@SeanTAllen
Copy link
Member

Sounds reasonable @EpicEric

@rhagenson rhagenson added the good first issue Good for newcomers label Dec 16, 2020
@rhagenson
Copy link
Member

For anyone tackling this as their first issue, feel free to move the Whitespace section into an Appendix (as Eric suggests). If you are feeling extra helpful, expanding that new "documentation" appendix to include steps on building documentation locally might be a nice addition.

@rhagenson
Copy link
Member

There are documentation-related matters in the Appendix here.

@SeanTAllen SeanTAllen added the help wanted Extra attention is needed label Feb 8, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
good first issue Good for newcomers help wanted Extra attention is needed
Projects
None yet
Development

No branches or pull requests

3 participants