-
Notifications
You must be signed in to change notification settings - Fork 23
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
Switch theme to openff-sphinx-theme #234
Switch theme to openff-sphinx-theme #234
Conversation
Thanks @Yoshanuikabundi - I think this looks nice, and the unification is a huge plus. However, fI'd like to park this for a day or two while I get something more sensible off the ground. For example, the API docs are all completely broken, but mostly because everything tries to point to old modules names which no longer exist. The only detail I could find right now is that some of the text in this sidebar looks clipped (( |
The above could/should probably be fixed with better-named headers. We'll see if I can figure that out |
Blocked by #235, which should also be good to go |
I'm meeting with Simon to discuss the theme today and then I'll have more info about this one. As for #271 and #255, I was hoping to hear any of your preferences; we should close one and merge the other. As much as I love the idea of autoapi, I think autosummary is probably superior, especially since we can mock imports and since autodoc_pydantic is planning to support this use case in the near future. |
In that case, I think that autosummary is the option we should go with! |
Now that openforcefield/openff-toolkit#979 is merged, I think this should be ready to go? |
This seems to have slipped through the cracks, but I don't think anything should conflict with this going live. |
Description
New theme!! Let me know if you have any thoughts, we have a lot of flexibility with this theme.
Checklist