-
Notifications
You must be signed in to change notification settings - Fork 86
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
Upload ROBODoc documentation to gh-pages project page #7
Comments
Do you have a custom |
Pull request #12 automates the documentation build with CMake. |
I’ve put up an example on my branch at http://zbeekman.github.io/json-fortran if you want to check it out. If you put the API documentation online via gh-pages, then we should update the README.md to point there. |
FYI: I fiddled with the headers a little bit. I switched LICENSE to COPYRIGHT, which is recognized by default. I'm going to clean it up a bit more later. |
I like it. I'm going to go ahead and do the gh-pages thing. |
Done. check it out. |
Nice. I suggest adding the |
Done. |
Looks great. 👍 I’ll close the issue. |
This is just a suggestion, but it might be nice to have the ROBODoc documentation online. The README.md could then link to the API documentation. I’m going to work on a feature branch to implement this in the CMake (and maybe build.sh) builds if you like the idea. I’ll send a pull request when I’m done.
I’m not sure whether or not it would make sense to also add something like a “publish” target (which would not be triggered with the “all” target) to automate publishing to gh-pages. To do this git commit and git push commands would have to be issued. CMake has machinery to find git, and script this in a makefile. However, having something like:
but it does make me a bit nervous to be scripting git commits and pushes to remotes. One could also argue that it is less likely to make a typo if it is scripted and tested.
Since scripting the publishing of gh-pages with the build system is of no utility to end users I think it doesn’t make sense to include it.
Check out this page on GitHub help for some info on creating a project page.
The text was updated successfully, but these errors were encountered: