[
https://issues.apache.org/jira/browse/SEDONA-245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17697512#comment-17697512
]
Gregoire Leleu commented on SEDONA-245:
---------------------------------------
Preview of the pkgdown docs here:
[https://gregleleu.github.io/sedona/docs/index.html]
I ported over a lot of the R pages in the existing documentation.
What would be the best way to integrate this to the website? Arrow has
essentially a subsite by language (docs/project, docs/r, docs/python etc.)
> Switch R documentation to pkgdown
> ---------------------------------
>
> Key: SEDONA-245
> URL: https://issues.apache.org/jira/browse/SEDONA-245
> Project: Apache Sedona
> Issue Type: Improvement
> Reporter: Gregoire Leleu
> Priority: Major
>
> R users are increasingly getting used to pkgdown-generated documentation.
> This would lower the bar to entry for new users and help current users work
> faster
> Pkgdown automates the creation of:
> * Function reference pages
> * Articles (programming guides)
> * A getting started page
> Sparklyr is using it:
> [https://spark.rstudio.com/packages/sparklyr/latest/reference/]
> Arrow R package is a great example in the Apache ecosystem:
> [https://arrow.apache.org/docs/r/]
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
