Rambaud Pierrick
Rambaud Pierrick
looking closely to the existing Google docuemntation I think you embraced the mkdocs look and feel so you will want to go for https://jbms.github.io/sphinx-immaterial/ (the one used in geemap)
let me know as well when I can start setting up stuff for a clean documentation (having pre-build run in readthedocs would make my life way easier)
I'm not sure I'm fit for the job but I currently build up my skills in maintaining python libs so I would be happy to help you if it's still...
Hi @jonascj I saw that some new issues were opened are you still looking for a co-maintainer ?
Let me do some preparation PR first and I'll let you know when I'm ready to make a test release
sorry i got busy with other stuff and completely forgot to deal with it. I'll try to take a look as soon as possible
I had one when I published the issue I'll try to find it back. If not I think I can create one super easily
I recently set-up a working workflow to update my libs to pypi, it's based on conventional commits and github actions. It allows to do a release and a changelog in...
no not exactly as the deprecated decorator they introduced is not setting the version reason and is not compatible with Sphinx which to me are 2 huge downgrades. It goes...
I'm also trying to contact the original developer of the lib so you can merge your dev and use the original name.