-
Notifications
You must be signed in to change notification settings - Fork 3
DF Documentation 🔖 #60
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
…nd some automatization of it
I am missing a couple of documents to migrate from CONTRIBUTING.md but I am already opening it for review. |
Looks very slick to me! 👓 |
Ok I am merging this one, thanks @eleniv3d @DamienGilliard for the feedback! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nice !
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No other remark, looks sleek indeed
description
This is a PR introducing the first documentation framework for DF. It's not complete I just throw in the main structure and we will have to split the work to have a nice fully documentation for DF 😃 .
To know how to document I wrote a small guide in
Further resources
>>Developer documentation
>>Documentation
.I liked a lot Jax ( thanks @DamienGilliard for the ref!) and I tried to replicate for us, have a look at the screenshot plis. Basically it is split in two:
Getting Started
: top user (top hand) aimed to be a quickstart basically and that's our gh user,Further resources
: for developers that need extra resources.Have a look and tell me what you think about the general structure and bare-bone content. We can maybe merge it and then split the work to do for the tutorial documentation later.
This is what it looks like:
Warning
I cannot show you the documentation since it has to be merged on main first before to be deployed but you can switch do this branch, upload the conda and do:
this will build and show locally the static website.
For all the features have a look here..
main contribs/modifications
Run()
function for all thecodee.py
in the components. This function is not needed anymore since a double of the metadata (that's what we use for generating documentation)pybind
module that is not fully-automatically documented (marked onpybind
module is not fully documented #64 ).Ruff
andpymy
to help us check python code sanity before committing. Before committing and in an action you will see something like this:additional info
The building of the documentation and deployment is grouped in one git workflow in doc-build.yml. Only when merged to main the documentation will be deployed to the GithubPage, in all other scenarios it will only test the building of the doc.