-
Notifications
You must be signed in to change notification settings - Fork 627
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
I would appreciate context and an example #989
Comments
examining the page source code one finds the following <div class="pkgdown-footer-right">
<p></p>
<p>Site built with <a href="[https://pkgdown.r-lib.org/](view-source:https://pkgdown.r-lib.org/)" class="external-link">pkgdown</a> 2.0.7.</p>
</div> |
Regarding the CRAN pkgdown webpage see the GH pkgdown repo DESCRIPTION file. I suppose you're aware that the location where you opened this Issue is not that of the pkgdown repo. |
The 7/6 email from spaghetti answers my question, thank you.
I haven't dealt with the 7/13 followup, indicating that I had reported this
to the wrong package.
…On Wed, Jul 19, 2023 at 4:35 PM spaette ***@***.***> wrote:
@TimHesterberg <https://github.com/TimHesterberg>
Have the questions been sufficiently addressed so as to justify closing
this current Issue?
—
Reply to this email directly, view it on GitHub
<#989 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AH2N4PGEOFRFAY7H4XQH3HDXRBVLNANCNFSM6AAAAAAYIK2ZQ4>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
pkdgown produces a website for a package - what is that?
How does it relate to a github site where the package code is stored?
Does it include code, or just documentation?
How does it relate to CRAN site where the documentation is available, e.g.
http://cran.fhcrc.org/web/packages/pkgdown/index.html ?
An example of a package website built with pckdown would be helpful.
The text was updated successfully, but these errors were encountered: