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

Initial docs restyling #2612

Merged
merged 4 commits into from Jun 13, 2018
Merged

Initial docs restyling #2612

merged 4 commits into from Jun 13, 2018

Conversation

medubelko
Copy link
Contributor

Initial docs restyling to better match Gaffer colors and branding.

Changes

  • Add new stylesheet that adjusts navigation bar colors.
  • Include Gaffer logos as static resources.
  • Add Gaffer logo to navigation.
  • Adjust the mobile header to have better spacing and readability.
  • Some minor adjustments to article text classes.

Enable: logo, smart quotation marks
Disable: links to reST sources
Copy link
Contributor

@andrewkaufman andrewkaufman left a comment

Choose a reason for hiding this comment

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

Thanks @medubelko ! Looks great. I haven't tried on mobile, but I believe you on those bits. Just a couple small comments/questions.

@@ -0,0 +1,146 @@
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
Copy link
Contributor

Choose a reason for hiding this comment

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

Rather than adding the logos directly, can we just copy them in-place using a generate script? They're already in the repo under <localClone>/resources/, so we should be able to copy them during the doc build itself.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I wasn't sure if there was ever going to be a point where they might differ, so for now I just made them static. If you think it's unlikely, should it be added to SCons or its own generate.py script?

Copy link
Contributor

Choose a reason for hiding this comment

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

I'd say its own generate.sh script (simple cp command). If you want to add that now, I can rebase my other branch top of this and adjust it to the new style generate for you.


/* Add icon after external links */
a[href^="http"]:after {
content: " " url(data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAAAoAAAAKCAYAAACNMs+9AAAAVklEQVR4Xn3PgQkAMQhDUXfqTu7kTtkpd5RA8AInfArtQ2iRXFWT2QedAfttj2FsPIOE1eCOlEuoWWjgzYaB/IkeGOrxXhqB+uA9Bfcm0lAZuh+YIeAD+cAqSz4kCMUAAAAASUVORK5CYII=);
Copy link
Contributor

Choose a reason for hiding this comment

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

I'm not sure how I feel about this one. None of the websites we're linking to use an icon for their links... is this considered standard?

Copy link
Contributor Author

@medubelko medubelko Jun 13, 2018

Choose a reason for hiding this comment

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

It adds the standard external link icon () to indicate to the user they're being taken to an outside URL – not for internal doc links. It's a courtesy feature to improve UX. We won't be using external links often, in any case.

Copy link
Contributor

Choose a reason for hiding this comment

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

Yeah, I know. I'm just saying its a courtesy that none of the links on our main page (Arnold, Appleseed, 3delight, Tractor, Sphinx) are doing themselves for their external links, so I was wondering if that's modern standard UX or legacy from wikipedia days?

Copy link
Contributor Author

@medubelko medubelko Jun 13, 2018

Choose a reason for hiding this comment

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

This will differ from the main site. They're still relevant and useful for most help files and docs.

Websites don't use them very often, because there's an understanding by the user that on the web (= multiple "documents," dynamic) most body text links are external references. In docs it's the opposite: most body text links are to other pages in the same help system (= single "document," static), and suddenly opening an external link can be jarring and disruptive. A more immediate use for this is that it will signal to IE users that they'll need to open that link in Isla.

A more complex way of accomplishing this is to use automatic hover-text, but this was the simpler and more direct method.

Copy link
Contributor

Choose a reason for hiding this comment

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

Ok, fair enough. Thanks for the explanation.

- Add Gaffer branding and colors to nav and search
- Minor adjustments to headers and links
- Adjust mobile header title and menu button
@medubelko
Copy link
Contributor Author

Added generate.sh to drag in the logo files, as discussed.

@andrewkaufman
Copy link
Contributor

Thanks!

@andrewkaufman andrewkaufman merged commit b0f5850 into GafferHQ:master Jun 13, 2018
@medubelko medubelko deleted the docStyle branch July 18, 2019 21:51
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

Successfully merging this pull request may close these issues.

None yet

2 participants