Skip to content
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

Add 'How to install' section to the main page #41

Closed
arcticbear opened this issue Mar 12, 2021 · 4 comments · Fixed by #42
Closed

Add 'How to install' section to the main page #41

arcticbear opened this issue Mar 12, 2021 · 4 comments · Fixed by #42
Assignees
Labels
enhancement New feature or request p0-critical Max priority (ASAP)

Comments

@arcticbear
Copy link

Regarding the legal requirements, there must be a section on the website with a description of how to download and/or install the software.

Suggesting to add:

  • A ghost 'install' button in the header on the top right. A click will show a simple flyout dialog. It closes after clicking everywhere outside the menu or after pressing the 'OK' button. The command copy button would be very useful here.
    image

  • A button 'Download' in the Hero section. It should redirect to the 'https://github.com/iterative/cml#install-cml-as-a-package' page with an anchor, as well as link 'More in documentation' in the popover.

Design mockups → Open in Figma.

Full mockup example
@arcticbear
Copy link
Author

@julieg18 Added hovered and pressed states for the flyout dialog elements and the download button. (Open specs in Figma)

Example

@arcticbear
Copy link
Author

arcticbear commented Mar 16, 2021

@julieg18 And almost forgot one important thing. It would be great if UI gives feedback to a user when the command is successfully copied. Green label should disappear after several seconds (let's try 3 sec). (Link to mockup)

image

@julieg18
Copy link
Contributor

julieg18 commented Mar 16, 2021

@julieg18 Added hovered and pressed states for the flyout dialog elements and the download button. (Open specs in Figma)

Example

@arcticbear The styles look great! Is the focus styles supposed to look just like the default styles for the OK button? I don't see any difference between the two. 🤔

@arcticbear
Copy link
Author

@julieg18 Yes, it would be enough having two styles. One for default and pressed states, and another for hovering. The pressed state could be seen only after hovered state, so in motion it would be fine.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request p0-critical Max priority (ASAP)
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants