Closed etiennebacher closed 1 year ago
Just a question: do we need to commit this large number of Markdown files?
All markdown files are used when we run mkdocs build
(called by altdoc::preview()
) so that it can build the docs/site
folder. I'm still thinking of the best way to write a github action that would create all the docs automatically without having to commit anything other than in the usual R development workflow (like pkgdown
).
But for now I commit everything because I put this branch on github pages so that we can have a live demo
Thanks, it make sense now.
Note to self: we still need a docs
folder in the main
branch that contains mkdocs.yaml
and a subfolder docs
containing custom CSS and logo because that's crucial to structure our docs. What we don't need in this folder are:
site
subfolder because it's generated by mkdocs build
Looks like the CI for documentation is ready, it only errors because I don't have the rights to create a branch on this repo
Could the generated files be added to gitignore and then deleted?
I think the preview is still useful for now so if I delete the files we won't have it anymore. Do we do all the cleaning in R files here before merging? @sorhawell
Do we do all the cleaning in R files here before merging?
I didn't quite get this question. How can I help to bring this live, what buttons should I press to give branch permission?
Currently pkgdown pushes to rpolars github.io with secrets.DEPLOY_DOCS
token. Could you use that from the new workflow?
Currently pkgdown pushes to rpolars github.io with secrets.DEPLOY_DOCS token. Could you use that from the new workflow?
We now updated the workflow to also push to this repo. I removed most of the docs files (that will be automatically generated by the workflow) so once @eitsupi's comment is addressed I think we can merge this
Thank you for tackling this tough task! I would like to try a local build later and push some minor updates.
I would like to try a local build later and push some minor updates.
I'd like to implement the "About" page mentioned in this comment in a future PR, unless you want to do it here
I have made some minor updates.
mkdocs.yml
is both the template and an auto generated file, CI was set up to copy the template mkdocs.orig.yml
to mkdocs.yml
just before executing altdoc::update_docs()
.
Perhaps it would be worth adding a new feature that could specify a template for altdoc::update_docs()
If there are no problems with this change, it is working well and can be merged. Great job!
Looks great, thanks for cleaning all of this @eitsupi, it's much better to keep a clear template like this. One thing: should we rename pkgdown.yml
to something else?
Otherwise, if tests pass, I'm ok to merge
One thing: should we rename
pkgdown.yml
to something else?
My understanding is that CI will not run if renamed in this PR. It would make sense to change this in a follow-up PR after merging this.
Looking forward to see the official r-polars. pkgdown was a good stepping stone, but just deprecate it whenever ready.
Great work !
Ok, let's try merging this!
Looks like it worked! :tada: :tada:
I'll make another PR soon with various tweaks
This is amazing work and a massive improvement over pkgdown
. Thanks!
Awesome!
(I forgot to remove the dev doc badge from README...)
Close #137
See progress here:
https://etiennebacher.github.io/r-polars/siteNo longer available (I removed the files so that this can be merged)