Open
Conversation
…readme; update to hex sticker logo
…der to seed future work
Collaborator
|
Thanks. CI/CD is failing:
I also quite enjoy the current vignette-less state: with a vignette, Does the hex logo need to be over 2000 pixels wide? Is there perhaps a smaller version? |
Author
|
Gosh. I see your point. I'll remove the Vignette, but keep the split readme and smaller hex. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Hello! Huge fan of duckdb and R. Wanted to make some small improvements to the pkgdown site and set the seeds for future vignette contributions.
I've done the following in this PR:
index.mdfile to separate Github README presentation from pkgdown sitepkgdown.ymltopkgdown/folder; added description to the home page