Skip to content

Conversation

@choldgraf
Copy link
Member

@choldgraf choldgraf commented Jul 25, 2025

This updates our documentation to make it a bit easier to navigate and understand. It also makes some content improvements along the way.

Docs preview of this PR is here

Here are some major things that this PR tries to improve:

  • The get started guide is now a tutorial, meant to be followed step by step, in line with how Diataxis recommends tutorials be used. It now has fewer information, and focuses specifically on "getting started"
  • The howto section has been renamed the user guide, and now groups pages based on major topic area (e.g. Configuration, Deployment, etc).
  • The giant list of configuration files is broken into sub-sections based on the kind of workflow they're attached to (e.g. datascience) to make it easier to parse.
  • A lot of content has been consolidated and-or moved around to make it easier to find the right information in one place.
  • Some updates to styling so that we hide sidebars when they aren't needed, improvements to the dark-mode logo, etc.
  • Updating a lot of content to markdown so that it's easier to maintain and improve.
  • Uses the dirhtml builder for "clean" URLs. If we merge this, we should enable clean URLs with readthedocs so that any direct links will properly redirect

More updates

  • Adds a little guide on when to use repo2docker in different scenarios.
  • Creates a short how-to for each scenario with example code and external links.
  • Updates the landing page so that it's more visually appealing and quick to parse, and "feels like" a landing page.

It probably could use a pass or two to double check that the structure works and that I haven't missed something. Happy to iterate with feedback if folks would like.

@yuvipanda
Copy link
Collaborator

/cc @chuckwondo who has helped with related docs to take a look if he can :)

Copy link

@chuckwondo chuckwondo left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for tagging me @yuvipanda.

@choldgraf, thanks for the reorg. Your description of the reorg sounds great, and I've added a few comments, but I haven't gone over it in great detail. If I could see it all properly rendered, it would be much easier to provide comments regarding the layout/reorg, and go through it all in detail. Is that possible without my having to pull it down and run the doc server locally?

@yuvipanda
Copy link
Collaborator

@chuckwondo you can see it in https://repo2docker--1433.org.readthedocs.build/en/1433/! That link is accessible via the tests - it's the read the docs

@choldgraf
Copy link
Member Author

The latest PR adds a bit more content using some slides from a presentation that @yuvipanda has given a few times about repo2docker. Here are some highlights (copied to the PR body as well):

  • Adds a little guide on when to use repo2docker in different scenarios.
  • Creates a short how-to for each scenario with example code and external links.
  • Updates the landing page so that it's more visually appealing and quick to parse, and "feels like" a landing page.

I think this is ready for somebody to take a pass at it - many thanks for the review @chuckwondo - I'll get to your questions when I take another pass after you or somebody else gives it a look.

@choldgraf choldgraf marked this pull request as ready for review July 31, 2025 01:13
Copy link
Contributor

@rgaiacs rgaiacs left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Great revamp of the documentation. I added minor comments. I'm happy for this to be merged and further improvement to be made in new pull requests.

@choldgraf
Copy link
Member Author

I believe that I've addressed all of the comments except for a couple. I'm not sure whether we recommend "just" repo2docker or the full jupyter-repo2docker, I'm also not sure what our policy is on calling them container images vs. Docker images. Could we resolve those in a follow-up PR? This one is already quite beefy!

@rgaiacs
Copy link
Contributor

rgaiacs commented Aug 1, 2025

Yes, I can send a PR covering the use of "container image".

@choldgraf
Copy link
Member Author

Feel free to ping me and I'm happy to review. Shall we merge this one and then iterate there?

@rgaiacs
Copy link
Contributor

rgaiacs commented Aug 1, 2025

Shall we merge this one and then iterate there?

Yes. 👍 to merge.

@choldgraf
Copy link
Member Author

OK cool - let's wait a couple hours to see if @chuckwondo wants to give another pass, but I think I addressed his questions, and given your review i think it's safe to merge. I'll merge if he doesn't ask us to hold off. Happy to iterate with y'all further

Copy link

@chuckwondo chuckwondo left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I really like the reorg and the clarity! Thanks!

Comment on lines 10 to 11
follows the [Reproducible Executable Environment Specification](./specification.md). Repositories can be pulled from a number of repository providers, such as the URL of a Git repository, a [DOI](https://en.wikipedia.org/wiki/Digital_object_identifier) from Zenodo or Figshare, a [Handle](https://en.wikipedia.org/wiki/Handle_System) or DOI from a Dataverse installation, a [SWHID] of a directory of a revision archived in the
[Software Heritage Archive](https://archive.softwareheritage.org), or a path to a local directory.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Consider pulling these cases out into a bulleted list for better visibility/readability.

@choldgraf
Copy link
Member Author

Thanks @chuckwondo for the extra comments - I've gone through and made another round of edits to address your suggestions. Thank you to both of you for your help.

I'll merge this one in since we have one explicit and one implicit approval, and please ping me if y'all would like to iterate on the content more from here!

@choldgraf choldgraf merged commit 6cf91e4 into jupyterhub:main Aug 1, 2025
21 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants