yous / whiteglass Goto Github PK

I would like to use your theme but the last release is from February and the comments code was merged in June 2017.

Any change you could throw up a release on Rubygems?

Thanks for a great theme!

I'd like to have a visual highlight (e.g. boldface) if you visit a page that is part of the navigation. Currently, there is no hint as to what page of the navigation you're on.

A possible solution could be this SO answer.

Why are keywords a comma-separated list, instead of sequence inside the keyword-mapping like

keyword:
  - food
  - recipe
  - avocado

Right now the keywords cannot be processed for anything else, if I understand this correctly.

Great theme by the way. 😊

When links get generated for posts they don’t include category name as the first thing in the path. Links starts with year instead. Anyone switching to this theme will have links broken if they posted links to post else where

I can write the blog in master branch and build by travis automaticlly . But I may need to add pictures for my blog text. I found that the gh_pages branch directory is very different with master .So how should I create the image directory and include them into the text. Thanks

I am trying to create a new blog. Changed the theme to whiteglass. I just have 1 post. I can see it under Archives, but not in the home page. How can I fix it?

The user @carlsonsantana validate your site template "https://yous.github.io/whiteglass/" and found these accessibility errors:

• Page https://yous.github.io/whiteglass/:
  • Issue 02dd1968-b1f0-468b-a75a-e81ec1e1191b:
    • Type: Error
    • Code: WCAG2AA.Principle1.Guideline1_4.1_4_3.G18.Fail
    • Message: This element has insufficient contrast at this conformance level. Expected a contrast ratio of at least 4.5:1, but text in this element has a contrast ratio of 3.78:1. Recommendation: change text colour to #757575.
    • Selector: html > body > footer > div > p
    • Context: <p>© Yous - Powered by <a...</p>
  • Issue d9757176-423f-4373-b613-1c9c91dc2200:
    • Type: Error
    • Code: WCAG2AA.Principle1.Guideline1_4.1_4_3.G18.Fail
    • Message: This element has insufficient contrast at this conformance level. Expected a contrast ratio of at least 4.5:1, but text in this element has a contrast ratio of 3.78:1. Recommendation: change text colour to #757575.
    • Selector: html > body > main > div > div > ul > li:nth-child(4) > header > p
    • Context: <p class="post-meta"> Jan 2, 2017 ...</p>
  • Issue f8f1bd80-82bc-4ef0-b163-d2f7f08d8a23:
    • Type: Error
    • Code: WCAG2AA.Principle1.Guideline1_4.1_4_3.G18.Fail
    • Message: This element has insufficient contrast at this conformance level. Expected a contrast ratio of at least 4.5:1, but text in this element has a contrast ratio of 3.78:1. Recommendation: change text colour to #757575.
    • Selector: html > body > main > div > div > ul > li:nth-child(3) > header > p
    • Context: <p class="post-meta"> Jan 3, 2017 ...</p>
  • Issue 36a573dc-9c41-424a-a4a3-360619773bcc:
    • Type: Error
    • Code: WCAG2AA.Principle1.Guideline1_4.1_4_3.G18.Fail
    • Message: This element has insufficient contrast at this conformance level. Expected a contrast ratio of at least 4.5:1, but text in this element has a contrast ratio of 3.78:1. Recommendation: change text colour to #757575.
    • Selector: html > body > main > div > div > ul > li:nth-child(2) > div > blockquote > p
    • Context: <p>This quote will change your lif...</p>
  • Issue 95dc5e6d-cea3-4f46-9bed-99344ba88915:
    • Type: Error
    • Code: WCAG2AA.Principle1.Guideline1_4.1_4_3.G18.Fail
    • Message: This element has insufficient contrast at this conformance level. Expected a contrast ratio of at least 4.5:1, but text in this element has a contrast ratio of 3.78:1. Recommendation: change text colour to #757575.
    • Selector: html > body > main > div > div > ul > li:nth-child(2) > header > p
    • Context: <p class="post-meta"> Jan 4, 2017 ...</p>
  • Issue 2e26c1ff-022b-4907-bd9c-3c662927a81b:
    • Type: Error
    • Code: WCAG2AA.Principle1.Guideline1_4.1_4_3.G18.Fail
    • Message: This element has insufficient contrast at this conformance level. Expected a contrast ratio of at least 4.5:1, but text in this element has a contrast ratio of 2.65:1. Recommendation: change text colour to #717160.
    • Selector: html > body > main > div > div > ul > li:nth-child(1) > div > figure > pre > code > span:nth-child(17)
    • Context: <span class="c1">#=&gt; prints 'Hi, Tom' to STDO...</span>
  • Issue 7eee096d-50ea-4740-b78d-a293daca934e:
    • Type: Error
    • Code: WCAG2AA.Principle1.Guideline1_4.1_4_3.G18.Fail
    • Message: This element has insufficient contrast at this conformance level. Expected a contrast ratio of at least 4.5:1, but text in this element has a contrast ratio of 3.81:1. Recommendation: change text colour to #0079a2.
    • Selector: html > body > main > div > div > ul > li:nth-child(1) > div > figure > pre > code > span:nth-child(9)
    • Context: <span class="nb">name</span>
  • Issue 3e77ed5a-4195-4522-aa7d-e02ac78cddc2:
    • Type: Error
    • Code: WCAG2AA.Principle1.Guideline1_4.1_4_3.G18.Fail
    • Message: This element has insufficient contrast at this conformance level. Expected a contrast ratio of at least 4.5:1, but text in this element has a contrast ratio of 3.81:1. Recommendation: change text colour to #0079a2.
    • Selector: html > body > main > div > div > ul > li:nth-child(1) > div > figure > pre > code > span:nth-child(6)
    • Context: <span class="nb">puts</span>
  • Issue 36fe9e83-dc51-4b55-86c9-df0575381690:
    • Type: Error
    • Code: WCAG2AA.Principle1.Guideline1_4.1_4_3.G18.Fail
    • Message: This element has insufficient contrast at this conformance level. Expected a contrast ratio of at least 4.5:1, but text in this element has a contrast ratio of 3.81:1. Recommendation: change text colour to #0079a2.
    • Selector: html > body > main > div > div > ul > li:nth-child(1) > div > figure > pre > code > span:nth-child(4)
    • Context: <span class="nb">name</span>
  • Issue 2bc6d27e-6073-45d0-9970-d68e41033c7b:
    • Type: Error
    • Code: WCAG2AA.Principle1.Guideline1_4.1_4_3.G18.Fail
    • Message: This element has insufficient contrast at this conformance level. Expected a contrast ratio of at least 4.5:1, but text in this element has a contrast ratio of 3.78:1. Recommendation: change text colour to #757575.
    • Selector: html > body > main > div > div > ul > li:nth-child(1) > header > p
    • Context: <p class="post-meta"> Jan 5, 2017 ...</p>

You can check these accessibility errors using pa11y.
You can view the full validation results in our website.

I'm still a big fan of the theme.

I was wondering if you would consider adding support for a dark theme using the prefers-color-scheme media query.

I've grown very fond of sites that support a dark theme when reading in low light environments.

It works fine in local but doesn't work after committed to github.

I built a blog using your theme. However I am yet to figure out how to use GitHub Pages to work with it since you said that jekyll-archives wont play well with it. One option is to just publish the contents of _site folder so that GitHub Pages just renders index.html. However when that happened the css didn't work at all. When I looked at the link tag I noticed that location for main.css was - <link rel="stylesheet" href="/whiteglass/assets/main.css"> but there is NO whiteglass folder in _site.

How do I solve this so that whenever I do jekyll serve, everything is built properly?

I have added some custom css to my assets/main.scss file. The site builds locally just fine but Github throws the following error when I try to build it online.

Your SCSS file `assets/main.scss` has an error on line 58: File to import not found or unreadable: whiteglass. Load path: /hoosegow/.bundle/ruby/2.4.0/gems/jekyll-theme-primer-0.5.2/_sass

I'm assuming it has something to do with the whiteglass theme not being a supported theme of github. I've tried adding the jekyll-remote-theme plugin and then referring to the theme in my _config.yml as remote_theme: yous/whiteglass but it still throws the same error.

I can get the post categories working when I build it locally, but they don't show up in github pages :-( can you please help? Thanks,

Hi there, I noticed that the about page offered the following information about creating a post that links directly to a URL:

External URL

external-url turns the title of your post to a link. Specify a URL which you want to link to.

layout: post
title: Jekyll whiteglass theme
external-url: https://github.com/yous/whiteglass

But right now, it seems like all that happens is that the right arrow is added to the title. The anchor tag here still uses the post.url. Should it be using post.external-url if it's present, or am I misunderstanding this feature?

I really like this theme!
But i have some problem when i changing the theme.
It seems that the change shows in the local server by using jeykll server,but when i commit to the github. It doesn't work ,but the article and some title does change. I try to fix it, but still in vain.
Do you guys have some solution with this problem?
This is my blog's link : https://ss12f32v.github.io/
Thank you for making this awesome theme!

Is it possible to have posts with future dates that will only appear once the date has passed?

Your theme has been listed on http://jekyllthemes.ru/

In the above example the word "performance benchmark" is a link but since it's a visited one, it's very hard to recognise that.

Would it be possible to make the colour of visited links more obvious?

