pola-rs / r-polars

Bring polars to R
https://pola-rs.github.io/r-polars/
Other
405 stars 35 forks source link

docs: Switch website from pkgdown to mkdocs-material with altdoc #138

Closed etiennebacher closed 1 year ago

etiennebacher commented 1 year ago

Close #137

See progress here: https://etiennebacher.github.io/r-polars/site No longer available (I removed the files so that this can be merged)

eitsupi commented 1 year ago

Just a question: do we need to commit this large number of Markdown files?

etiennebacher commented 1 year ago

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).

etiennebacher commented 1 year ago

But for now I commit everything because I put this branch on github pages so that we can have a live demo

eitsupi commented 1 year ago

Thanks, it make sense now.

etiennebacher commented 1 year ago

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:

etiennebacher commented 1 year ago

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

eitsupi commented 1 year ago

Could the generated files be added to gitignore and then deleted?

etiennebacher commented 1 year ago

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

sorhawell commented 1 year ago

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?

etiennebacher commented 1 year ago

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

eitsupi commented 1 year ago

Thank you for tackling this tough task! I would like to try a local build later and push some minor updates.

etiennebacher commented 1 year ago

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

eitsupi commented 1 year ago

I have made some minor updates.

If there are no problems with this change, it is working well and can be merged. Great job!

image

etiennebacher commented 1 year ago

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

eitsupi commented 1 year ago

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.

sorhawell commented 1 year ago

Looking forward to see the official r-polars. pkgdown was a good stepping stone, but just deprecate it whenever ready.

Great work !

eitsupi commented 1 year ago

Ok, let's try merging this!

etiennebacher commented 1 year ago

Looks like it worked! :tada: :tada:

I'll make another PR soon with various tweaks

vincentarelbundock commented 1 year ago

This is amazing work and a massive improvement over pkgdown. Thanks!

eitsupi commented 1 year ago

Awesome!

(I forgot to remove the dev doc badge from README...)