home.social

#pkgdown — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #pkgdown, aggregated by home.social.

  1. I just discovered that the latest release of #pkgdown now adds an llms.txt file to the rendered site by default. Immediately disabled the new 'feature' and added human.json instead 🙃

    codeberg.org/g-rppl/movetrack/

    #rstats #rpackage #noAI #humanjson

  2. I just discovered that the latest release of #pkgdown now adds an llms.txt file to the rendered site by default. Immediately disabled the new 'feature' and added human.json instead 🙃

    codeberg.org/g-rppl/movetrack/

    #rstats #rpackage #noAI #humanjson

  3. I just discovered that the latest release of #pkgdown now adds an llms.txt file to the rendered site by default. Immediately disabled the new 'feature' and added human.json instead 🙃

    codeberg.org/g-rppl/movetrack/

    #rstats #rpackage #noAI #humanjson

  4. I just discovered that the latest release of #pkgdown now adds an llms.txt file to the rendered site by default. Immediately disabled the new 'feature' and added human.json instead 🙃

    codeberg.org/g-rppl/movetrack/

    #rstats #rpackage #noAI #humanjson

  5. I just discovered that the latest release of #pkgdown now adds an llms.txt file to the rendered site by default. Immediately disabled the new 'feature' and added human.json instead 🙃

    codeberg.org/g-rppl/movetrack/

    #rstats #rpackage #noAI #humanjson

  6. Day 5: Package Structure with pkgdown Site Generation 🌐
    Create beautiful documentation websites for your packages! ✨

    Setup: 🔧

    usethis::use_pkgdown()
    pkgdown::build_site()

    💡 Pro Tip: Use usethis::use_pkgdown_github_pages() for automatic deployment.
    📚 Resources: pkgdown.r-lib.org

    📖

  7. Day 5: Package Structure with pkgdown Site Generation 🌐
    Create beautiful documentation websites for your packages! ✨

    Setup: 🔧

    usethis::use_pkgdown()
    pkgdown::build_site()

    💡 Pro Tip: Use usethis::use_pkgdown_github_pages() for automatic deployment.
    📚 Resources: pkgdown.r-lib.org

    #rstats #pkgdown #Documentation #RPackageAdvent2025 📖

  8. Day 5: Package Structure with pkgdown Site Generation 🌐
    Create beautiful documentation websites for your packages! ✨

    Setup: 🔧

    usethis::use_pkgdown()
    pkgdown::build_site()

    💡 Pro Tip: Use usethis::use_pkgdown_github_pages() for automatic deployment.
    📚 Resources: pkgdown.r-lib.org

    #rstats #pkgdown #Documentation #RPackageAdvent2025 📖

  9. Day 5: Package Structure with pkgdown Site Generation 🌐
    Create beautiful documentation websites for your packages! ✨

    Setup: 🔧

    usethis::use_pkgdown()
    pkgdown::build_site()

    💡 Pro Tip: Use usethis::use_pkgdown_github_pages() for automatic deployment.
    📚 Resources: pkgdown.r-lib.org

    #rstats #pkgdown #Documentation #RPackageAdvent2025 📖

  10. Day 5: Package Structure with pkgdown Site Generation 🌐
    Create beautiful documentation websites for your packages! ✨

    Setup: 🔧

    usethis::use_pkgdown()
    pkgdown::build_site()

    💡 Pro Tip: Use usethis::use_pkgdown_github_pages() for automatic deployment.
    📚 Resources: pkgdown.r-lib.org

    #rstats #pkgdown #Documentation #RPackageAdvent2025 📖

  11. @beps I truly understand what you mean. I am now talking a little about . We have a solid integration of , and some other tools. works. A tight integration of would be nice. We have a good R console and a terminal. Likewise, we don't have the deep integration of , and . Some find it good (I) others find it a hindrance.
    In the end, there are many good choices.

  12. @beps I truly understand what you mean. I am now talking a little about #RKWard. We have a solid integration of #git, #rio and some other tools. #quarto works. A tight integration of #styler would be nice. We have a good R console and a terminal. Likewise, we don't have the deep integration of #devtools, #roxygen2 and #pkgdown. Some find it good (I) others find it a hindrance.
    In the end, there are many good choices.

    #rstats

  13. @beps I truly understand what you mean. I am now talking a little about #RKWard. We have a solid integration of #git, #rio and some other tools. #quarto works. A tight integration of #styler would be nice. We have a good R console and a terminal. Likewise, we don't have the deep integration of #devtools, #roxygen2 and #pkgdown. Some find it good (I) others find it a hindrance.
    In the end, there are many good choices.

    #rstats

  14. @beps I truly understand what you mean. I am now talking a little about #RKWard. We have a solid integration of #git, #rio and some other tools. #quarto works. A tight integration of #styler would be nice. We have a good R console and a terminal. Likewise, we don't have the deep integration of #devtools, #roxygen2 and #pkgdown. Some find it good (I) others find it a hindrance.
    In the end, there are many good choices.

    #rstats

  15. @beps I truly understand what you mean. I am now talking a little about #RKWard. We have a solid integration of #git, #rio and some other tools. #quarto works. A tight integration of #styler would be nice. We have a good R console and a terminal. Likewise, we don't have the deep integration of #devtools, #roxygen2 and #pkgdown. Some find it good (I) others find it a hindrance.
    In the end, there are many good choices.

    #rstats

  16. Hey, a new version 2.0.0. of my 𝗯𝘀𝘃𝗮𝗿𝘀 package has lots of new options, such as functions for predictive and structural analyses. But it also comes with a new 𝗽𝗸𝗴𝗱𝗼𝘄𝗻 website! 🕸️📦💯

    bsvars.github.io/bsvars/

  17. @Russpoldrack I usually have a repo per project anyway, so I'm now using quarto for project websites (using github pages), and then I use quarto/revealjs to add a slide deck as a link on the project website.

    Basically the same approach as what @matti and I wrote here with {vertical}, but using #QuartoPub instead of #pkgdown. This is all R-centric, but doesn't need to be.

    link.springer.com/article/10.3

  18. @Russpoldrack I usually have a repo per project anyway, so I'm now using quarto for project websites (using github pages), and then I use quarto/revealjs to add a slide deck as a link on the project website.

    Basically the same approach as what @matti and I wrote here with {vertical}, but using #QuartoPub instead of #pkgdown. This is all R-centric, but doesn't need to be.

    link.springer.com/article/10.3

  19. @Russpoldrack I usually have a repo per project anyway, so I'm now using quarto for project websites (using github pages), and then I use quarto/revealjs to add a slide deck as a link on the project website.

    Basically the same approach as what @matti and I wrote here with {vertical}, but using #QuartoPub instead of #pkgdown. This is all R-centric, but doesn't need to be.

    link.springer.com/article/10.3

  20. @Russpoldrack I usually have a repo per project anyway, so I'm now using quarto for project websites (using github pages), and then I use quarto/revealjs to add a slide deck as a link on the project website.

    Basically the same approach as what @matti and I wrote here with {vertical}, but using #QuartoPub instead of #pkgdown. This is all R-centric, but doesn't need to be.

    link.springer.com/article/10.3

  21. @Russpoldrack I usually have a repo per project anyway, so I'm now using quarto for project websites (using github pages), and then I use quarto/revealjs to add a slide deck as a link on the project website.

    Basically the same approach as what @matti and I wrote here with {vertical}, but using #QuartoPub instead of #pkgdown. This is all R-centric, but doesn't need to be.

    link.springer.com/article/10.3