https://twitter.com/stefaniebutland/status/1050561344418676737?s=12

Write a function to create package links from package names and list those links as shortcuts to package website.

http://style.tidyverse.org/error-messages.html#problem-statement

Take the chance and replace stop(), warning() and message() by rlang's abor(), warn() and inform().

To index datasets -- and even their descriptions -- I can wrap data()

get_datasets <- function(package) {
    dinfo <- data(package = package)
    dinfo[["results"]][, "Item"]
}

get_datasets("ggplot2")

Thanks to Nathan Werth via rstudio community.

What is your favorite resource?

The goal of the learn repository is to store learning resources as issues.

Your job is to explore learning resources as issues and react with an emoji. For example, this is how you can up-vote the resources you like:

By contributing to this issue you will help others discover the best resources.

If you have any question, please ask me by referring to me as @maurolepore.

Search related issues on https://github.com with: label:hacktoberfest maurolepore

Get Started appears automatically when the package contains an article with the same name of the package.

• Simplify README to the bare bones. Give detailed installation instructions in blog .
• Move all the rest of the information to Get Started.
• Add links to packages.
• Remove links to packages from References.
• Leave references only for functions.
• Add list of all functions to get started.
• Add list of all datasets to get started.

I think this comes from cwickham tidyverse course:

This ...

install.packages("fgeo")

... is equivalent to this

install.packages("fgeo.tool")
install.packages("fgeo.map")
...

And this ...

library(fgeo)

... is equivalent to this

library(fgeo.tool)
library(fgeo.map)
...

From README remove internal functions.

• Find out how to create a workspace that is temporary, e.g. this one

Links can be added programatically. This can be useful to add links to packages in README, to funcitons in Get Started; to people's websites on acknowledgements.

For inspiration see:

• code to generate the list of reviewers here.
• fgeo README, with links created with fgeo_link() and stored in a knitr::kable().

E.g. code of the paper of Joe LaManna.

What labels would you add/remove?

The goal of the learn repository is to store learning resources as issues. To make those easy to find I am using labels. The resources and labels accumulated organically, and now it's time to get organized. What labels would you add/remove?

If you have any question, please ask me by referring to me as @maurolepore.

Search related issues on https://github.com with: label:hacktoberfest maurolepore

Simplify readme even further. E.g. don't repeat package name. See http://dplyr.tidyverse.org/.

Find what functions are used and not used in each package:

• May use pkginspector.
• May use the shell.

Reorganize functions in website:

• Hide developer-oriented functions with @Keywords internal.
• Redefine families and use_concept().
• Label useless functions to be moved to PR.
  • Functions that work with fastField seem too specific to live in fgeo.tool. Extract them into a PR.
  • Functions to read/write from/to files/directories should move to its own package fgeo.io

• Moved functions from ctfs to fgeo.ctfs (not a core package).
• Renamed funcitons.
• Removed functions.
• Some functions are exported but not shown in website.

what does tidyverse_update() do?

Incorporate text edits from Stuart and Haley.

Use this instead.

use_lifecycle_badge("EDIT-STAGE")
use_travis()

Remove this (.github/ is created automatically with use_tidy_coc()):

use_directory(".github")
# move coc manually to .github/

This is closer to defaults, and is achieved adding nothing to the left side of the navbar.

