-
Notifications
You must be signed in to change notification settings - Fork 1
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
What's a good sphinx API into sphinx-ink? #1
Comments
Interesting. I think this could also be a way to add some of the interactive citations stuff potentially as well. I am a bit rusty on my sphinx, so will take me a few days to get up to speed. Maybe we could meet later this week or next?
|
Ah yeah that makes sense - I had thought you were going with the "ink components" branding which is why I went with "ink" here. +1 to |
OK I've just updated the docs here to the new name, and also updated the example so it uses your new syntax for the components. Let me know if you wanna walk through Sphinx a little bit...I have been knee-deep in sphinx for a few months now haha |
That is awesome - I think that the I will close the other branding issue over in iooxa now! |
Hey @rowanc1 - I was thinking a bit about how Sphinx could utilize your ink-components framework for interactive documents (that would be the first step to get it into jupyter book). I decided to make a little repo that could be used for iteration and exploration. (if this seems to be a good idea in general, I'd probably move it to the executablebooks organization)
Here's a quick proof-of-concept that we can easily load the components with raw HTML, as well as one idea for how the API would work:
https://choldgraf.github.io/sphinx-ink/
Any interest in iterating on this a little bit with me? I'd love to brainstorm ways that we could expose the functionality into ink components using things like roles/directives. I think for roles it is pretty straightforward, but directives will be trickier because they tend to not be as easily-parameterized. Would be curious to hear your thoughts.
The text was updated successfully, but these errors were encountered: