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

Redesign the template #1339

Merged
merged 3 commits into from Mar 20, 2017
Merged

Redesign the template #1339

merged 3 commits into from Mar 20, 2017

Conversation

afnizarnur
Copy link
Contributor

Redesign the documentation based on #1304

@coveralls
Copy link

Coverage Status

Coverage remained the same at 95.345% when pulling 8ebe058 on afnizarnur:master into e401337 on sinonjs:master.

@coveralls
Copy link

Coverage Status

Coverage remained the same at 95.345% when pulling 1e788be on afnizarnur:master into e401337 on sinonjs:master.

@fatso83
Copy link
Contributor

fatso83 commented Mar 19, 2017

Seems we need to exclude the docs folder from linting. Ref the failing build https://travis-ci.org/sinonjs/sinon/jobs/212364765

Would you mind, @afnizarnur?

@coveralls
Copy link

coveralls commented Mar 19, 2017

Coverage Status

Coverage remained the same at 95.345% when pulling 538f754 on afnizarnur:master into e401337 on sinonjs:master.

@afnizarnur
Copy link
Contributor Author

Already done :) @fatso83

@fatso83 fatso83 self-requested a review March 19, 2017 17:26
@fatso83 fatso83 self-assigned this Mar 19, 2017
@fatso83
Copy link
Contributor

fatso83 commented Mar 19, 2017

Took a while before I could bundle exec jekyll serve, but finally did. This looks tons better, @afnizarnur! Thanks a lot for your valuable work. The legibility is improved a lot and the general design is smoother and friendlier to the eye.

Also a big-up for taking the extra time to make sure the site is more readable on mobile.

I will hold off merging until another one on the core team signs this one off. What do you think, @sinonjs/sinon-core - should we starte the new week with this design?

@mroderick
Copy link
Member

This is looking pretty good!

I do think that the content area should be wide enough to accommodate 80 chars of code in the examples, without horizontal scrolling.

2017-03-19 at 19 23

I think in the case like this, visitors are most likely to be using desktop browsers with desktop screens.

What do you think?

Copy link
Contributor

@fatso83 fatso83 left a comment

Choose a reason for hiding this comment

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

Finally got time to look at the actual code. Just a few comments.

<div class="footer-col footer-col-1">
<ul class="contact-list">
<li>{{ site.title }}</li>
<li><a href="http://groups.google.com/group/sinonjs">http://groups.google.com/group/sinonjs</a></li>
Copy link
Contributor

Choose a reason for hiding this comment

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

Are we sure we want to get rid of this? I think we should have at least the same pointers as we already have in the README on Github. If not in the same place, then somewhere.

Copy link
Member

Choose a reason for hiding this comment

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

The link is on the homepage at the very bottom now. However, I think having the Google group to the footer on all pages (additionally) is a good idea.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Yeah, I forget to add the google group 😅 . Will proceed it now, and add it to the footer.

{% include header.html %}

<div class="content">
<div class="container container-2">
Copy link
Contributor

Choose a reason for hiding this comment

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

This might be a bit of a nitpick, but container-2 does not tell me much in the way of "what separates this from the normal container". Might choose a slightly more telling name?

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 agree with you. Basically, it's just different container size.

@@ -1,10 +1,10 @@
---
layout: page
title: API documentation
title: Sinon.JS - API documentation
Copy link
Contributor

Choose a reason for hiding this comment

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

Good, this is a lot better for SEO.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Yeah, may I change all of the title pages to the better title? I found many titles in documentation is not using good SEO

@fatso83
Copy link
Contributor

fatso83 commented Mar 19, 2017

I also find that we should be able to see a width of 80 chars in code snippets on desktop. Scrolling is fine if on mobile.

@mantoni
Copy link
Member

mantoni commented Mar 20, 2017

Looks great! I agree that the font size of the code snippets could be a little smaller to fit 80 characters. I'd vote to merge and deploy this with the one font-size change – or maybe even as is – and iterate on it from there. It's already a big step forward.

Thank you @afnizarnur for the nice work! 👏 👍

@fatso83
Copy link
Contributor

fatso83 commented Mar 20, 2017

Yeah, I agree on the "merge and iterate until perfect" approach. Merge at will :-)

@mantoni mantoni merged commit 6a7c801 into sinonjs:master Mar 20, 2017
@mantoni
Copy link
Member

mantoni commented Mar 20, 2017

Aaaaaaand the new design has shipped! http://sinonjs.org

However, the GitHub asset is missing, which was not the case when I checked locally. Any idea why @afnizarnur ?

@mantoni
Copy link
Member

mantoni commented Mar 20, 2017

No worries, got it. GitHub hosting is apparently case sensitive while the locally served version is not.

@afnizarnur
Copy link
Contributor Author

Wow cool thanks! Glad to help Sinon.JS 😃 🙌 🎉🎉🎉🎉 @mantoni

timcosta pushed a commit to timcosta/sinon that referenced this pull request Mar 21, 2017
* Redesign the template

* Fix error

* Exclude docs/assets/ from .eslint
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

5 participants