Downloading GitHub repo forestgeo/ctfs@master
Error in utils::download.file(url, path, method = download_method(), quiet = quiet,  : 
  cannot open URL 'https://api.github.com/repos/forestgeo/ctfs/zipball/master'

Problems is in fgeo.demography()

library(fgeo)
Error in library(fgeo) : there is no package called ‘fgeo’
> library(fgeo.map)
> library(fgeo.tool)
> library(soilkrig)
Warning message:
In fun(libname, pkgname) : couldn't connect to display ":0"
> library(fgeo.demography)
Error in library(fgeo.demography) : 
  there is no package called ‘fgeo.demography’
> library(fgeo.abundance)

fgeo_nms_conventions()
fgeo_abreviations()
fgeo_funs()

• Workflow:
  • google sheets
  • Project oriented workflow
  • Row oriented workflow
• Managing data
• Exploratory data analysis
• dplyr: wrangling
• ggplot2: visualizing
• janitor: Counting things

Please briefly describe your problem and what output you expect. If you have a question, please don't use this form. Instead, ask on https://stackoverflow.com/, https://community.rstudio.com/, https://github.com/forestgeo/forum/ or email Mauro Lepore at [email protected].

Please include a minimal reproducible example (AKA a reprex). If you've never heard of a reprex before, start by reading https://www.tidyverse.org/help/#reprex.

Brief description of the problem

# insert reprex here

Instead of adding code I may point to good packages. E.g.:

• See this paper presenting the ads package.
• See spatstat. It has a long version history on CRAN going back to 2002.
• Consider using spatstat, recommended by Alexandre (adalardo).
• Research uses of ppm point pattern models.

Record videos for an overview of fgeo.

• fgeo home
• searching functions, packages and datasets
• understanding helpfiles
• Write. Finish blog on packages
• Continue adapting rstudio.cloud/primers

Ideas:

• See how pkgdown parses topic's titles.
• Get functionality from ctfs

Configure following http://pkgdown.r-lib.org/articles/pkgdown.html?q=search%20shift#docsearch-configuration

On Tue, Jun 26, 2018 at 7:47 AM Sylvain Pace [email protected] wrote:
Hi Mauro,

Congratulations, your search is now ready!
I've successfully configured the underlying crawler and it will now run every 24h.

You're now a few steps away from having it working on your website:

• Copy the following CSS/JS snippets and add them to your page

<!-- at the end of the HEAD --> 
<link rel="stylesheet" href="https://cdn.jsdelivr.net/npm/docsearch.js@2/dist/cdn/docsearch.min.css" /> 

<!-- at the end of the BODY --> 
<script type="text/javascript" src="https://cdn.jsdelivr.net/npm/docsearch.js@2/dist/cdn/docsearch.min.js"></script> 
<script type="text/javascript"> docsearch({ 
 apiKey: 'ec79b1c00aff9cd841703edc746e1a71', 
 indexName: 'fgeo', 
 inputSelector: '### REPLACE ME ####', 
 debug: false // Set debug to true if you want to inspect the dropdown 
}); 
</script> 

• Add a search input in your page if you don't have any yet. Then update the inputSelector value in JS snippet to a CSS selector that targets your search input field.
• Optionally customize the look and feel by following the DocSearch documentation (https://community.algolia.com/docsearch/documentation/)
• You can also check your configuration in our github repo (https://github.com/algolia/docsearch-configs/blob/master/configs/fgeo.json).

Please open a pull request if want to leverage your configuration!

Feel free to get back to us if you have any issues or questions regarding the integration.

We'd also be happy to get your feedback and thoughts about DocSearch - so we can continue to improve it.

Have a nice day :)

Sylvain Pace
Software Engineer
| www.algolia.com | @algolia

(info @)

• How to tweak a theme
• Where to place the files in the root directory

Standardize infrastructure following this post.

README

Logo:

• Use logo on the left of package name

<img src="https://i.imgur.com/39pvr4n.png" align="right" height=44 /> 

Badges

EDIT: ADD BADGES CREATED WITH:

use_lifecycle_badge()
use_cran_badge()

EDIT: CONSIDER ADDING BADGES CREATED WITH:

# In .travis.yml consider adding `warnings_are_errors: false`
use_travis()

use_coverage("coveralls")

Installation

# install.packages("remotes")
remotes::install_github("EDIT-OWNER/EDIT-PACKAGE-NAME")

For details on how to install packages from GitHub, see [this article](https://goo.gl/dQKEeg).

Code of Conduct

EDIT: Run this:

use_tidy_coc()

use_directory(".github")
# move coc manually to .github/

Search box finds stuff but the links to found stuff don't work.

library(fgeo)
#> -- Attaching packages ------------------------------------------- fgeo 0.0.0.9000 --
#> v fgeo.abundance  0.0.0.9005     v fgeo.demography 0.0.0.9100
#> v fgeo.base       0.0.0.9001     v fgeo.habitat    0.0.0.9006
#> v fgeo.data       0.0.0.9005     v fgeo.map        0.0.0.9204
#> v fgeo.abundance  0.0.0.9005     v fgeo.tool       0.0.0.9003
#> 

Created on 2018-10-19 by the reprex package (v0.2.1)

Export fgeo_imports _sugests _core, to do things from other pkgs. See ?fgeo_pkg_deps().

This is the home page of fgeo, an R package that helps you Analyze forest diversity and dynamics.

You may bookmark this page so you can find it quickly.

To find out what you can do with fgeo -- even before you install it -- try a Quick Search for
• packages,
• functios, or
• datasets.
Follow the links for information on any topic.

To install fgeo by running this code.

Then in any R session you can load fgeo with library(fgeo) and find anything run fgeo_help().

You can also narrow down your search with specific keywords, for example fgeo_help ("map").

Each help file has a similar structure -- generally with a title, description, arguments and examples.

With latest versions of RStudio you can run examples directly from the Help tab. Highlight the code you want run and press Control/Cmd enter.

If what you found is not quite what you expected, try the links to related topics.

You can try fgeo on rstudio.cloud for free at http://bit.ly/fgeo-demo

Now go ahead and Get Started