In my website's header I see localhost:4000 mentioned in a few places -

<link rel="canonical" href="http://localhost:4000/testing-whiteglass/">
<link rel="alternate" type="application/rss+xml" title="COVID-19 Stories" href="http://localhost:4000/testing-whiteglass/feed.xml">
<meta property="og:url" content="http://localhost:4000/testing-whiteglass/">

Any idea what causes this and how to fix it?

This might be a bit of a noob question, so apologies in advance. But every time I create a new folder under the _site parent (e.g. projects) with an index.html file in it, after a few minutes the folder and index.html file disappear. This happens if I create the folders manually in the directory or via my text editor.

Is there a recommended way of creating new folders / pages that I should be following? I didn't have the same issue using a different Jekyll theme, so I am presuming I am not following correct protocol for your theme.

I have read the docs, but have not been able to find any answer.

Thanks in advance.

Todd

Showing blog posts reverse chronological order makes sense. But if you are using this template for something other than a blog, like a poetry anthology or chapters of a book then it makes sense to show the oldest entry first.
Is there any way to do that?
I looked up the jekyll-paginate plugin but it looks like its no longer under active development or have support for reverse pagination.

I found that a backwards compatible plugin exists - jekyll-paginate-v2

Any idea on how to make the entries in the home page appear in a chronological order?

https://fonts.gstatic.com in _includes/fonts.html 404's.

Hi.

I modify my i18n.yml with words on catalan and spanish. How I put this modification for you?

Thanks for your work

Apparently no posts appear in my homepage. I need to add a _layouts/home.html page, changing line 12 from {% for post in paginator.posts %} to {% for post in page.posts %}.

Is this intentional? Do I need to install some paginator gem? I'm using Jekyll 3.4.3 with Whiteglass 1.3.0.

Hi!

I love this theme, clean and feature full at the same time.
I've got it mostly up and very happy with it.

On to the question/issue: I've seen that the theme makes use of the lang attribute, but when I create posts with a different language (lang: pt for instance) it still shows up just like any other post on the home page.
Can you please tell me if I am doing something wrong or if there is anything else I need to change in the theme to make this work?

Thanks!

Am I correct in observing that whiteglass has no support for favicons right now?

If I need to provide support then I have to edit head.html with maybe one of the solutions from here?

I'd like to display my page in German. The items in the theme that need translation as far as I discovered are:

1. Read on button on index.html
2. Abbreviated month names in index.html and the post-layout.

I'd suggest to enable translation by providing a yaml file where these values can be entered. If none are present, English is selected as default.

Summary: calc($spacing-unit / 2) does not work for me; need to replace with calc(#{$spacing-unit} / 2).

I cannot believe this isn't happening to everyone else using whiteglass. Yesterday I updated my blog (raygard.net, aka raygard.github.io) for the first time in a year. Suddenly all the spacing between paragraphs in all posts was gone!

Eventually, I used wget to retrieve my raygard.net/assets/main.css file. In it, I found this: h1,h2,h3,h4,h5,h6,p,blockquote,pre,ul,ol,dl,figure,.highlight{margin-bottom:calc($spacing-unit / 2)}, along with several other instances of calc($spacing-unit / 2). Of course $spacing-unit means nothing in plain CSS.

I know little of CSS and nothing of SCSS or Sass, but I poked around and found that in December there was a commit to change occurrences of $spacing-unit / 2 to calc($spacing-unit / 2), made because of a breaking change to SCSS to deprecate use of / as divide operator outside of calc().

I do not know the rules governing substitution or evaluation of $variables in SCSS, or why it's not working inside calc() for my blog. Maybe the SCSS processor used by github is defective? At the SCSS playground, I tried $foo: 30px; h3{margin-bottom: calc($foo / 2)} and it worked fine, yielding h3{margin-bottom:15px}.

In any case, using interpolation, I find that $foo: 30px; h3{margin-bottom: calc(#{$foo} / 2)} compiles to h3{margin-bottom:calc(30px / 2)} at the playground, and I get similar results in whiteglass by copying _base.css to my blog and changing to calc(#{$spacing-unit} / 2) in _base.scss (also in _layout.scss). So my blog is fixed for now, but I think it needs to be fixed in whiteglass.

Hello, I am looking for a theme like this that I can use for my github pages

This relates to PR in the template repo - yous/whiteglass-template#3

Hello,

My site builds locally, but I get this error when I push to github.

Your SCSS file blog/assets/main.scss has an error on line 45: File to import not found or unreadable: whiteglass. Load path: /hoosegow/.bundle/ruby/2.5.0/gems/jekyll-theme-primer-0.5.4/_sass.

I have tried with the remote_theme as in the previous issue, but I still get the same error.