-
Notifications
You must be signed in to change notification settings - Fork 39
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
Improve flow of install page #274
Conversation
It looks like the pr-milestone-check is causing the CircleCI redirector action to be skipped. In any case, this looks good to me, thanks @dstansby ! |
The whole CircleCI job isn't proc'ing... |
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.
I can't make the suggestion, but what are y'alls thoughts on using tab sets instead of the admonitions? (new line 58)
Like here:
https://napari.org/dev/developers/contributing.html#setting-up-a-development-installation
Code:
https://github.com/napari/docs/blob/1a3192fd7fc549b4ef8730dccae8bcbc673096c9/docs/developers/contributing.md?plain=1#L31C5-L54
Love the tabs, maybe in a follow-up? |
# Description Update installation guide: - If I'm installing the bundled app, I don't care about pre-requisites for installing the Python package, so move that section under the "Installing as a Pytho package" section - Modify the header levels, so the second level now only has "Install as Python package", "Install as bundled app", "Next steps". In particular, two sections which are only relevant to the Python package route have been moved down a level to simplify the top level contents. Co-authored-by: Peter Sobolewski <[email protected]>
# References and relevant issues This came up at the docs workgroup and also: #274 (review) # Description Currently, the install docs have pip, conda and GitHub install instructions in series followed by the `checking that it worked`. No-one will use all three approaches. In this PR instead Tabs are used for *each* of the approaches, to let the user choose an install strategy. This makes the install page simpler and cleaner, leading the user to the the next logical step. What it looks like: <img width="776" alt="image" src="https://github.com/napari/docs/assets/76622105/3c86bb63-07e0-44e9-83c5-6e777698f2db">
Description