Skip to content

Convert remaining narrative docs to tutorials #19688

Closed

Description

@timhoffm

The following docs should be converted to tutorials.

  • docs/users/interactive.rst
  • docs/users/interactive_guide.rst
  • docs/users/event_handling.rst

They are the only narrative docs that is not a tutorial, and thus are hard to find. While they could use some work, moving them as is would already be a net win for discoverability.

Activity

  1. jklymak commented on Mar 11, 2021

    @jklymak
    Member

    Does sphinx-gallery allow bare rst files in the python directory? That would be easiest (plus a redirect).

  2. timhoffm commented on Mar 12, 2021

    @timhoffm
    MemberAuthor

    I don't think so. It's probably renaming to .py and adding comments in front of every line, or .. include: interactive.rst.

  3. rajpratyush commented on Mar 12, 2021

    @rajpratyush
    Contributor

    Can I take up this issue? @timhoffm

  4. timhoffm commented on Mar 13, 2021

    @timhoffm
    MemberAuthor

    Go for it.

  5. tacaswell commented on Aug 22, 2021

    @tacaswell
    Member

    I think we should be pushing things the other way and converting more tutorials to be adjacent to these (to separate out the "how to do a task" from "understand how Matplotlib views the world".

  6. jklymak commented on Aug 22, 2021

    @jklymak
    Member

    To me the current division is whether the page is made via Sphinx gallery or as rst. Ideally there would be a way to combine technology (or even better allow notebooks)

  7. story645 commented on Aug 22, 2021

    @story645
    Member

    @jklymak https://nbsphinx.readthedocs.io/en/0.6.1/subdir/gallery.html

    And also then would that division be

    • tutorials: *.ipynb
    • gallery: *.py
    • narrative docs: *.rst

    which is a bit medium guides the message & I think could either work really well to set expectations on content for each section or end up really clunky.

  8. anntzer commented on Aug 22, 2021

    @anntzer
    Contributor

    fwiw I would also much prefer if s-g could be made to support .rst files, just for editing convenience (e.g. I have better syntax highlighting, and shortcut for directly converting a single rst to html (obviously, some links will be broken, but you still catch plenty of simple rst syntax errors in that way)).

  9. timhoffm commented on Aug 22, 2021

    @timhoffm
    MemberAuthor

    fwiw I would also much prefer if s-g could be made to support .rst file

    sphinx-gallery/sphinx-gallery#330

  10. jklymak commented on Aug 22, 2021

    @jklymak
    Member

    I guess I was thinking even simpler - just support the rst files directly without worrying about backlinks etc.

    However, those links are useful in pointing out that its probably OK to just have an rst->py converter that would only need to be run once to make the files such that s-g could render them.

    The overarching point is that it would be nice if our docs were not organized by the rendering technology, which is why "Users Guide" is different than "Tutorials" currently.

  11. timhoffm commented on Aug 23, 2021

    @timhoffm
    MemberAuthor

    I'm closing this issue because it's not clear how we want to origanize the different doc types. For now, we won't convert the existing narrative docs. At least they are put in a better location by #20867.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions