-
Notifications
You must be signed in to change notification settings - Fork 149
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
Start sphinx docs #177
Start sphinx docs #177
Conversation
This is mostly wired up now, and at least generates the docs on azure. I've also updated the architecture pieces a fair amount (i.e. documented #165 here, rather than on that branch), and spent a little more time on the install piece. There are a number of outstanding issues, of course, but it might make sense to merge and move forward more incrementally: it's not ready to start publishing on readthedocs, and indeed, we may not want to do so, if we want to use screenshots from the acceptance tests in the docs. Some future, non-content thoughts:
|
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.
Incremental progress is the best kind of progress!
|
||
Language Server Specs can be [configured](./LANGUAGESERVERS.ms) by Jupyter users, | ||
Language Server Specs can be [configured](./LANGUAGESERVERS.md) by Jupyter users, |
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 catch!
Waiting for the CI to pass before I merge. |
The tests like to fail on master... |
References
Code changes
Goals for this PR:
(Maybe) non-goals for this PR:
User-facing changes
None, yet
Backwards-incompatible changes
None, yet
Chores