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

Printed version needs a total review #48

Open
ogregoire opened this issue Oct 27, 2015 · 1 comment
Open

Printed version needs a total review #48

ogregoire opened this issue Oct 27, 2015 · 1 comment

Comments

@ogregoire
Copy link

To help my fellow colleagues starting using git flow, I tried to print the cheatsheet.

Why do I believe that it is a valid use-case? Because this page is "sold" as a cheat sheet (= reference card). And as Wikipedia says, it is a common usage to print them.

I tried to print this cheatsheet on both Firefox and Chrome.

Here are some issues I saw:

  • The comment section shouldn't be present.
  • The list of translations shouldn't be present.
  • The paragraphs are short so there shouldn't be any orphan.
  • All interesting images are on the background and are therefore not visible by default.
  • URLs should have the same style as the text it's wrapped in and should be written down next to the text they refer to.
  • With the stripes, there is some yellow on yellow title text, making it hard to read (specifically "Make a release").

Issues specific to Firefox:

  • The content-part of first page is totally striped.
  • The "feature" 5-lines background starts in section "Getting started" and stop around the "hotfix" title.

I noticed no issue specific to Chrome.

@danielkummer
Copy link
Owner

@ogregoire - yes you're completely right that the page should be printable. I will get on it as soon as I have some free time to take a look at the problem. Until then you'll have to wait... (or create a pull request ;) )

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants