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

Documentation Site #20

Open
jeddeloh opened this issue Jul 19, 2020 · 4 comments
Open

Documentation Site #20

jeddeloh opened this issue Jul 19, 2020 · 4 comments
Labels
documentation Improvements or additions to documentation help wanted Extra attention is needed

Comments

@jeddeloh
Copy link
Owner

I'd really like to get a proper documentation site up. Some possibilities:

@jeddeloh jeddeloh added documentation Improvements or additions to documentation help wanted Extra attention is needed labels Jul 19, 2020
@jeddeloh jeddeloh mentioned this issue Jul 19, 2020
4 tasks
@jfrolich
Copy link
Collaborator

I am hacking on odoc (but not sure when I will arrive at anything good). Markdown support for doc comments /** ... */ will land in reason soon automatically converting it to ocamldoc so it will render in the documentation generator, so it would be good to document the bindings and modules using that even before we have good documentation generation and before markdown supports land.

@yawaramin
Copy link

yawaramin commented Jul 20, 2020

@jfrolich Markdown support will land in Reason (I assume, at some point), but not in BuckleScript because BuckleScript is not upgrading its refmt version for the foreseeable future.

@jfrolich
Copy link
Collaborator

jfrolich commented Jul 21, 2020

I hope we can land it in the new syntax as well. It is possible to use your own version of refmt with Bucklescript. Are you sure Bucklescript is not upgrading Reason? That would not be great. It wouldn't be so bad if they would decoupled and released separately though, but shipping an old version by default is not great I guess.

@yawaramin
Copy link

Based on what happened in rescript-lang/rescript-compiler#4271 and then after that the new syntax being publicized, I assume they won't upgrade. And I don't see Markdown docs landing in the new syntax in the near future either (in fact it will be a long road to get to even odoc support for the new syntax, i.e. parity with where Reason syntax is now).

If you want to publish API docs in the near future, your best bet is bsdoc with the current Reason syntax + ocamldoc markup.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation help wanted Extra attention is needed
Projects
None yet
Development

No branches or pull requests

3 participants