-
Notifications
You must be signed in to change notification settings - Fork 16
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
{pkgdown} website #7
Comments
I think you're tackling two issues here. Firstly, I've not got time to work on the html version of the documentation --- partly because a lot more details are both in my website and in our books (mainly this one). The second one I think is about integration with Travis. I have this --- but the problem is that in the past, Travis wasn't very responsive at allowing to install external packages (eg So: anyway, both of these could be "fixed" and I would certainly be interested in collaborating on this! |
Great. I totally understand the time issue. I am happy to set up the docs and provide hosting details (some switches in GitHub that only you can switch). I will take a look at Travis separately as you are right they are really different issues! Happy with a pull request? |
Sure! Looking forward to it! (see my comment to #18 too!) |
closed 78b6c0a |
Personally I really like using html websites to navigate through package documentation. It can also be a great way of centralising all of the resources for your package.
The {pkgdown} package makes constructing these very easy with the sites then being able to be hosted on GitHub pages. It can be nice to have the package built externally (i.e on Travis) so that it updates without package author interventions
Happy to help with this if interested.
Linked to #6
The text was updated successfully, but these errors were encountered: